dlandon

Do the following: Copy the attached lib.php file to /usr/local/emhttp/plugins/unassigned.devices/include/lib.php. Click on the double arrows in the upper right corner of the UD GUI. This will refresh udev. Type this at the command line: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned mount auto Let me know if this takes care of the warning. lib.zip

Give me the output of this command: cat /var/state/unassigned.devices/unassigned.devices.ini

Remove the preclear plugin and see if it goes away.

I don't see the error in your log.

No. Just 'dev1'. The Unraid page is where you work with UD devices. Click on the help icon (question mark in the circle) in the upper right of the page. Do you know how to enable the help in Unraid?

Yes. Go to the UD page and click on help. Scroll down and you'll see the rc.unassigned commands.

Read the post just above this one.

Use the 'devX' designation. It does not change when rebooting. i.e. a device showing in UD as 'Dev 1' would be 'dev1' in your script. As you found out the sdX designations can change on reboot.

Update to the latest version I released today and see if the issue is fixed. I have added the ability for some debug so we can continue to work on solving your issue.

I'm not sure you copied the file. You have to unzip the file before copying.

How does this happen?

Can you give me a link to that tutorial?

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

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.

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.

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.

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

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

You can click on the Docker Container icon and select 'WebUI'. This will take you to the LMS web UI. The WebUI is at ip:9000.

No, I don't see it in the diagnostics. It's fine, I just don't think it's a good idea.

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.

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.

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.

An external USB shouldn't be getting that warm, but I guess it could under a heavy load. 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.

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