dlandon

Doing three preclears at once could be a bit much for a less powerful processor.

I think the GUI timed out because the processor was so busy.

Sweetalert2 is used for the dialogs used in UD and UD Preclear.

That's a good solution.

The server may be running, but it is not responding to a ping. After the server is booted can you eventually mount the remote share? If you can, the network and/or server needs more time. You can set a delay before mounting remote shares in UD settings. If the 'Mount' button stays grayed out and you can't mount the remote share, the remote server is not responding to a ping.

Post diagnostics.

There have been several reports of post read issues on larger disks. I haven't been able to get enough information to figure out what this might be. That's why I suggested using the docker for your preclear. The disk should be good to go.

I'll have a fix in the next release.

I have finally been able to reproduce this warning. It will be fixed in the next release.

Unzip and copy the attached file: cp lib.php /usr/local/emhttp/plugins/unassigned.devices/include/lib.php Let me know if the php warning goes away. Keep any eye out for array disks or pool devices showing up in the UD page.lib.ziplib.zip

I'm trying to track down the error and I am unable to reproduce it.

The .Recycle.Bin is the one this plugin uses for deleted files. I'll take a look and see if I can reproduce the error. So far I've not been abe to reproduce the error.

When you go to 'Main', UD is also running because it is a tab on main. I took your disks.ini and processed it with the same ode and couldn't get the error.

Unfortunately, that's probably the case.

Linux doesn't see a file system on the partition. You said it was a nvme disk in an external enclosure. You might want to try reseating the nvme drive. If that doesn't help, try the nvme drive in another enclosure.

Post a UD screen shot of the disk having the issue.

I'm also seeing this: May 28 21:16:48 Tardis kernel: pci 0000:0d:00.0: 63.012 Gb/s available PCIe bandwidth, limited by 16.0 GT/s PCIe x4 link at 0000:00:01.2 (capable of 252.048 Gb/s with 16.0 GT/s PCIe x16 link) I think that may be this device: 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] Subsystem: ASUSTeK Computer Inc. Starship/Matisse GPP Bridge [1043:87c0] Kernel driver in use: pcieport

I'm seeing realtek NICs in your server. They are not recommended for Unraid. The Realtek drivers are not reliable in Linux because they are not well maintained. Intel NICs would be a better choice. This might be the cause of your GPFs.

Updates are held back until someone is having a problem. If you were to suddenly have an issue with mounting a disk or a remote share, would you rather have an update or be told to wait until the next planned release? You aren't the only person using UD. UD has to deal with all manner of USB disks, and CIFS and NFS connections to remote servers. Some servers are old and don't deal nicely with newer technologies. For example the many versions of CIFS. This presents challenges in dealing with all the varied issues from the many combinations of hardware and software. While I can appreciate your thinking that the updates are annoying, just click the update banner and update, or cancel it until later. It's really not that hard. If it's that much of an inconvenience, uninstall UD and don't use it.

Ok. So those aren't ZFS disks you're mounting. Those are Unraid pools and they are fine. For some reason I thought you were mounting ZFS disks.

Post the disks.ini file here or PM it to me. There is something in that file that UD is having trouble with. Use /mnt/addons/ as the mount point instead of /mnt/.

That error is because UD cannot read the disks.ini file that defines the array disks so UD will know what disks are in the array. Show the output of this command: cat /usr/local/emhttp/state/disks.ini You are also ounting thinks at /mnt/: /dev/sdg1 1.9T 3.8M 1.9T 1% /mnt/cctv_pool /dev/sdh1 1.9T 111G 1.8T 6% /mnt/download_drive /dev/sdn1 11T 9.3T 1.7T 85% /mnt/games_drive /dev/sdf1 7.3T 600G 6.7T 9% /mnt/lan_cache_pool /dev/nvme1n1p1 932G 144G 782G 16% /mnt/unraid_files /dev/nvme0n1p1 1.9T 1.1T 825G 57% /mnt/vms_pool Don't mount things there. Use /mnt/addons/ for mounting your custom stuff.

Click on the double arrows icon on the UD page to see if the ram config files were not updated.

Unraid can serve NFSv4. I'm not sure what you need to do on the Ubuntu server to make it happen other than specify NFSv4 in the mount. As I said, NFSv4 is more robust and doesn't have stale file handles issues.

UD Settings.