dlandon

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.

I've run into the mounting problem with UD. I've passed this along to LT. I'm anxious to get UD working with NFSv4.

You shouldn't put Zoneminder files where the mover will move them. Stop Zoneminder, set the share to cache prefer, run the mover and the files will be moved from the array disks to the cache. Edit Zonemnder and confirm you have shared memory 'SHM' set to 50%, verify your 'data' path is set properly for a valid and not defaulting to memory. Restart Zoneminder.

Yes, take a look at the ownCloud documentation.

That is not currently possible. Not sure why you'd want to do that.

I've been making a few changes to the routine that pings remote servers to determine that they are online. The problem here is that the routine has not run before the automount of the remote shares. It will be fixed in the next release.

Please post your diagnostics.

Looks like it.

As soon as it is available I will test with UD.

It's a new idea I had that apparently needs some more work. I've just released an update that will stop the messages.

UD thinks the remote server is offline: Aug 26 22:45:56 Unraid unassigned.devices: Mounting 'Auto Mount' Remote Shares... Aug 26 22:45:56 Unraid unassigned.devices: Remote SMB/NFS server 'DISKSTATION' is offline and share '//DISKSTATION/Arbeit' cannot be mounted. Aug 26 22:45:56 Unraid unassigned.devices: Remote SMB/NFS server 'DISKSTATION' is offline and share '//DISKSTATION/Ronny' cannot be mounted. Aug 26 22:45:56 Unraid unassigned.devices: Remote SMB/NFS server 'DISKSTATION' is offline and share '//DISKSTATION/Nana' cannot be mounted. Aug 26 22:45:56 Unraid unassigned.devices: Remote SMB/NFS server 'DISKSTATION' is offline and share '//DISKSTATION/Restore' cannot be mounted. Aug 26 22:45:56 Unraid unassigned.devices: Remote SMB/NFS server 'DISKSTATION' is offline and share '//DISKSTATION/Pia' cannot be mounted. The remote server must respond to a ping or UD thinks it's offline.

Nach der Diagnose.

That's generally an issue with credentials. Try not to use special characters in the password. As soon as the mount is completed, that file is removed because the user and password are in plain text. After mounting the remote share, the credentials are no longer needed.

You don't have to, but it might help depending in what's going on in your system. Be sure to set it up for the specific directories to cache. Don't leave it at the default, it will cache too much.

Are you using the cache dirs plugin?

I don't see it on Brave browser.