dlandon

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.

Yes, I made a change that broke the script execution. If you go to the Tools->PHP Settings, you will see a php error. It will be fixed in the next release.

After that hppens, go to the Tools->PHP Settings and see if there are any php errors.

I see several things, but cannot offer any explanaton. In the log: Jan 31 08:34:23 BASIC-CABLE shfs: error: strcpy_share_path, 455: No such file or directory (2): path too long: /CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES SIZE and the output of df shows: Filesystem Size Used Avail Use% Mounted on rootfs 16G 1.7G 15G 11% / tmpfs 32M 1.5M 31M 5% /run /dev/sda1 29G 981M 28G 4% /boot overlay 16G 1.7G 15G 11% /lib overlay 16G 1.7G 15G 11% /usr devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 16G 0 16G 0% /dev/shm tmpfs 128M 396K 128M 1% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/addons tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1p1 5.5T 5.3T 168G 98% /mnt/disk1 /dev/md2p1 5.5T 5.3T 175G 97% /mnt/disk2 /dev/md3p1 5.5T 5.3T 171G 97% /mnt/disk3 /dev/md4p1 5.5T 5.3T 177G 97% /mnt/disk4 /dev/md5p1 3.7T 3.4T 341G 91% /mnt/disk5 /dev/md6p1 3.7T 3.4T 322G 92% /mnt/disk6 /dev/md7p1 3.7T 3.4T 338G 91% /mnt/disk7 /dev/md8p1 3.7T 3.4T 325G 92% /mnt/disk8 cache 1.7T 256K 1.7T 1% /mnt/cache /dev/sdb1 257G 249G 7.6G 98% /mnt/docker-cache /dev/sdc1 489G 36G 454G 8% /mnt/plex-cache cache/data 1.7T 512K 1.7T 1% /mnt/cache/data cache/isos 1.7T 32G 1.7T 2% /mnt/cache/isos cache/unraid_scripts 1.7T 203M 1.7T 1% /mnt/cache/unraid_scripts cache/system 1.7T 30G 1.7T 2% /mnt/cache/system cache/domains 1.7T 128K 1.7T 1% /mnt/cache/domains cache/Music 1.7T 29G 1.7T 2% /mnt/cache/Music cache/Plex DVR 1.7T 1.8G 1.7T 1% /mnt/cache/Plex DVR cache/vm-disks 1.7T 16G 1.7T 1% /mnt/cache/vm-disks cache/temp 1.7T 128K 1.7T 1% /mnt/cache/temp cache/appdata 1.7T 5.1G 1.7T 1% /mnt/cache/appdata cache/iCloud-Photos 1.7T 7.7G 1.7T 1% /mnt/cache/iCloud-Photos cache/Pre-Rolls 1.7T 451M 1.7T 1% /mnt/cache/Pre-Rolls shfs 37T 35T 2.0T 95% /mnt/user0 /dev/loop2 270G 16G 255G 6% /var/lib/docker overlay 270G 16G 255G 6% /var/lib/docker/overlay2/ceaae5d21858eed21b3c02b988e671146808da6ac5659070f89479f8771981cf/merged /dev/loop3 10G 4.5M 9.5G 1% /etc/libvirt overlay 270G 16G 255G 6% /var/lib/docker/overlay2/1fe89828cb1992deac96043a165b0c2d257bee31fbdfba6cde3c12fa78108cbd/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/232e8202b591222a7e925454bd743b305391cf9b1ba5cf8e45f8776b0dd2d3c7/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/3f713ae84e4622598210b94b15793c3260aea4a692cc7d7226b55030c88d7a4f/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/7175475e611234ca5e3da0f392bc31f9db2ca0cddab1e36085a67b82094d12ee/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/39b7105f858ae7dfd92628e545a60bed09bf2fe79d22df47f2b715d566c0bbb1/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/9b4d538da85729710cdc271557e36a0118c0a00fa390174430df405af3f7c9e8/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/3bbc4e85d87c6c86fe05edc45febfd136d2e1cc08e61ea0e994b284db0fdc5c8/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/4ab32eea32431398b12171c4d5dc4b1f1e5284e29507fd487befacc6461e1750/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/71cbdeea3c3dd7e4ee0488597410796130d1a57a100cb50d67cf8365e89ba2a1/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/b9b2da94a87c92e6b24a4c5441d85b3b6b3a46a394f88a2fc7191ad27f1f875b/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/51e6dec694ebd54d74406ddfaecfb0e016166cc87f784b17f032982678de8700/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/b7bab57da934f09a97e8012dc9c48e9d2ac97a19edf5c6a22160b7c87b12eb00/merged overlay 270G 16G 255G 6% /var/lib/docker/overlay2/7ab691d92f572e5b56d725dad3662d095d7aaa71f9377b3eddd8a20f94d1e7f2/merged tmpfs 3.2G 0 3.2G 0% /run/user/0

This is the troublesome Chinese character '空' and it will be turned into an underline character '_' for the GUI. The new configuration would look like this: [//UGREEN-5E37/ldt0621_存储_间4] protocol = "SMB" ip = "UGREEN-5E37" path = "ldt0621_存储空间4" domain = "" share = "ldt0621_存储空间4" and the GUI will look like this: This will be fixed in the next release of UD. You will see an invalid configurtion message when UD is updated. Just remove and then add the remote share back and it will be fixed

There are no Chinese charcters in the config file. Please post the samba config file with chinese charcters as you show in an earlier post, or post the chinese name of the share so I can test.

Post the samba.cfg file.

No, I'm not.

It's an alphanumeric sort, not a numeric sort. The display would have to be all numeric to sort in true size. That would not be very human readable. Not much I can do unless I can find a work around.

When a disk is unassigned from the array and then used in UD, it can sometimes show a duplicate UUID and won't mount. The change UUID only shows disks that might need their UUID changed. UD is not saying it has to be changed.

If an ntfs disk is not shut down properly in windows, it will mount as read only when UD mounts it. Look in the syslog and you'll see why it was mounted read only.

Fixed, update to 2024.01.22b.

Sounds like a php error. Go to Tools->PHP Settings and see if a php error shows.