dlandon

Update and you should be good to go.

I've found the problem and it will be fixed in the next release.

Please post your diagnostics.

I don't code for the Dashboard. You will have to ask Limetech for that enhancement.

Already There:

The folder won't be created until a file is deleted.

Is the recycle bin running? Look at the indicator in the upper right.

It should not affect at all what can be deleted. It only puts files in the recycle bin that have been deleted in a SMB share. The .Recycle.Bin folder is a hidden folder. You have to browse directly to the \\Tower\share\.Recycle.Bin folder, unless you have hidden folders enabled in Windows. You do not have to reboot the server to get the recycle bin to work.

New release of UD: The major change is support for NFSv4. You will need 6.10.rc2e or later for NFSv4 support. The default is to mount all remote NFS shares with NFSv3. If you want to enable NFSv4, go to the UD settings and select 'NFSv4' as the default version to mount.

That looks like a credentials issue. Be sure not to use special characters like '#', '?', '!', or quotes. You enter the IP address where you choose the server. Just type it in and don't click the search for servers button.

I've made a few security changes and the '#' character is a problem. When the '#' and '&' character along with a few others like single and double quotes are used in the mount point, they are converted to underscore. UD is written in php and there are some reserved and inappropriate characters that cannot be used in variables.

Working fine for me on plugin installation. The 'at' was used because if it is not the plugin install will not show the 'Done' button. Just a little fluke in the plugin install.

NFSv4 is now working in 6.10rc2e and UD is working with NFSv4. UD has a new setting to specify which version of NFS to use when mounting remote shares. It defaults to NFSv3 for backwards compatibility.

UD has to have a unique serial number for each device. Some external drive bays don't present the unique disk drive serial numbers that UD needs.

I'll have to take a look and see what changed.

Remove the '#' character from the mount points.

Are you out of memory? Post your diagnostics.

Upgrade to 6.10. The FTP server is disabled by default.

How do you have the disks connected?

I don't have access to my servers right now to get a screen shot. Click on the '+' under the drive and then click on the check mark.

Those were removed because they no longer apply.

The disk was not unmounted cleanly: Aug 26 18:03:03 Tower unassigned.devices: Adding disk '/dev/sdf1'... Aug 26 18:03:03 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'exfat' -o rw,auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdf1' '/mnt/disks/External_HD_Drive' Aug 26 18:03:04 Tower mount.exfat: volume was not unmounted cleanly Aug 26 18:03:04 Tower unassigned.devices: Mount of '/dev/sdf1' failed: 'FUSE exfat 1.3.0 WARN: volume was not unmounted cleanly. fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option ' Aug 26 18:03:04 Tower unassigned.devices: Partition 'WD Elements_25A3' cannot be mounted. Click on the check mark next to the mount point and see if it can be fixed. You also have a UPS communications issue: Aug 26 17:06:39 Tower apcupsd[5597]: Communications with UPS lost. Aug 26 17:15:51 Tower emhttpd: spinning down /dev/sda Aug 26 17:16:45 Tower apcupsd[5597]: Communications with UPS lost. Aug 26 17:16:56 Tower emhttpd: spinning down /dev/sde Aug 26 17:17:22 Tower emhttpd: spinning down /dev/sdd Aug 26 17:17:22 Tower emhttpd: spinning down /dev/sdc Aug 26 17:26:51 Tower apcupsd[5597]: Communications with UPS lost. Aug 26 17:30:52 Tower emhttpd: spinning down /dev/sda Aug 26 17:36:57 Tower apcupsd[5597]: Communications with UPS lost. Aug 26 17:45:53 Tower emhttpd: spinning down /dev/sda Aug 26 17:47:03 Tower apcupsd[5597]: Communications with UPS lost. Aug 26 17:51:07 Tower emhttpd: read SMART /dev/sde Aug 26 17:57:09 Tower apcupsd[5597]: Communications with UPS lost. You need to get that fixed.

You have the disk passed through: Sep 1 17:22:54 Galactica unassigned.devices: Disk with serial 'SSD_970_EVO_DD5641988390', mountpoint 'Samsung_SSD_970_EVO-part1' is set as passed through. Sep 1 17:22:54 Galactica unassigned.devices: Disk with serial 'SSD_970_EVO_DD5641988390', mountpoint 'Ny_volym' is set as passed through. UD does not spin down disks. Those messages come from Unraid spinning down the disk. Where is the disk passed through to? Check there.

You rebooted, so the log doesn't show the spin downs for /dev/sda like you posted. Looks like you have the spin down set for every 15 minutes. /dev/sda is a WD hard drive (WD60EFRX), so Unraid will spin it down. It doesn't appear to be a nvme SSD, but the sdX designation can change on reboot so that might not be right. This is not really a UD issue. You can filter the log messages by installing the Enhanced Log plugin and filtering these messages in the log 'Syslog Filter' tab of Enhanced Log.

That's not enough information. Please post the diagnostics.