dlandon

This is from UD: It should spin down unless there is activity on the disk. Since the disk is mounted, I suspect the issue is from disk activity.

Yes. Yes, with some exceptions. Some USB drives won't spin down. I believe that some disk controllers also can be a problem. Look in the log and confirm that you see the following: Aug 8 19:57:51 BackupServer unassigned.devices: Issue spin down timer for device '/dev/sdg'. for the drive(s) in question. The command issued is: /usr/sbin/hdparm -S180 /dev/sdg You will see this in the log for SSDs: Aug 30 07:56:34 BackupServer unassigned.devices: Don't spin down device '/dev/sdc'.

That's not an issue with UD. All I did was add the spindown timer command for a disk that was never mounted. Some disks, especially USB disks, don't respond the the shutdown timer command.

I see one situation where UD will not issue the spin down timer to a drive. That will occur when a drive is never mounted. I’ll issue an update to UD this weekend.

SSDs are never spun down. Spinning disks have a shutdown timer set on the disk to spin down after about 20 minutes of inactivity. You can control whether or not spinners are spun down by a setting in UD Settings.

Did you create a default script like it says?

Post diagnostics.

You can also have ownCloud scan for manually added files in the background by setting the following in the confg.php file: /** * Define how often filesystem changes are detected * Specifies how often the local filesystem (the ownCloud data/ directory, and * NFS mounts in data/) is checked for changes made outside ownCloud. This * does not apply to external storages. * * 0 -> Never check the filesystem for outside changes, provides a performance * increase when it's certain that no changes are made directly to the * filesystem * * 1 -> Check each file or folder at most once per request, recommended for * general use if outside changes might happen. */ 'filesystem_check_changes' => 0,

I don't see in the log where you mounted the SMB share. Click on the 'Mount' button to mount the share. I would also suggest changing the mount point name to something more meaningful. Click on the mount point name to change it.

Because of the changes in the Yolo model downloads and path renaming, the template has changed to modify the Yolo install environment variable and add Yolo V4 environment variables. You can specify the Yolo V3 or V4 models.

UD can only show what the Drobo reports. There is no way to override that.

Once you use the transfer to a new USB, the old one is blacklisted.

The fstrim command is 'fstrim -v -a' executed by the fstrim plugin. Go to a command line and try it. You'll see it will trim all SSDs.

The master repository is now updated to ZM 1.35 and ES 5.15.6.

I have been working to get the CIFS mounts working and have succeeded. I had to add a package to the Docker and finally figured out how to successfully set up a CIFS mount. Update the Docker and when setting up the CIFS mount, do the following: Select 'Username and password' for authentication. Use the server name or IP address of the server for the 'Host'. Enter the 'Share' name on the server. Use the server name as the 'Domain'. Enter credentials. This works for me:

Restart Zoneminder Docker and ES will update to 5.15.6.

You would be better serverd to ask for help on the Zoneminder forum.

Read the first post.

The destination is /mnt/disks/APPLE_HDD_HTS_541010A9E662_JD8002EZOXX3TD-part2. As I said earlier, change the mount point of the second partition to a meaningful name and use that as the destination.

The second partition has more than enough room. I would change the mount point of that partition to something easier to work with. That complex serial number is a bit difficult to work with in a script.

Which partition are you trying to copy files to? This is neither of those partitions. One is 'EFI' the other is a disk serial number.

Mount the disk and show a screen shot of the disk on the UD page. Edit: Click the '+' so all partitions show.

Post diagnostics.

As I get time.

I doubt it. Unraid encryption uses Linux Luks encryption. I doubt Mac OS will support that and vice versa.