-
Posts
10,283 -
Joined
-
Last visited
-
Days Won
20
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by dlandon
-
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.
-
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.
-
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.
-
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.
-
Here is what I see: 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. Dec 3 17:21:03 Serverbrain3 unassigned.devices: Disk with serial 'KINGSTON_SA2000M8500G_50026B728269650F', mountpoint 'KINGSTON_SA2000M8500G_50026B728269650F-part3' is not set to auto mount. It doesn't look like udev is finding a serial number on the disk /dev/nvme0n1. See if the serial number shows on the base Unraid unassigned disks page. As for the php error, it's not very graceful when udev doesn't provide the information requested. Before you reboot the server go to a command line and give me the output of this command: /sbin/udevadm info --query=property --path $(/sbin/udevadm info -q path -n /dev/nvme0n1) I'll try to come up with a graceful way of handling this rather that a php error showing up.
-
I do realize this is a php error, but I see nothing at that line. Another person had an issue with UD showing disks using Safari and I wanted to be sure that was not happening for you. I'll take a look at the diagnostics, but has anything changed on your server? I have been working on lib.php so those are the changes you are seeing. The area where this error is occurring has not been touched lately and I can't reproduce the issue. Can you remove the UD plugin and see if the disks show up in the base OS as unassigned disks?