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


Recommended Posts

5 hours ago, heffe2001 said:

Also, is there a reason you can't mount a drive in UD wherever you want (I believe this was the old behavior), and not be forced to mount them in /mnt/disks/ ?  Or would it be possible to make that a toggleable feature?

That was changed years ago.  The issue was that people that were not tech savy were mounting devices all over the place and causing a lot of support issues.

 

I'll take a look at your diagnostics later when I have some time.

Link to comment
6 hours ago, heffe2001 said:

I'm having the same issue.  I have 2 SAS SSD's installed that were showing up, I tried to add another drive to that controller and it wouldn't show up, so I tried restarting the server just to see if the controller could even see the drive (it didn't, drive is definitely bad, but it does still see the 2 SAS SSD's).  On restart, Unassigned Devices can't see those 2 SAS drives now, but you can find them in the '/dev/disk/by-id' to identify them, and even manually mount them if you want (both contain XFS partitions, one I'm using for my plex transcoding cache, and the other I'm going to use for my Docker appdata).  I can always edit the go file to mount those 2 drives where they need to be by their 'by-id' info (just in case them move from their 'sd?' designation), but they WERE working in UD, but it will NOT see them now (through about 4 boots so far, and this damned HP DL380p-G8 takes forever to reboot, lol).  I'm going to attach my current diagnostics to this post.  Also, is there a reason you can't mount a drive in UD wherever you want (I believe this was the old behavior), and not be forced to mount them in /mnt/disks/ ?  Or would it be possible to make that a toggleable feature?

media01-diagnostics-20200505-0102.zip 189.16 kB · 1 download

Are these the disks you are having trouble with?

May  5 00:55:29 media01 kernel: sd 3:0:0:0: [sdd] tag#1432 Sense Key : 0x1 [current] 
May  5 00:55:29 media01 kernel: sd 3:0:0:0: [sdd] tag#1432 ASC=0x1c ASCQ=0x2 
May  5 00:55:29 media01 kernel: sd 3:0:2:0: [sdf] tag#1436 Sense Key : 0x1 [current] 
May  5 00:55:29 media01 kernel: sd 3:0:2:0: [sdf] tag#1436 ASC=0x1c ASCQ=0x2 
May  5 01:01:11 media01 emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
May  5 01:02:36 media01 kernel: sd 3:0:2:0: [sdf] tag#433 Sense Key : 0x1 [current] 
May  5 01:02:36 media01 kernel: sd 3:0:2:0: [sdf] tag#433 ASC=0x1c ASCQ=0x2 
May  5 01:02:36 media01 kernel: sd 3:0:0:0: [sdd] tag#334 Sense Key : 0x1 [current] 
May  5 01:02:36 media01 kernel: sd 3:0:0:0: [sdd] tag#334 ASC=0x1c ASCQ=0x2 

 

Link to comment

Those would be the ones.  The've been giving those 2 warnings since installation, but have worked without issue up to now (and still seem to work ok when I manually mount them).  UD won't actually see any of the scsi- devices (I have a couple raid arrays set up on a hp 420 controller that I use directly mapped to a windows VM, but it didn't see them before I mapped them either).

 

Looks like it's basically not finding a grown defect list by that 'error':

 

0x1C 0x02  GROWN DEFECT LIST NOT FOUND

 

 

It's not seeing any of these devices:

 


scsi-HUSMM1640ASS200_0QV1M8XA@        scsi-LOGICAL_VOLUME_001438033715B80-part1@  scsi-ST31000424SS_9WK2N0XS00009120NV0P-part1@
scsi-HUSMM1640ASS200_0QV1M8XA-part1@  scsi-LOGICAL_VOLUME_001438033715B80-part2@  scsi-ST6000NM0034_Z4D2NK0X0000R545W10B@
scsi-HUSMM1640ASS200_0QV1NH7A@        scsi-LOGICAL_VOLUME_001438033715B80-part3@  scsi-ST6000NM0034_Z4D2NK0X0000R545W10B-part1@
scsi-HUSMM1640ASS200_0QV1NH7A-part1@  scsi-LOGICAL_VOLUME_001438033715B80-part4@
scsi-LOGICAL_VOLUME_001438033715B80@  scsi-ST31000424SS_9WK2N0XS00009120NV0P@

I'd forgotten about even putting that ST6000 in there at all, since neither the system nor the UD detected it, lol.

 

 

 

 

Edited by heffe2001
Link to comment
1 hour ago, heffe2001 said:

Those would be the ones.  The've been giving those 2 warnings since installation, but have worked without issue up to now (and still seem to work ok when I manually mount them).  UD won't actually see any of the scsi- devices (I have a couple raid arrays set up on a hp 420 controller that I use directly mapped to a windows VM, but it didn't see them before I mapped them either).

 

Looks like it's basically not finding a grown defect list by that 'error':

 

0x1C 0x02  GROWN DEFECT LIST NOT FOUND

 

 

It's not seeing any of these devices:

 


scsi-HUSMM1640ASS200_0QV1M8XA@        scsi-LOGICAL_VOLUME_001438033715B80-part1@  scsi-ST31000424SS_9WK2N0XS00009120NV0P-part1@
scsi-HUSMM1640ASS200_0QV1M8XA-part1@  scsi-LOGICAL_VOLUME_001438033715B80-part2@  scsi-ST6000NM0034_Z4D2NK0X0000R545W10B@
scsi-HUSMM1640ASS200_0QV1NH7A@        scsi-LOGICAL_VOLUME_001438033715B80-part3@  scsi-ST6000NM0034_Z4D2NK0X0000R545W10B-part1@
scsi-HUSMM1640ASS200_0QV1NH7A-part1@  scsi-LOGICAL_VOLUME_001438033715B80-part4@
scsi-LOGICAL_VOLUME_001438033715B80@  scsi-ST31000424SS_9WK2N0XS00009120NV0P@

I'd forgotten about even putting that ST6000 in there at all, since neither the system nor the UD detected it, lol.

Remove the preclear plugin and see if it makes a difference.  What does the UD page show?

 

The ST6000 seems to be having a lot of read issues - look at the SMART report.

Link to comment

With Preclear removed it still shows the same (none of the SCSI- drives are listed).  I'll look at the ST6000, it's not been used and I honestly can't even remember buying it let alone installing it, lol.  I do have the dynamix SCSI Devices plugin installed from when I had an Areca controller in the machine (long since removed).  I wonder if that's got anything to do with the issues?  I may try uninstalling it soon as my docker restore is done and restarting the machine to see if it makes any difference.

 

 

image.thumb.png.7f18a9349cb5c88efd21a92f0460d5b7.png

Link to comment

After removing that dynamix SCSI devices plugin I get the desired results..  SO if anybody is having the issue of SAS drives (or raid containers) not showing up on UD, and have that dynamix plugin installed (and aren't using a Areca controller), try removing it and see if it helps.

image.thumb.png.47ce90e6c22d1783b38a5401d93f5d69.png

Link to comment
22 minutes ago, DarkMan83 said:

Heyho folks,

 

today after restarting the server i get the following, which tells me nothing from user perspective...

unassinged-devices-warning.thumb.JPG.22b9d0070c4f40f03118aab84ce8fc99.JPG

You appear to have a corruption in your /config/plugins/unassigned.devices/unassigned.devices.cfg file.

 

Several options:

  • Reboot server to see if it clears up.  That file is copied to ram disk and it may have been corrupted.
  • Remove the unassigned.devices.cfg file and reboot.  You will have to re-do any UD mounted disks.

If it does not clear up, you'll need to shutdown the server and put your flash drive in another computer and check for issues.

Link to comment
25 minutes ago, dlandon said:

You appear to have a corruption in your /config/plugins/unassigned.devices/unassigned.devices.cfg file.

 

Several options:

  • Reboot server to see if it clears up.  That file is copied to ram disk and it may have been corrupted.
  • Remove the unassigned.devices.cfg file and reboot.  You will have to re-do any UD mounted disks.

If it does not clear up, you'll need to shutdown the server and put your flash drive in another computer and check for issues.

Thanks, deleting the file + restart worked 🙂

Link to comment

I have an IPsec VPN setup between sites and mount a remote NFS share from UnRaid using the UD plugin. I use this for remote backups. This works great 99% of the time. Occasionally there is a network issue and the NFS share is no longer accessible. It seems like the system pings the remote system to confirm the share is still active and if it fails it takes the share offline. Then both the UD plugin and UR act strange. Once here the only way to fix it is a full system reboot. The strange behavior I see is if I try to use UD to unmount or remount the share the system just hangs. If I do a simple 'ls' command in the /mnt/disks folder the terminal just hangs as well. It doesn't happen daily, so a full system reboot isn't the end of the world but it is still annoying. Hopefully I am just missing something and there is an easy fix.

 

1. Is there a way to force UD to retry a NFS mount after a previous failure?

2. Is there a way to reload just the UD plugin without a full system reboot?

3. Is there a better way to mount this remote NFS share that is more tolerant of network hiccups?

 

Thanks,

Link to comment

Hi guys, 

 

Noob here, but could anyone tell me what the green dot means in this context?  I'm preclearing my drives before setting up an array.  The two 1tb drives have already been precleared.  I started the preclear process on the 3 4tb drives, and one of the 1tb drives lights up green.  What do the indicators mean in this context.  I don't think there's necessarily a problem, but I don't understand what it's telling me here.  

 

Thanks!  

 

939975925_2020-05-0610_28_40-173_172_115.60_4001-RemoteDesktopConnection.thumb.png.cc1e29d6ee8de23f24f4b3b9d65b1a5d.png

Link to comment
7 hours ago, PJPorch said:

1. Is there a way to force UD to retry a NFS mount after a previous failure?

2. Is there a way to reload just the UD plugin without a full system reboot?

UD mounts the remote mount, but has no control over the operation of the NFS share.  Linux manages the remote share.  UD does not unmount the share if the server goes off-line.  With that said, please post diagnostics when this happens and I'll see if here is more that can be done to prevent hangs.

Link to comment
1 hour ago, ScoopGP said:

I started the preclear process on the 3 4tb drives, and one of the 1tb drives lights up green.

That indicates that the disk is spun up.  When a disk is preclearing, UD does not scan to see if the disk is spun up so it doesn't interfere with the preclear. 

Link to comment
4 hours ago, dlandon said:

UD mounts the remote mount, but has no control over the operation of the NFS share.  Linux manages the remote share.  UD does not unmount the share if the server goes off-line.  With that said, please post diagnostics when this happens and I'll see if here is more that can be done to prevent hangs.

It only happens maybe once per month, but I will try to capture the diagnostics when it does. That or I might try to recreate it by blocking the rsync ports over the VPN to force it.

 

Thanks,

Link to comment

After unmounting a drive, I'm getting this error:

May 7 21:37:10 server kernel: usb 2-4: USB disconnect, device number 2
May 7 21:37:10 server kernel: sd 9:0:0:0: [sdh] Synchronizing SCSI cache
May 7 21:37:10 server kernel: sd 9:0:0:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00

Just wanna make sure that I'm not doing anything wrong, what's SCSI cache here? I assume this has nothing to do with my Unraid cache but...

Link to comment
On 5/7/2020 at 10:33 PM, dnLL said:

After unmounting a drive, I'm getting this error:


May 7 21:37:10 server kernel: usb 2-4: USB disconnect, device number 2
May 7 21:37:10 server kernel: sd 9:0:0:0: [sdh] Synchronizing SCSI cache
May 7 21:37:10 server kernel: sd 9:0:0:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00

Just wanna make sure that I'm not doing anything wrong, what's SCSI cache here? I assume this has nothing to do with my Unraid cache but...

Post diagnostics,

Link to comment
29 minutes ago, dnLL said:

Your log is loaded with this:

May  9 08:35:32 server xinetd[7472]: START: check_mk pid=19280 from=10.1.1.21
May  9 08:35:35 server rpcbind[19937]: connect from 127.0.0.1 to getport/addr(mountd)
May  9 08:35:35 server xinetd[7472]: EXIT: check_mk status=0 pid=19280 duration=3(sec)
May  9 08:37:32 server xinetd[7472]: START: check_mk pid=23909 from=10.1.1.21
May  9 08:37:35 server rpcbind[24568]: connect from 127.0.0.1 to getport/addr(mountd)
May  9 08:37:35 server xinetd[7472]: EXIT: check_mk status=0 pid=23909 duration=3(sec)
May  9 08:39:32 server xinetd[7472]: START: check_mk pid=28608 from=10.1.1.21
May  9 08:39:36 server rpcbind[29220]: connect from 127.0.0.1 to getport/addr(mountd)
May  9 08:39:36 server webGUI: Successful login user root from 10.30.1.2
May  9 08:39:36 server xinetd[7472]: EXIT: check_mk status=0 pid=28608 duration=4(sec)

You need to get the check_mk application under control and stop the excessive logging.  I can't scan your log for anything meaningful with all that useless logging.

 

sdh was not connected when you produced the diagnostics.  I'd leave the disk attached for a minute or two to let the cache flush before disconnecting the device.  I'll take a look at doing a sync before a device is unmounted and see if this can help.

 

Link to comment
19 minutes ago, dlandon said:

Your log is loaded with this:


May  9 08:35:32 server xinetd[7472]: START: check_mk pid=19280 from=10.1.1.21
May  9 08:35:35 server rpcbind[19937]: connect from 127.0.0.1 to getport/addr(mountd)
May  9 08:35:35 server xinetd[7472]: EXIT: check_mk status=0 pid=19280 duration=3(sec)
May  9 08:37:32 server xinetd[7472]: START: check_mk pid=23909 from=10.1.1.21
May  9 08:37:35 server rpcbind[24568]: connect from 127.0.0.1 to getport/addr(mountd)
May  9 08:37:35 server xinetd[7472]: EXIT: check_mk status=0 pid=23909 duration=3(sec)
May  9 08:39:32 server xinetd[7472]: START: check_mk pid=28608 from=10.1.1.21
May  9 08:39:36 server rpcbind[29220]: connect from 127.0.0.1 to getport/addr(mountd)
May  9 08:39:36 server webGUI: Successful login user root from 10.30.1.2
May  9 08:39:36 server xinetd[7472]: EXIT: check_mk status=0 pid=28608 duration=4(sec)

You need to get the check_mk application under control and stop the excessive logging.  I can't scan your log for anything meaningful with all that useless logging.

 

sdh was not connected when you produced the diagnostics.  I'd leave the disk attached for a minute or two to let the cache flush before disconnecting the device.  I'll take a look at doing a sync before a device is unmounted and see if this can help.

 

I can do a test tonight, mount the drive, do some writes, unmount it and wait 5 minutes before unplugging. I did unplug it like 10 seconds after unmounting. So yea, maybe syncing before unmounting would help, I don't mind doing some tests with you if need be.

 

As for Check_MK... well, it's my monitoring solution, I should probably tune syslog to filter out these infos, but it's not a Check_MK problem per se, it's just the way syslog is configured on Unraid with xinetd. It can definitely be filtered but I never really saw any reason to do it, logrotate does its job and I can just egrep -v xinetd|rpcbind if that bothers me that much while looking at logs. With that said, I'll look into it as it is, like you said, useless logging =).

Link to comment
43 minutes ago, dnLL said:

As for Check_MK... well, it's my monitoring solution, I should probably tune syslog to filter out these infos, but it's not a Check_MK problem per se, it's just the way syslog is configured on Unraid with xinetd. It can definitely be filtered but I never really saw any reason to do it, logrotate does its job and I can just egrep -v xinetd|rpcbind if that bothers me that much while looking at logs. With that said, I'll look into it as it is, like you said, useless logging =).

I didn't see the logging as a problem necessarily with the check_mk app, it just loads the log with useless info and makes it hard to browse.  Does it really need to scan that often?  3-4 secs?  Wouldn't every five or ten minutes be enough?

 

I did a quick test with an ata docking station on my test server.  Hot plugging a drive and then removing it without mounting it causes the log entries you are seeing.  I've not seen this issue on a USB disk though.  I'd say it's not a problem.

Link to comment
10 minutes ago, dlandon said:

I didn't see the logging as a problem necessarily with the check_mk app, it just loads the log with useless info and makes it hard to browse.  Does it really need to scan that often?  3-4 secs?  Wouldn't every five or ten minutes be enough?

 

I did a quick test with an ata docking station on my test server.  Hot plugging a drive and then removing it without mounting it causes the log entries you are seeing.  I've not seen this issue on a USB disk though.  I'd say it's not a problem.

It is a USB drive that was causing the "error". I don't think it's particularly a big issue either but at the same time I hate ignoring error messages so I decided to post here just in case.

 

Check_MK by default poke every host every minute, I changed it to 2 minutes. Yes, I like having detailed information about what's happening with my VMs, dockers and physical hardwares such as my server, my pfsense router, my printer and so on very often. the big adavantage of check_mk is data aggregation, it produces charts that are good for 400 days with a very minimal amount of disk space needed. It's just not as "live" as some other monitoring solutions, I can miss CPU spikes within those 2 minutes, but it's accurate enough for my needs. It also scans my logfiles... so check_mk is the reason why I saw that error in syslog and why I'm here now. I can just filter it out in check_mk itself. I added a conf file for rsyslog to discard the useless messages however, UserScripts will create the conf file on every start and restart rsyslog. Anyways, that's beyond the scope of this thread.

Edited by dnLL
Link to comment
On 6/26/2019 at 4:15 AM, Marshalleq said:

Does anyone know if there is a way to get disk io from the attached unassigned devices?  I'd really like to be able to visually see real time so I can guage the amount of writing to my attached SSD's.

 

Thanks.

I would also really like to be able to view disk I/O for unassigned devices, ideally in the dashboard the same way we can see it for array disks/cache.  Is this possible?  If not in the dashboard what other ways can I monitor this in real-time?

Link to comment

I'm currently on UD v2020.04.27 and have been trying to mount a Bitlocker protected drive for the first time. I'm not capable of selecting a drive for the "encrypted disk" settings in either Firefox nor Edge at the moment. Could this be a bug with the drop down menu? I can't seem to mount the disk without the password beforehand either.

 

 

 

 

Untitled.png

Link to comment
  • trurl pinned this topic

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.