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

dlandon · December 3, 2021

15 minutes ago, mr2web said:

Ok, that kind of fixed it. but it took a few seconds after loaded the main page for the disk to show up under UD but they do show up eventually so u r on the right track. When refreshing the page its just like it was before the issue started. Great work!!

I need to hit the sack as its quite late over here. I really appreciating the work u do! Keep up the good work and if u like me to test some more please do not hesitate to let me know. :-)

Glad it's working for you. I'll release an update in case anyone else runs into the issue.

dlandon · December 4, 2021

23 minutes ago, wgstarks said:

USB

An external USB shouldn't be getting that warm, but I guess it could under a heavy load.

32 minutes ago, dlandon said:

The problem is that this disk is set to warning=65 critical=70.

Disk temperatures are checked on a polling interval set by poll_attributes in Settings->Disk Settings (every 30 minutes), so it is not an immediate warning message. Because the disk temperature is not shown real time, you can see a disk is hot warning, but when you check the UI it may not be that hot.

As for the temperature not giving the warning at the right temperature, go to the disk setting for this disk and make a change in the temperature settings and re-apply.

wgstarks · December 4, 2021

1 minute ago, dlandon said:

An external USB shouldn't be getting that warm, but I guess it could under a heavy load.

It's a really old disk that I'm using for swap files. It always stays a little warm (55-56). If it continues to be a problem I'll change it out. Seems like I've got old hard drives laying around everywhere.😆

dlandon · December 4, 2021

1 minute ago, wgstarks said:

It's a really old disk that I'm using for swap files. It always stays a little warm (55-56). If it continues to be a problem I'll change it out. Seems like I've got old hard drives laying around everywhere.😆

I have an older USB disk that is showing the same symptom. Starting to overheat when in use. A replacement is not in the budget at this time though.

comet424 · December 4, 2021

i keep getting errors with extneral hot swap .. when i have a ssd swapped in and out.. i keep getting errors for mounting and the only fix is to reboot.. and the unassigned plugin will auto mount.. but any other time it will fail lots... been happening for a while

mitchflix-diagnostics-20211203-2315.zip

mr2web · December 4, 2021

@dlandon Morning. I did the new update u pushed after our troubleshooting session yesterday. This morning I see that I have that warning message still, see attached image. I also see that I had it last night as well after updating the lib.php manually. I was quite tired last night so I must have missed it. Now running UD 2021.12.03. I do see my unassigned devices though.

Edited December 4, 2021 by mr2web

dlandon · December 4, 2021

8 hours ago, comet424 said:

i keep getting errors with extneral hot swap .. when i have a ssd swapped in and out.. i keep getting errors for mounting and the only fix is to reboot.. and the unassigned plugin will auto mount.. but any other time it will fail lots... been happening for a while

mitchflix-diagnostics-20211203-2315.zip 183.99 kB · 0 downloads

Your disk sda1 has errors:

Nov 26 04:41:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6277, flush 0, corrupt 0, gen 0
Nov 26 04:42:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6278, flush 0, corrupt 0, gen 0
Nov 26 04:43:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6279, flush 0, corrupt 0, gen 0
Nov 26 04:44:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6280, flush 0, corrupt 0, gen 0
Nov 26 04:45:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6281, flush 0, corrupt 0, gen 0
Nov 26 04:46:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6282, flush 0, corrupt 0, gen 0
Nov 26 04:47:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6283, flush 0, corrupt 0, gen 0
Nov 26 04:47:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6284, flush 0, corrupt 0, gen 0
Nov 26 04:47:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6285, flush 0, corrupt 0, gen 0
Nov 26 04:47:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6286, flush 0, corrupt 0, gen 0
Nov 26 04:47:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6287, flush 0, corrupt 0, gen 0
Nov 26 04:47:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6288, flush 0, corrupt 0, gen 0
Nov 26 04:47:01 MitchFlix kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 6289, flush 0, corrupt 0, gen 0
Nov 26 04:47:26 MitchFlix emhttpd: spinning down /dev/sda

This appears to be the UD device you are having trouble with. I don't see the SMART report for this disk, probably because of these errors.

Start by updating the latest UD I posted yesterday, then mount the UD disk and click on the check mark next to the mount point and run a disk check to see if the disk can be fixed.

It appears this is a USB disk and you should remove it before rebooting. This device is showing as /dev/sda and this is normally the Unraid flash drive.

dlandon · December 4, 2021

4 hours ago, mr2web said:

@dlandon Morning. I did the new update u pushed after our troubleshooting session yesterday. This morning I see that I have that warning message still, see attached image. I also see that I had it last night as well after updating the lib.php manually. I was quite tired last night so I must have missed it. Now running UD 2021.12.03. I do see my unassigned devices though.

I see a SD card reader installed, but without a SD card installed? It s showing as /dev/sdb so it is not being recognized as having a partition by Linux. Unraid should show it as 'Dev X'.

Post your new diagnostics first, then remove the SD card reader and see if the error stops. Once I get a chance to look at the diagnostics, I'll probably have some tests for you.

While the php error is clear and I see the line in question, I cannot see why the error is happening on that line. Because it's a termination/closing problem - like a missing '}', it may be happening sooner in the code and not showing up until later when the opening and closing braces are not matching. I've had this happen while coding.

comet424 · December 4, 2021

@dlandon

havent tried to your steps yet.. i did do a reboot of the server.... and i dont have phyiscal access i access for my sister so its a remote location...

but i did a reboot no issues with the drive smart shows no errors... and it mounted and syncing her data to the drive she gives me

can u see the smart info? and so you shouldnt reboot a computer with the usb hard drive plugged in?

and ya its a usb ssd 1tb and a 500tb she hot swaps to exchange in a external 2.5 extneral hd bay

and i running 2021.05.01a version

mitchflix-diagnostics-20211204-1343.zip

Edited December 4, 2021 by comet424

trurl · December 5, 2021

5 hours ago, comet424 said:

running 2021.05.01a version

Why?

comet424 · December 5, 2021

why what dlandon said run the latest so i am

sorry for my disliexa i read the wrong one

but i running latest

dlandon · December 5, 2021

6 hours ago, comet424 said:

can u see the smart info?

No, I don't see it in the diagnostics.

6 hours ago, comet424 said:

and so you shouldnt reboot a computer with the usb hard drive plugged in?

It's fine, I just don't think it's a good idea.

comet424 · December 5, 2021

@dlandon here is the smart info for the ssd

mr2web · December 5, 2021

On 12/4/2021 at 1:44 PM, dlandon said:

I see a SD card reader installed, but without a SD card installed? It s showing as /dev/sdb so it is not being recognized as having a partition by Linux. Unraid should show it as 'Dev X'.

Post your new diagnostics first, then remove the SD card reader and see if the error stops. Once I get a chance to look at the diagnostics, I'll probably have some tests for you.

While the php error is clear and I see the line in question, I cannot see why the error is happening on that line. Because it's a termination/closing problem - like a missing '}', it may be happening sooner in the code and not showing up until later when the opening and closing braces are not matching. I've had this happen while coding.

@dlandon Hi, so I have now done three diagnostics dumps for u. one with the SD-card reader in the USB slot, one with the SD-card reader unplugged but no reboot and finally one with the SD-card reader unplugged and after a reboot.

The thing is that that SD-card reader has been plugged into that USB-port for a long time without any problems prior to UA 2021.12.02. The issues and the warning was introduced in the UA 2021.12.02 version for sure. The issues u have already solved with the unassigned disks not showing up under "unassigned disks" on the main page. Thanks again foe that. still have the warning to solve though.

Let me know if u need anything else or if u like me to test anything.

serverbrain3-diagnostics-20211205-1412_with_SD-card_reader.zip serverbrain3-diagnostics-20211205-1416_without_SD-card_reader_NO_REBOOT.zip serverbrain3-diagnostics-20211205-1420_without_SD-card_reader_AFTER_REBOOT.zip

dlandon · December 5, 2021

This is the issue with your php error:

Dec  3 17:21:03 Serverbrain3 unassigned.devices: Disk with serial 'KINGSTON_SA2000M8500G_50026B728269650F', mountpoint 'KINGSTON_SA2000M8500G_50026B728269650F-part1' is not set to auto mount.
Dec  3 17:21:03 Serverbrain3 emhttpd: Warning: syntax error, unexpected end of file, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in Unknown on line 31
Dec  3 17:21:03 Serverbrain3 emhttpd:  in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1942
Dec  3 17:21:03 Serverbrain3 unassigned.devices: Disk '/dev/nvme0n1' does not have a serial number and cannot be mounted.

The nvme disk has two partitions. Partition 1 is a vfat file system. There is no partition 2. Partition 3 has no file system. UD is apparently having an issue with no partition 2.

I have added some debug. Copy the attached file to /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned. Then unmount and remount the nvme disk. Post the log.

rc.unassigned.zip

mr2web · December 5, 2021

28 minutes ago, dlandon said:
This is the issue with your php error:
Dec  3 17:21:03 Serverbrain3 unassigned.devices: Disk with serial 'KINGSTON_SA2000M8500G_50026B728269650F', mountpoint 'KINGSTON_SA2000M8500G_50026B728269650F-part1' is not set to auto mount.
Dec  3 17:21:03 Serverbrain3 emhttpd: Warning: syntax error, unexpected end of file, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in Unknown on line 31
Dec  3 17:21:03 Serverbrain3 emhttpd:  in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1942
Dec  3 17:21:03 Serverbrain3 unassigned.devices: Disk '/dev/nvme0n1' does not have a serial number and cannot be mounted.
The nvme disk has two partitions. Partition 1 is a vfat file system. There is no partition 2. Partition 3 has no file system. UD is apparently having an issue with no partition 2.

I have added some debug. Copy the attached file to /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned. Then unmount and remount the nvme disk. Post the log.

rc.unassigned.zip 3.54 kB · 0 downloads

Attached is the diagnostics file after mounting the nvme disk then unmounting it. This is a disk I HW passthrough to a WIN10 VM that utilises the partition 1. Naturally I should sort the partitions on this disk but it has been working just fine for a long time as it is.

I'll be AFK for a few hours so, sry 4 not being able to respond quickly during those hours.

serverbrain3-diagnostics-20211205-1507_debug_MONUNT_then_UNMOUNT_nvme_disk_UA_2021.12.03.zip

Edited December 5, 2021 by mr2web

dlandon · December 5, 2021

12 minutes ago, mr2web said:

Attached is the diagnostics file after mounting the nvme disk then unmounting it. This is a disk I HW passthrough to a WIN10 VM that utilises the partition 1. Naturally I should sort the partitions on this disk but it has been working just fine for a long time as it is.

I'll be AFK for a few hours so, sry 4 not being able to respond quickly during those hours.

serverbrain3-diagnostics-20211205-1507_debug_MONUNT_then_UNMOUNT_nvme_disk_UA_2021.12.03.zip 127.75 kB · 0 downloads

If you are passing it through to a VM, mark the disk as passed through so UD ignores the disk.

mr2web · December 5, 2021

3 hours ago, dlandon said:

If you are passing it through to a VM, mark the disk as passed through so UD ignores the disk.

@dlandon No, that is what I do not like to do as I plan to use the partition 3 for storage outside the array and this should not be auto-mounted, I'll mount it when I need access to the storage. The VM is mostly not running. I need UD to mount the partition whenever I need to. This is one of the main features that I appreciate a lot from UD to be able to mount partitions when needed even though I pass them through to VMs at times. 🙂

dlandon · December 5, 2021

4 minutes ago, mr2web said:

@dlandon No, that is what I do not like to do as I plan to use the partition 3 for storage outside the array and this should not be auto-mounted, I'll mount it when I need access to the storage. The VM is mostly not running. I need UD to mount the partition whenever I need to. This is one of the main features that I appreciate a lot from UD to be able to mount partitions when needed even though I pass them through to VMs at times. 🙂

Be sure you don't mount partitions in the VM and with UD at the same time. You will cause corruption.

I'm trying to reproduce your issue, but have not had any luck so far.

Shane1234 · December 5, 2021

Hello! I'm having trouble mounting a disk in the UD plugin. It's a WD Purple 4TB hard drive, pulled from an NVR.

I have it connected via SATA on the ASROCK MB, and unraid sees it

I ran preclear on it twice, with no problems.

There is a partition (CCTV) that I am unable to remove. (trying results in a "FAIL" error message.

There is a MOUNT button present, but it is grayed out

Destructive mode IS ENABLED

I want to use this disk as a stand-alone, not attached to the array, but I can't format or mount it.

Any ideas what I can try? Thanks!

image.png.fa68705d406fa6075e5d60a0ecdbf821.png

From unraid log:

Dec 5 11:40:25 unraid ool www[4301]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'apply'

Dec 5 11:40:25 unraid unassigned.devices: Updating share settings...

Dec 5 11:40:25 unraid unassigned.devices: Share settings updated.

Dec 5 11:40:37 unraid ool www[9732]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'apply'

Dec 5 11:40:37 unraid unassigned.devices: Updating share settings...

Dec 5 11:40:37 unraid unassigned.devices: Share settings updated.

Dec 5 11:41:39 unraid unassigned.devices: Refreshed Disks and Configuration.

Dec 5 11:41:39 unraid kernel: sdf: sdf1

Dec 5 11:41:39 unraid rc.diskinfo[10874]: SIGHUP received, forcing refresh of disks info.

Dec 5 11:41:39 unraid unassigned.devices: Adding disk '/dev/sdf1'...

Dec 5 11:41:39 unraid unassigned.devices: Mounting partition '/dev/sdf1' at mountpoint '/mnt/disks/CCTV'...

Dec 5 11:41:39 unraid unassigned.devices: No filesystem detected on '/dev/sdf1'.

Dec 5 11:41:39 unraid unassigned.devices: Partition 'WDC_WD40PURX-64NZ6Y0_WD-WCC7K6RRSKU5' cannot be mounted.

Dec 5 11:44:17 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'.

Dec 5 11:44:17 unraid unassigned.devices: Remove partition failed: 'Error: Partition doesn't exist. '.

Dec 5 11:44:17 unraid rc.diskinfo[10874]: SIGHUP received, forcing refresh of disks info.

Dec 5 11:44:43 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'.

Dec 5 11:44:43 unraid unassigned.devices: Remove partition failed: 'Error: Partition doesn't exist. '.

Dec 5 11:44:43 unraid rc.diskinfo[10874]: SIGHUP received, forcing refresh of disks info.

Dec 5 11:45:36 unraid emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdf

Dec 5 12:16:13 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'.

Dec 5 12:16:13 unraid unassigned.devices: Remove partition failed: 'Error: Partition doesn't exist. '.

Dec 5 12:16:14 unraid rc.diskinfo[10874]: SIGHUP received, forcing refresh of disks info.

Dec 5 12:17:57 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'.

Dec 5 12:17:57 unraid unassigned.devices: Remove partition failed: 'Error: Partition doesn't exist. '.

Dec 5 12:17:57 unraid rc.diskinfo[10874]: SIGHUP received, forcing refresh of disks info.

From Disk log:

Dec 4 13:51:41 unraid kernel: ata5: SATA max UDMA/133 abar m131072@0xfb680000 port 0xfb680300 irq 56
Dec 4 13:51:41 unraid kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 4 13:51:41 unraid kernel: ata5.00: ATA-10: WDC WD40PURX-64NZ6Y0, WD-WCC7K6RRSKU5, 80.00A80, max UDMA/133
Dec 4 13:51:41 unraid kernel: ata5.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Dec 4 13:51:41 unraid kernel: ata5.00: configured for UDMA/133
Dec 4 13:51:41 unraid kernel: sd 5:0:0:0: [sdf] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Dec 4 13:51:41 unraid kernel: sd 5:0:0:0: [sdf] 4096-byte physical blocks
Dec 4 13:51:41 unraid kernel: sd 5:0:0:0: [sdf] Write Protect is off
Dec 4 13:51:41 unraid kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Dec 4 13:51:41 unraid kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 4 13:51:41 unraid kernel: sdf: sdf1
Dec 4 13:51:41 unraid kernel: sd 5:0:0:0: [sdf] Attached SCSI disk
Dec 4 13:52:32 unraid emhttpd: WDC_WD40PURX-64NZ6Y0_WD-WCC7K6RRSKU5 (sdf) 512 7814037168
Dec 4 13:52:32 unraid emhttpd: read SMART /dev/sdf
Dec 4 13:58:20 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'.
Dec 4 14:06:00 unraid emhttpd: read SMART /dev/sdf
Dec 4 14:08:44 unraid emhttpd: read SMART /dev/sdf
Dec 4 14:09:04 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'.
Dec 4 14:09:31 unraid unassigned.devices: Adding disk '/dev/sdf1'...
Dec 4 14:09:31 unraid unassigned.devices: Mounting partition '/dev/sdf1' at mountpoint '/mnt/disks/CCTV'...
Dec 4 14:09:31 unraid unassigned.devices: No filesystem detected on '/dev/sdf1'.
Dec 4 15:22:00 unraid preclear_disk_WD-WCC7K6RRSKU5[17680]: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 1 --frequency 1 --cycles 1 --skip-preread --skip-postread --no-prompt /dev/sdf
Dec 4 15:22:02 unraid preclear_disk_WD-WCC7K6RRSKU5[17680]: Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=2097152 count=4000784932864 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Dec 5 11:41:39 unraid kernel: sdf: sdf1
Dec 5 11:41:39 unraid unassigned.devices: Adding disk '/dev/sdf1'...
Dec 5 11:41:39 unraid unassigned.devices: Mounting partition '/dev/sdf1' at mountpoint '/mnt/disks/CCTV'...
Dec 5 11:41:39 unraid unassigned.devices: No filesystem detected on '/dev/sdf1'.
Dec 5 11:44:17 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'.
Dec 5 11:44:43 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'.
Dec 5 12:16:13 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'.
Dec 5 12:17:57 unraid unassigned.devices: Removing partition '1' from disk '/dev/sdf'

mr2web · December 5, 2021

2 hours ago, dlandon said:

Be sure you don't mount partitions in the VM and with UD at the same time. You will cause corruption.

I'm trying to reproduce your issue, but have not had any luck so far.

@dlandon I haven't tested with UD 2021.12.03, but with previous versions the disk is no longer visual under Unassigned Devices on the main page as soon as I start my VM. So not very easy to double mount the disk. This behaviour has been great so far! 🙂

dlandon · December 5, 2021

1 hour ago, Shane1234 said:

I want to use this disk as a stand-alone, not attached to the array, but I can't format or mount it.

Any ideas what I can try? Thanks!

How did that partition get created? UD can't deal with the partition layout. There are some manual ways to remove all partitions from the disk. UD can't do that because it can only remove partitions, and not clear the complete disk because of the risk of removing partitions it shouldn't. Maybe @JorgeB can offer some help.

dlandon · December 5, 2021

27 minutes ago, mr2web said:

I haven't tested with UD 2021.12.03, but with previous versions the disk is no longer visual under Unassigned Devices on the main page as soon as I start my VM.

That's not the normal behavior, so I don't know how that's happening for you. The reason for the "Passed Through" setting on a UD disk is so UD will leave it alone and not offer the option to mount the disk, nor auto mount the disk.

mr2web · December 5, 2021

40 minutes ago, dlandon said:

That's not the normal behavior, so I don't know how that's happening for you. The reason for the "Passed Through" setting on a UD disk is so UD will leave it alone and not offer the option to mount the disk, nor auto mount the disk.

@dlandon Ok, I have had it set up like this for quite a few years without any issues. I did follow a tutorial made by Spaceinvader One at the time of setting up that VM. I have tested with UD 2021.12.03 and it has the same lovely behaviour as it always have had; whilst the VM is up and running the disk is not visual under Unassigned Devices on the main page. as soon as the VM is no longer running then the disk is available under Unassigned Devices on the main page and one can operate on the disk using UD plugin as any other disk that is unassigned.

Prior to 2021.12.03 all was working very smooth and I did not experience any warning message like I do now. I know and I understand that a rollback is not an option. Would diffing the two versions give any guidance where the current 2021.12.03 do things differently than its presessor narrowing it down to find the problematic part of the code responsible for the warning message?

dlandon · December 5, 2021

3 minutes ago, mr2web said:

Would diffing the two versions give any guidance where the current 2021.12.03 do things differently than its presessor narrowing it down to find the problematic part of the code responsible for the warning message?

Way too many changes for that to be practical.

I've been working on some changes that I'd like you to try. I cannot reproduce your issue. I've been trying to create a disk layout that would cause the problem, but I can't make it happen.

Copy the attached file to /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned and see if the error still shows up. Give me some diagnostics after that.

rc.unassigned.zip

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

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

dlandon

dlandon

dlandon

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation