dlandon

Show the output of this command: /sbin/udevadm info --query=property --path $(/sbin/udevadm info -q path -n /dev/nvme1n1p3)

You don't need to pass through the UD disk to do that. Just mount the disk and copy files from /mnt/disks/... All pass through does is to tell UD to not do any operations on the disk.

You have a partition 3 that is causing UD to choke. There is no file system on partition 3. Can I get you to upgrade to 6.11.5? There are better diagnostics that will help me understand why UD is choking on partition 3. If you are willing to upgrade, give me new diagnostics.

Passed through means that a VM or Docker is mounting and working with the disk. If UD also mounts the device, you wil corrupt the file system. Because this is an invalid condition, UD now prevents passing through a mounted disk. Why do you want to pass through a mounted disk?

6.12 is highlighting a lot of php warnings because of the update to php 8. While the warnings are not fatal, they are very messy in their presentation - all over the UI potentially. Those of us with core plugins are just trying to prepare for a public release. That being said, some plugin authors may experience plugins that no longer work and they will need to make some adjustments. This has been rare that a plugin no longer works. Plugin authors will be able to work with one of the beta releases so they can sort out any issues with plugins.

No, reboot. I have added an indicator on the orb on a Historical device in this situation. If the disk can be attached, the orb will show green. Edit: I'm making a change so the red 'X' (delete Historical Device) will be disabled when a disk can be re-attached.

You can re-attach it with Historical Devices, or remove the disk and hot plug it back.

Are you detaching the disk? Feb 5 20:33:51 Tower ool www[14136]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned 'detach' 'sdp' 'true' Feb 5 20:33:51 Tower kernel: sd 10:0:0:0: [sdp] Synchronizing SCSI cache Feb 5 20:33:51 Tower kernel: sd 10:0:0:0: [sdp] Stopping disk Feb 5 20:33:54 Tower ool www[14154]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned 'detach' 'sdp' 'true' Feb 5 20:33:55 Tower kernel: ata5.00: disable device Feb 5 20:33:55 Tower unassigned.devices: Device 'sdp' has been detached. Feb 5 20:34:11 Tower ool www[14146]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned 'attach' 'Samsung_SSD_870_QVO_2TB_.....' Detaching the disk puts it offline.

UD thinks it's offline, so something is indicating to UD it's no longer connected. As I said, marking a disk as passed through only changes the 'Mount' button indicator to 'Passed'. UD does not put the disk offline. If you delete it from the Historical Devices, it will show up again when UD sees it online. It will not be marked as passed through. Post diagnostics if you want me to look into it further.

Is it showing up in the Historical devices? If you set a disk to passed through, it only sets the "Mount" button to "Passed". It does not hide the disk from view. Post diagnostics and tell me which disk you are not seeing when set to passed through.

Post a screen shot of the UD page.

Something is not quite right with your UD disk(s): Feb 3 20:37:44 Tower unassigned.devices: Disk with ID 'Samsung_SSD_970_EVO_Plus_2TB_S4J4NZFNC00208H (nvme1n1)' is not set to auto mount. Feb 3 20:37:44 Tower unassigned.devices: Disk with ID 'Samsung SSD 970 EVO Plus 2TB_S4J4NZFNC00208H (nvme1n1)' is not set to auto mount. Feb 3 20:37:44 Tower unassigned.devices: PHP Warning: syntax error, unexpected TC_CONSTANT in Unknown on line 24 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 2750 Feb 3 20:37:44 Tower unassigned.devices: PHP Warning: array_keys() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned on line 69 Feb 3 20:37:44 Tower unassigned.devices: PHP Warning: array_map(): Expected parameter 2 to be an array, null given in /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned on line 69 Feb 3 20:37:44 Tower unassigned.devices: PHP Warning: implode(): Invalid arguments passed in /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned on line 69 Feb 3 20:37:44 Tower unassigned.devices: Disk with ID 'Samsung SSD 970 EVO Plus 2TB_S4J4NZFNC00208H (nvme1n1)' is not set to auto mount. The 'Samsung_SSD_970_EVO_Plus_2TB_S4J4NZFNC00208H (nvme1n1)' is trying to auto mount multiple times. The disk should only be found once. The php errors are from the info missing or invalid. Show a screen shot of the UD page when the disks are all being displayed. Also go to the UD settings and set 'Debug Log Level:' to "Udev and Hotplug'. Reboot your server and then post diagnostics again.

Give it a file name.

If you removed the UD plugin, there is no way you'll get these errors on lib.php because it's removed. The UD webpage is active on the "Main" tab, even though the UD page is not displayed. UD refreshes every three seconds. I'll have a look, but please post diagnostics so I can see better what is going on.

See if this script won't work for you.

No those are varables passed to the device script by UD to work with inside the script. Load the default script (click 'Default' button) and then add your script operations in the approprate sections of the script.

Click on the device settings icon (three gears) and enter your script there.

Are you connecting to a remote server through Wireguard?

You are auto mounting a remote share and when UD tries to mount it, it is not available: Feb 3 15:45:03 PoppelSRV unassigned.devices: Mounting Remote Share '//ZINKID/HDTV'... Feb 3 15:45:03 PoppelSRV unassigned.devices: Remote Server 'ZINKID' is offline and share '//ZINKID/HDTV' cannot be mounted. Feb 3 15:45:33 PoppelSRV kernel: wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information. Feb 3 15:45:33 PoppelSRV kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <[email protected]>. All Rights Reserved. It looks like you are using Wireguard to access the remote share and it is not ready. I don't have an answer for this right now. Auto Mount USB devices does not apply to remote shares. You should also turn off UD debug logging. It's not necessary and can add too much logging to the syslog.

Post diagnostics.

No. Those log entries are from CIFS. Unraid has no control over those. Unmount the remote shares before turning off the remote server.

No. You can always enter your passphrase when the array starts if you don't want it saved on the flash drive.

That's what I was talking about. You need to unmount the device, then set a different volume, then remount. I don't see anywhere in the logs where you attempted to mount an apfs drive. I'm having trouble understanding what is going on from your logs. Do this: Set all devices to not auto mount. Reboot the server leaving everything connected. It looks like some of the devices are USB devices. After the server has rebooted, click on the mount button on one of the drives that didn't mount and post diagnostics.

Post diagnostics. On the apfs that won’t mount, click the drive settings (three gears) and set a different partition to mount. The bottom hpfs disk I don’t understand. The diagnostics will help me see what is going on.

UD waits for the network to start for two minutes as indicated by the time stamps on the log messages: Feb 1 12:02:42 towerpve unassigned.devices: Mounting 'Auto Mount' Remote Shares... Feb 1 12:03:54 towerpve webGUI: Successful login user root from 10.34.51.69 Feb 1 12:04:01 towerpve kernel: mdcmd (38): nocheck pause Feb 1 12:04:02 towerpve kernel: md: recovery thread: exit status: -4 Feb 1 12:04:13 towerpve kernel: br0: port 2(vnet0) entered blocking state Feb 1 12:04:13 towerpve kernel: br0: port 2(vnet0) entered disabled state Feb 1 12:04:13 towerpve kernel: device vnet0 entered promiscuous mode Feb 1 12:04:13 towerpve kernel: br0: port 2(vnet0) entered blocking state Feb 1 12:04:13 towerpve kernel: br0: port 2(vnet0) entered forwarding state Feb 1 12:04:14 towerpve avahi-daemon[5414]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:feaf:b722. Feb 1 12:04:14 towerpve avahi-daemon[5414]: New relevant interface vnet0.IPv6 for mDNS. Feb 1 12:04:14 towerpve avahi-daemon[5414]: Registering new address record for fe80::fc54:ff:feaf:b722 on vnet0.*. Feb 1 12:04:44 towerpve unassigned.devices: Cannot 'Auto Mount' Remote Shares. Network not available! Check your network Gateway setting.