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


dlandon

Recommended Posts

Thanks a lot. The update seems to have fixed (part of) my issue.


I am not sure though whether it is fully solved? The disk now mounts and shows two partitions (TO_Exter_nal_USB_3.0 and TO_Exter_nal_USB_3.0-part5). However, there seems to be a third partition (disks). Not sure what this partition does and whether it is a bug of UD or part of the disk?

 

Attached diagnostic log. Thanks for your help!

tower-diagnostics-20201005-0910.zip

Link to comment

I continue to face issues when switching between disks in my USB enclosure (even with turning it off/on, plugging on/off). What solves it is to restart the Unraid server, but this defeats the purpose.

 

Attached log shows some info on some more issues:

 

1) Two disks (sdv and sdw) are both connected and seem perfect. However, when I try to run a SMART test, it says that the disks are spun down. Also, it gives a different size. Both are connected via one USB enclosure.

 

2) One disk (sdx) show non-mountable and shows two parities. I don't think the disk is broken and this one actually ran a successful SMART test.

 

Attached a new diagnostic.

tower-diagnostics-20201005-0940.zip

Link to comment
9 hours ago, steve1977 said:

I continue to face issues when switching between disks in my USB enclosure (even with turning it off/on, plugging on/off). What solves it is to restart the Unraid server, but this defeats the purpose.

 

Attached log shows some info on some more issues:

 

1) Two disks (sdv and sdw) are both connected and seem perfect. However, when I try to run a SMART test, it says that the disks are spun down. Also, it gives a different size. Both are connected via one USB enclosure.

 

2) One disk (sdx) show non-mountable and shows two parities. I don't think the disk is broken and this one actually ran a successful SMART test.

 

Attached a new diagnostic.

tower-diagnostics-20201005-0940.zip 249.09 kB · 1 download

You have multiple issues going on here.

 

I found that you have a nvme disk mounted with UD and UD was issuing a spin down command.  That's fixed in the latest release.

 

You have one of the mount points on a disk set to 'disks'.  That is not a good choice of mount point names.

 

Please post a screen shot of the UD page so I can see the particulars of the disks and partitions.  Be sure that you set the 'None' switch to show 'All' so I can see the partitions.

Link to comment

Thanks for your note.

 

The NVME devices are working flawless. So are 2 internal disks. The issue is contained to USB devices (and happens after changing the disk within the USB enclosure).


I don't think any of my mount points is called "disks". I think that's part of the issue with the plugin in my use case that makes this to display like that.

 

I will post a screenshot later.

Link to comment
7 minutes ago, steve1977 said:

The NVME devices are working flawless. So are 2 internal disks. The issue is contained to USB devices (and happens after changing the disk within the USB enclosure).

You said when you tried to run a SMART test, it said the disk was spun down.  That's what I addressed.

 

USB enclosures are a problem with UD because of the way they present the disk serial numbers to UD.  I'm not very hopeful that you can do what you want with the enclosure and UD.

Link to comment

Yes, thanks. All permanently installed / mounted disks work very well. This includes the NVME disks and also disks that are connected directly to the SATA adapters of my mobo.

 

USB works when starting up Unraid. However, if I turn off / detached the USB enclosure and put in another disks, things go crazy...

 

Below copy & paste from the GUI about disks sdx:

 

sdx nal_USB_3.0_[ID-removed]-4 TB--  

1TO_Exter_nal_USB_3.0MOUNT-0 B--  

2disksMOUNT-0 B--  

 

Both cannot be mounted.

Edited by steve1977
Link to comment

I have a quick (hopefully) question/issue. I'm sure I'm just missing something, but UD shows my array devices as... well... Unassigned devices... Screen shots included, and hopefully self explanatory. The sd* identification is different between the two, but as you can see the HDD ID is the same.

Array Diskss.jpg

UD Disks.jpg

Link to comment
2 hours ago, HSEDuster said:

I have a quick (hopefully) question/issue. I'm sure I'm just missing something, but UD shows my array devices as... well... Unassigned devices... Screen shots included, and hopefully self explanatory. The sd* identification is different between the two, but as you can see the HDD ID is the same.

Array Diskss.jpg

UD Disks.jpg

Post diagnostics.

Link to comment
11 minutes ago, HSEDuster said:

So I feel pretty dumb asking this, but which? I downloaded the diagnostics but I somewhat doubt you need/want all the various files. I am including the syslog but if there's another, I'll happily post it. 

syslog.txt 252.45 kB · 0 downloads

Post the complete diagnostics.zip.  I'm needing to see the vars so I can see how Unraid has assigned the disks.

Link to comment
2 hours ago, HSEDuster said:

So I feel pretty dumb asking this, but which? I downloaded the diagnostics but I somewhat doubt you need/want all the various files. I am including the syslog but if there's another, I'll happily post it. 

For future reference, please assume we want the complete zip. It has many things in it that can help make much more sense of things than just the syslog. I often don't even look at the syslog until I have looked at other things in diagnostics just to get some context of what I might be looking for in those hundreds of lines of syslog. And many things syslog doesn't even tell us that are in other parts of the diagnostics.

 

Save everyone time if we don't even have to ask for it. For example, it was 4 hours after your initial question before we finally got the diagnostics.

Link to comment
1 hour ago, HSEDuster said:

Oh okay, here you go then. Thank you very much.

tower-diagnostics-20201005-1609.zip 127.91 kB · 0 downloads

I'm not an expert with disk controllers, but it appears your disk controller caused Linux to have trouble assigning drive designations for Unraid and Unraid assigned the wrong designations to the array disks.  UD checks the vars for the disks not assigned to the array and designates any that are not as unassigned disks.  In this case all disks look to UD to be unassigned.

Oct  4 17:57:13 Tower emhttpd: Device inventory:
Oct  4 17:57:13 Tower emhttpd: HUS724020ALS641_P5GPZ54V (sdm) 512 3907029168
Oct  4 17:57:13 Tower emhttpd: device /dev/sdj problem getting id
Oct  4 17:57:13 Tower emhttpd: device /dev/sdk problem getting id
Oct  4 17:57:13 Tower emhttpd: device /dev/sdh problem getting id
Oct  4 17:57:13 Tower emhttpd: device /dev/sdg problem getting id
Oct  4 17:57:13 Tower emhttpd: device /dev/sdd problem getting id
Oct  4 17:57:13 Tower emhttpd: HUH72808CLAR8000_VJGT1S8X (sdt) 4096 1953506646
Oct  4 17:57:13 Tower emhttpd: device /dev/sde problem getting id
Oct  4 17:57:13 Tower emhttpd: KINGSTON_SA400S37120G_50026B768240E4F0 (sdb) 512 234441648
Oct  4 17:57:13 Tower emhttpd: HUS724040ALS640_PCKJBP8X (sdr) 512 7814037168
Oct  4 17:57:13 Tower emhttpd: device /dev/sdf problem getting id
Oct  4 17:57:13 Tower emhttpd: device /dev/sdc problem getting id
Oct  4 17:57:13 Tower emhttpd: HUS724040ALS640_PCJGNY0X (sds) 512 7814037168
Oct  4 17:57:13 Tower emhttpd: HUS724040ALS640_PCJGET8X (sdn) 512 7814037168
Oct  4 17:57:13 Tower emhttpd: HUS724040ALS640_PCKJMT2X (sdq) 512 7814037168
Oct  4 17:57:13 Tower emhttpd: HUH72808CLAR8000_VJGS29MX (sdo) 4096 1953506646
Oct  4 17:57:13 Tower emhttpd: HUS724020ALS641_P6JV08ZV (sdl) 512 3907029168
Oct  4 17:57:13 Tower emhttpd: device /dev/sdi problem getting id
Oct  4 17:57:13 Tower emhttpd: HUS724040ALS640_PCKJ6ZBX (sdp) 512 7814037168
Oct  4 17:57:13 Tower emhttpd: Kingston_DataTraveler_2.0_1C1B0D65F648B421496A204F-0:0 (sda) 512 30240768
Oct  4 17:57:13 Tower kernel: mdcmd (1): import 0 sdt 64 7814026532 0 HUH72808CLAR8000_VJGT1S8X
Oct  4 17:57:13 Tower kernel: md: import disk0: (sdt) HUH72808CLAR8000_VJGT1S8X size: 7814026532 
Oct  4 17:57:13 Tower kernel: mdcmd (2): import 1 sdr 64 3907018532 0 HUS724040ALS640_PCKJBP8X
Oct  4 17:57:13 Tower kernel: md: import disk1: (sdr) HUS724040ALS640_PCKJBP8X size: 3907018532 
Oct  4 17:57:13 Tower kernel: mdcmd (3): import 2 sds 64 3907018532 0 HUS724040ALS640_PCJGNY0X
Oct  4 17:57:13 Tower kernel: md: import disk2: (sds) HUS724040ALS640_PCJGNY0X size: 3907018532 
Oct  4 17:57:13 Tower kernel: mdcmd (4): import 3 sdq 64 3907018532 0 HUS724040ALS640_PCKJMT2X
Oct  4 17:57:13 Tower kernel: md: import disk3: (sdq) HUS724040ALS640_PCKJMT2X size: 3907018532 
Oct  4 17:57:13 Tower kernel: mdcmd (5): import 4 sdp 64 3907018532 0 HUS724040ALS640_PCKJ6ZBX
Oct  4 17:57:13 Tower kernel: md: import disk4: (sdp) HUS724040ALS640_PCKJ6ZBX size: 3907018532 
Oct  4 17:57:13 Tower kernel: mdcmd (6): import 5 sdn 64 3907018532 0 HUS724040ALS640_PCJGET8X
Oct  4 17:57:13 Tower kernel: md: import disk5: (sdn) HUS724040ALS640_PCJGET8X size: 3907018532 
Oct  4 17:57:13 Tower kernel: mdcmd (7): import 6 sdm 64 1953514552 0 HUS724020ALS641_P5GPZ54V
Oct  4 17:57:13 Tower kernel: md: import disk6: (sdm) HUS724020ALS641_P5GPZ54V size: 1953514552 
Oct  4 17:57:13 Tower kernel: mdcmd (8): import 7 sdl 64 1953514552 0 HUS724020ALS641_P6JV08ZV
Oct  4 17:57:13 Tower kernel: md: import disk7: (sdl) HUS724020ALS641_P6JV08ZV size: 1953514552 

This isn't really a UD issue.  UD is doing exactly what it is supposed to do.

 

I would report this in the 6.8.3 support forum.

Link to comment

An update on my two issues:

 

1) SMART test - SMART test only works with my one-bay enclosure. It does not work with my two-bay enclosure. This may be because of the enclosure rather than the UD script?

 

2) Mounting point - when I freshly boot Unraid, all works fine and the USB is well detected. However, when I turn off the USB, switch the disk and turn it back on, it no longer works. It has a proper mounting point at first. Upon changing the disk, the mounting point shows as "TO_Exter_nal_USB_3.0". I believe this can be fixed with XFS formatted disks by changing the UID in the settings. For NFS disks, there is no option to change it, which may be the cause of this issue?

Link to comment
21 hours ago, steve1977 said:

Yes, thanks. All permanently installed / mounted disks work very well. This includes the NVME disks and also disks that are connected directly to the SATA adapters of my mobo.

 

USB works when starting up Unraid. However, if I turn off / detached the USB enclosure and put in another disks, things go crazy...

 

Below copy & paste from the GUI about disks sdx:

 

sdx nal_USB_3.0_[ID-removed]-4 TB--  

1TO_Exter_nal_USB_3.0MOUNT-0 B--  

2disksMOUNT-0 B--  

 

Both cannot be mounted.

I can't help you with a text snippet from the UD page.  I asked for a screen shot of the UD page so I can see the file system type, the partitioning of the disks, and the other information shown on the complete UD page.

Edited by dlandon
Link to comment

I did a few more round of problem solving what is leading to what issue with various disks and enclosure. A few things I found out:

 

1) None of my multi-bay USB enclosures supports to run RAID. Only the single-bay enclosure supports it. I don't think that this issue is related to UD, but is more likely a broader Unraid issue (or even a hardware limitation?)

 

2) The UD issue does not occur after starting Unraid and freshly accessing the disks. It occurs once I unplug the USB enclosure and replace the disks within it. For example, I take out a 2TB disk and replace it instead with a 250GB disk. When I do this, the volume info does not get updated (i.e., 250GB is identified as 2TB disk after mounting). Also, the mount point has a different name rather than the actual mount name. Something like "TO_Exter_nal_USB_3.0". When I reboot Unraid, the mount name shows properly and also the volume info is correct. See below screenshot. The 250GB is wrongly identified as 2TB (previous disk had this volume) and you will also see the wrong mountain name. Both will be fixed when I restart Unraid.

 

1845391942_Capture-UDissue.thumb.PNG.c1ba2f329a95c22a3488470bbb1f09bd.PNG

Link to comment

After upgrading to 6.9.0-Beta29 none of my NFS shares will auto mount. Anyone else have this issue? I can post diagnostics if needed.

 

Additional Details

  1. I don't use USB or SMB related devices with with Unassigned Devices
  2. I can mount any of my NFS shares manually using the UD Mount button from the UI
  3. After boot they don't mount automatically, even with the Auto-Mount option enabled
Link to comment
54 minutes ago, ryanhaver said:

After upgrading to 6.9.0-Beta29 none of my NFS shares will auto mount. Anyone else have this issue? I can post diagnostics if needed.

Always post diagnostics.  How can we figure out what is wrong by just being told it doesn't work?

 

Please everyone, post your diagnostics each time you ask for help.  It's delays a resolution to your issue if we have to ask every time for diagnostics.  Support on the forum is mostly provided by volunteers like myself and it's not respectful of the time we donate to help.  Limetech has made the gathering of diagnostics very easy and obscures any private information so it is not exposed.  It's not difficult and goes a long way to providing the information needed to diagnose a problem.

Link to comment
26 minutes ago, ryanhaver said:

Attached are the affected unraid server's diagnostics.

unraid-diagnostics-20201006-1418.zip 138.66 kB · 1 download

This is the issue:

Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Anime' cannot be mounted.
Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/TV Shows' cannot be mounted.
Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/docker' cannot be mounted.
Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Movies' cannot be mounted.
Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Workout' cannot be mounted.
Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Music' cannot be mounted.
Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Books' cannot be mounted.
Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Video' cannot be mounted.
Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/transcode' cannot be mounted.
Oct  6 05:43:02 unRAID unassigned.devices: Remote SMB/NFS server '192.168.1.113' is offline and share '192.168.1.113:/volume2/Photo' cannot be mounted.

Because you can mount the NFS shares manually, the issue is that the Unraid network is not ready when the shares are auto mounted.  I try to have the auto mount of remote shares occur as late as possible in the startup process to give the network enough time to be ready, but in your case it is taking a bit longer.

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.