10 minutes ago, Vic_ent said:

 

Not sure worth mentioning, but when I click on the Unmount button, it shows Unmounting but finally it seems to not succeed and shows again Unmount.

 

It's busy:

May 29 09:50:23 TALASSA unassigned.devices: Unmounting partition 'sdj1' at mountpoint '/mnt/disks/UGREEN_MassStorageClass'...
May 29 09:50:23 TALASSA unassigned.devices: Synching file system on '/mnt/disks/UGREEN_MassStorageClass'.
May 29 09:50:23 TALASSA unassigned.devices: Unmount cmd: /sbin/umount '/dev/sdj1' 2>&1
May 29 09:50:23 TALASSA unassigned.devices: Unmount of 'sdj1' failed: 'umount: /mnt/disks/UGREEN_MassStorageClass: target is busy. '
May 29 09:50:23 TALASSA unassigned.devices: Partition 'UGREEN MassStorageClass' cannot be unmounted.

 

13 hours ago, JorgeB said:

Won't that be because there's no card inserted? They also don't count for Unraid licensing purposes, when there's no card inserted.

I made a change so a disk device with a zero size will not show in UD.

On 5/28/2022 at 12:04 AM, dlandon said:

they are plugged into a backplane on an DL380

 

Post your diagnostics zip file.

Hi @dlandon, here is my diagnostics file.

 

Thanks

 

unraid-diagnostics-20220530-1000.zip

Edited May 30, 20224 yr by Kill3r
extra info

On 5/27/2022 at 7:58 AM, Kill3r said:

Adding a second pushes the first into historic devices

 

Can I get the diagnostics in this condition?

49 minutes ago, dlandon said:

On 5/27/2022 at 1:58 PM, Kill3r said:

 

Can I get the diagnostics in this condition?

Hi 

 

Sure, sorry i unplugged on drive to stop it constantly filling the logs with 

 

"device /dev/sdx problem getting id"

 

thanks

 

unraid-diagnostics-20220530-1322.zip

18 minutes ago, Kill3r said:

Hi 

 

Sure, sorry i unplugged on drive to stop it constantly filling the logs with 

 

"device /dev/sdx problem getting id"

 

thanks

 

unraid-diagnostics-20220530-1322.zip 258.28 kB · 1 download

The best I can tell, it's an issue with the way the disks are being seen by Linux and isn't something UD can sort out.

2 hours ago, dlandon said:

The best I can tell, it's an issue with the way the disks are being seen by Linux and isn't something UD can sort out.

Any thing i can do from a Unraid perspective to attempt to change the SCSI ID? 

12 minutes ago, Kill3r said:

Any thing i can do from a Unraid perspective to attempt to change the SCSI ID? 

Hi have just found a similar issue on ESXi which is a HP driver based issue (fixed in hpsa-2.0.18), how can i find out what driver version Unraid is using for the HP controller? and can i replace the driver as a test? 

 

I do realise this is technically falling outside of the UD plugin now too.

 

Thanks

Edited May 30, 20224 yr by Kill3r
edit

2 hours ago, Kill3r said:

Any thing i can do from a Unraid perspective to attempt to change the SCSI ID? 

No.  What would you change it to?  I don't think that is the issue.  The IDs are unique, the issue is that the controller is confused on what is installed and being reported to Linux.

Server went AWOL overnight.  CPU processes were maxed out at 99.99%.  I resolved that, but the new issue is that I cannot mount my Unassigned disks, where my VM images live:

 

May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Write Protect is off
May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Mode Sense: 46 00 10 08
May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 31 08:25:14 Singularity kernel: sdm: sdm1
May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Attached SCSI disk
May 31 08:26:21 Singularity emhttpd: Samsung_SSD_870_S6R4NJ0R607499P_33001438038737393 (sdm) 512 3907029168
May 31 08:26:21 Singularity emhttpd: read SMART /dev/sdm
May 31 08:26:32 Singularity unassigned.devices: Disk with ID 'Samsung_SSD_870_S6R4NJ0R607499P_33001438038737393 (sdm)' is not set to auto mount.
May 31 09:07:40 Singularity unassigned.devices: Error: Device '/dev/sdm1' mount point 'Samsung_SSD_' - name is reserved, used in the array or by an unassigned device.
May 31 09:08:22 Singularity unassigned.devices: Error: Device '/dev/sdm1' mount point 'Samsung_SSD_' - name is reserved, used in the array or by an unassigned device.

 

Any ideas on how to resolve this?

 

Edit:  I see, its the mount point name.  Which is failing when I attempt to change it. 
Edit 2:  It looks like it also gave the same label to my cache disk:

 

/dev/sdl1 on /mnt/cache type xfs (rw,noatime) [Samsung_SSD_]
...
sdl      8:176  0 232.9G  0 disk
└─sdl1   8:177  0 232.9G  0 part /mnt/cache

Thanks.

singularity-flash-backup-20210517-1342.zip

Edited May 31, 20224 yr by Singularity42

Afternoon, I have an 'electricity' icon my Samsung SSD (unassigned device) which I do not recognise, could anyone help with an explanation please.  I did check Google but nothing jumping out at me.  Thanks, Jon

 

1 hour ago, Singularity42 said:

Server went AWOL overnight.  CPU processes were maxed out at 99.99%.  I resolved that, but the new issue is that I cannot mount my Unassigned disks, where my VM images live:

 

May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Write Protect is off
May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Mode Sense: 46 00 10 08
May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 31 08:25:14 Singularity kernel: sdm: sdm1
May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Attached SCSI disk
May 31 08:26:21 Singularity emhttpd: Samsung_SSD_870_S6R4NJ0R607499P_33001438038737393 (sdm) 512 3907029168
May 31 08:26:21 Singularity emhttpd: read SMART /dev/sdm
May 31 08:26:32 Singularity unassigned.devices: Disk with ID 'Samsung_SSD_870_S6R4NJ0R607499P_33001438038737393 (sdm)' is not set to auto mount.
May 31 09:07:40 Singularity unassigned.devices: Error: Device '/dev/sdm1' mount point 'Samsung_SSD_' - name is reserved, used in the array or by an unassigned device.
May 31 09:08:22 Singularity unassigned.devices: Error: Device '/dev/sdm1' mount point 'Samsung_SSD_' - name is reserved, used in the array or by an unassigned device.

 

Any ideas on how to resolve this?

 

Edit:  I see, its the mount point name.  Which is failing when I attempt to change it. 
Edit 2:  It looks like it also gave the same label to my cache disk:

 

/dev/sdl1 on /mnt/cache type xfs (rw,noatime) [Samsung_SSD_]
...
sdl      8:176  0 232.9G  0 disk
└─sdl1   8:177  0 232.9G  0 part /mnt/cache

Thanks.

singularity-flash-backup-20210517-1342.zip 102.56 kB · 0 downloads

Change one or both of the mount points/names.  They must be unique.

48 minutes ago, JonUKRed said:

Afternoon, I have an 'electricity' icon my Samsung SSD (unassigned device) which I do not recognise, could anyone help with an explanation please.  I did check Google but nothing jumping out at me.  Thanks, Jon

 

When the disk is mounted that lets you run the device script - if you've set up a script for the device.  Hover your moue over the icon when it is blue and you'll get a tooltip about what it does.

4 hours ago, dlandon said:

Change one or both of the mount points/names.  They must be unique.

 

Yep, figured that out, thanks.  

Do you know why this happens?  Ive seen it reported here quite a few times, had it happen a few times, and have some friends that said its happened to them as well.  Should it retain labels?

3 minutes ago, Singularity42 said:

 

Yep, figured that out, thanks.  

Do you know why this happens?  Ive seen it reported here quite a few times, had it happen a few times, and have some friends that said its happened to them as well.  Should it retain labels?

Unless you manually change the mount point, UD will use a default mount point it puts together that can change.  Once you manually change the mount point, it will stay committed to that mount point and not change again.  Due to some changes lately (probably from udev, not UD), the default mount point changed on some devices.

I Have a disk that is mounted, it is assigned to a docker as a read/write slave and it keeps showing up as a drive share!

 

Is this intended, SMB sharing is turned off on the Unassigned Drive section yet its still showing as a share. Is this part of the slave function?

 

 

 

2 hours ago, Nano said:

Is this intended, SMB sharing is turned off on the Unassigned Drive section yet its still showing as a share. Is this part of the slave function?

No.  Post your diagnostics zip file.

2 hours ago, dlandon said:

No.  Post your diagnostics zip file.

 

pontower-diagnostics-20220604-1416.zip

32 minutes ago, Nano said:

 

pontower-diagnostics-20220604-1416.zip 174.72 kB · 0 downloads

I don't see anything obvious.  Where do you see the UD disk being shared?  Does FCP report any share issues?

7 hours ago, dlandon said:

I don't see anything obvious.  Where do you see the UD disk being shared?  Does FCP report any share issues?

Its showing as a SMB share. 

17 minutes ago, Nano said:

Its showing as a SMB share. 

Show the output of the command: ls /etc/samba/unassigned.devices

10 hours ago, dlandon said:

Show the output of the command: ls /etc/samba/unassigned.devices

I assume I have ran the command wrong?

2 hours ago, Nano said:

I assume I have ran the command wrong?

My bad.  ls /etc/samba/unassigned-shares/

6 minutes ago, dlandon said:

My bad.  ls /etc/samba/unassigned-shares/

 

There is something there!

Edited June 5, 20224 yr by Nano

That shows UD is sharing the disk.  I'll have to look and see how this happens.