dlandon

I've made a fix for this. It will be in the next release. The GUI is limited in space and a longer alias would take up too much space. When the device is detached, it is a very low power mode. What makes you think it is spinning? Can you spin down the disk using the GUI? There was a change made to allow a USB disk to act more like a SATA device and possibly fix this kind of thing, but the disk still has to handle spinning down. If you are not using 6.12.8, try upgrading and see if it helps.

This is a user script I use to perform a backup to that disk. It can be done on a schedule with User Scripts. #!/bin/bash #description=Backup Music Folder. #backgroundOnly=true #arrayStarted=true #clearLog=true # LOGFILE="/tmp/unassigned.devices/logs/Music_Backup.log" # Mount the backup disk /usr/local/sbin/rc.unassigned mount name=MusicBk # Backup the Music folder to the backup disk rsync -av --delete --exclude .Recycle.Bin '/mnt/user/Music' '/mnt/disks/Music Backup/' 2>&1 >> $LOGFILE # Unmount the disk /usr/local/sbin/rc.unassigned umount name=MusicBk # Spin down the disk /usr/local/sbin/rc.unassigned spindown name=MusicBk

The 'diskname' is the alias you assign to the disk:

I'm looking into this.

Be sure the keyfile does not have a new line at the end. The keyfile is one line of text with nothing else like a new line or carriage return.

Click on the 'Help' icon in the upper right side of the UD UI and read down the page. You'll see the script commands to manage a UD disk - mounting, unmounting, spinning down, and putting the disk in standby.

You've already posted this on the UD forum and answers have been posted there. Don't double post. It's confusing and makes it hard to help you.

Don't run a VM from a flash drive. Performance will be awful and you'l wear out the flash drive in short order.

That's too many drops and overruns on eth0. Is your motherboard fairly new? I would suggest some more things to try: Unplug your eth0 cable so only eth1 works. You have the bond set up as backup, so if eth0 disappears, eth1 will take over. See if your motherboard has a firmware update. In all cases monitor your NIC errors and see what change affects it.

There is no way to roll back because the Zoneminder Docker Container always installs the latest version of Zoneminder. Try getting support for your issue at Zoneminder support.

Does the right side of Tips and Tweaks show the proper status of the turbo mode when you turn it back on?

Turn off turbo boost and then go to a command line and run this command: /usr/bin/flock -x -w 1 /sys/devices/system/cpu/intel_pstate/no_turbo -c 'echo "0" > /sys/devices/system/cpu/intel_pstate/no_turbo' Let me know if this command generates any errors. If there are no errors, does the turbo boost turn back on?

What driver shows on the UI?

You need either NetBIOS or WSD enabled to be able to see your server on the network. I'd recommend turning on WSD.

Enable bridging also.

Go to the Dashboard and look at the network area. Select errors info and see if there are any network errors. Also see if your switch shows any network errors.

What CPU Governor shows in the Tips and Tweaks UI page?

If you are talking about /mnt/remotes, /mnt/rootshare, and /mnt/addons, those cannot be changed or hidden.

Don't mount them and you'll not see them in /mnt/. If they are mounted, the have to show in /mnt/.

You can disable the "Mount" button in the device settings.

Network equipment. Cables, router, network switch, etc.

Run a parity check when you are finished.

Click on the "Array Operation" tab and you'll see a check box to format the disks. Preclear does not format disks with a file system.

What happened was you started a preclear, then paused it either manually or by stopping the array. When the array started again, the preclear operation was resumed incorrectly even though the disk was moved to the array. I've reworked the logic for pausing and resuming preclears so a preclear won't resume on a disk that is not a unassigned - i.e not in the array or a pool, and the pause status more accurately reflects the actual paused status of the disk. As for the Historical devices, wait until the remove 'X' turns red so it can be removed. That may not happen until the next reboot. It's harmless as it only indicates that the disk was at some point seen by UD. I will be updating UD preclear and you'll want to upgrade so a preclear cannot resume again.

There's an issue with the preclear clearing operations. For the moment just click the double arrows on the preclear page to be sure any preclears are stopped. I'll follow up with what to do next.