Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array


Recommended Posts

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.

 

Link to comment
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 by Kill3r
edit
Link to comment
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.

Link to comment

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 by Singularity42
Link to comment
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.

Link to comment
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

 

638635572_Screenshot2022-05-31154207.png.716892045a0d5c64d79a0d22f2e57429.png

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.

Link to comment
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?

Link to comment
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.

  • Like 1
Link to comment

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?

 

 

 

Screenshot 2022-06-04 at 10.02.09.png

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.