dlandon

Go ahead and update UD and give it a try.

No takers? I guess I'll wait a bit more and release what I have to fix the problem.

Unzip and copy the attached file: cp lib.php /usr/local/emhttp/plugins/unassigned.devices/include/lib.php Wait for about 5 seconds to be sure UD refreshes the GUI and see if you can then mount a drive. lib.zip

Correct, what is happening is UD detects the drive being tested for duplicates as a duplicate rather than ignoring it.

Someone please post the output of this command: cat /var/state/unassigned.devices/share_names.json

It only relates to looking up the duplicate names and prevents a mount because it detects a duplicate share name. It does not affect the drive at all.

Looks to be an issue with nvme drives and I'm pretty sure I know the problem. Give me a few hours to resolve and test and I'll release an update. Unfortunagtely my test server does not have an nvme drive, so it's a little harder for me to test.

You have a copy of CA, but it won't update on 6.9.2. That is a good plan.

CA is only compatible with 6.12 and later. It doesn't work on 6.9.X any longer. I don't know why it says an update is available.

Update to the latest UD Preclear and test. I can only do limited testing because I don't have a drive that gives a double quote in the family string.

You have several issues with this line: Don't use "'". Don't use ', '. Only commas to separate the excludes. No spaces. You can only specify one folder level. You cannot specify two folder levels deep. It is share/folder, not share/folder/folder.

Several suggestions: Remove the Dynamix System Stats. Install Tips and Tweaks plugin and make the recommended adjustments to the NIC and disk buffering settings. Upgrade to Unraid 6.12.6. You are currently on 6.9.2, Review your network settings. You have two NICs, but only appear to be using one (eth0). Set up a bond and bridge and use both NICs.

Can someone post diagnostics after a crash. There is not enough diagnostics here to do anything with,

UD does not mount zfs pools.

Yes, that's the issue. I've got a fix and it will be in the next release of UD preclear.

Post dioagnostics.

That code could not have been executed unless you had the zfs plugin installed. I did make a fix to prevent that php warning just in case someone else runs into it.

That works. There is an easier way though. Just unmount the root share and rename the mount point to 'user-pool.Endurance'. It would have immediately showed it as mounted.

There is a problem with your disk: Feb 3 12:10:11 dserver unassigned.devices: Mounting partition 'sdh1' at mountpoint '/mnt/disks/Backupdp'... Feb 3 12:10:11 dserver unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sdh1' '/mnt/disks/Backupdp' Feb 3 12:10:11 dserver kernel: XFS (sdh1): Mounting V5 Filesystem Feb 3 12:10:11 dserver kernel: XFS (sdh1): Starting recovery (logdev: internal) Feb 3 12:10:11 dserver kernel: XFS (sdh1): Ending recovery (logdev: internal) Feb 3 12:10:12 dserver unassigned.devices: Successfully mounted '/dev/sdh1' on '/mnt/disks/Backupdp'. Feb 3 12:10:12 dserver unassigned.devices: Warning: Unassigned Devices are not set to be shared with SMB. Feb 3 12:10:16 dserver kernel: usb 2-4: USB disconnect, device number 2 Feb 3 12:10:16 dserver kernel: device offline error, dev sdh, sector 10737746976 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2 Feb 3 12:10:16 dserver kernel: XFS (sdh1): log I/O error -19 Feb 3 12:10:16 dserver kernel: XFS (sdh1): Filesystem has been shut down due to log error (0x2). Feb 3 12:10:16 dserver kernel: XFS (sdh1): Please unmount the filesystem and rectify the problem(s). It mounts and then shuts itself off and UD does not know that. UD does detect that the device has an issue and marks it "Reboot" because it has detected that it dropped offline. Click on the check mark by the mount point when the disk is unmounted and see if the disk can be fixed. If not, then maybe one of the disk experts can help you with the problem.

Please post your complete diagnostics. It sounds like the disk is going offline and then back online. That's why it is showing 'Reboot' on the mount button. Is it USB?

What does the GUI show?

I encourage anyone holding back on updating UD to update to the latest version. Several things have changed that I believe are worth updating now: Cut down on the number of system command calls used to get mount status, read only status, and file system type of a disk device. Cut down on code that was redundant and being executed in the wrong places wasting time. Cached some information like mount status to make checking for mounted/unmounted status and read only a lot faster. Removed the nchan messaging to be sure UD does not interfere with core Unraid. Changed to a Java Script timer. Reworked the mount/unmount status on the 'Mount' button so it would better show mounting and unmounting status. Fixed a lot of issues with Device Settings that didn't work properly - like being able to choose a pre-existing device script and delete not deleting the proper script file. Reworked the remote share online check to verify that the SMB or NFS port is open to the server. Ping is no longer used to do this. Now you will see the online status not just on the server, but on shares. For example, a server is online and SMB is enabled but NFS is turned off, any SMB shares on that server will show online, but the NFS shares will show offline. Improved the server scan to be faster and better at finding servers on the LAN. Fixed a situation where the scan for servers would go out of control and peg CPUs in an endless scan. Added "vfs object = dirsort" to help with SMB listings in network listings. The bottom line is I believe you will find UD a lot more responsive and operation in general a lot cleaner. EDIT: Feedback encouraged as I don't hear much about things that aren't bugs.

Be sure to have the latest version 2024.02.02a and that file will no longer be created. It's harmless and will go away after a reboot, or if your OCD kicks in, just do a 'rm /mnt/mounts'.

I was able to reproduce the error and that's how I found it - from the log.

When Unraid updated to PHP 8.0, we had to track down all the warnings in php. Php 8.0 throws warnings about everything now that it used to ignore. It should be ready soon. I've been rewriting a lot of old code that is difficult to read and maintain, and finding a few code mistakes as I do that. I have to test it all.