dlandon

Post diagnostics.

You don't need it. Use the alias you assign and then the device for all commands is 'name=alias'. In the case of the detach command, 'name-alias' does work. I see in the UD page it is not documented in the help that the alias can be used. I'll correct that. Edit: In your case use: /usr/local/sbin/rc.unassigned detach name=Backup1

BIOS.

Remove the ipmi plugin and contact the plugin author about the php errors.

When you use the built in device script, the device is passed to the script as $DEVICE. If you have a stand alone or User Script, the alias 'name=' always works as the device for all the commands. The serial is long and very cumbersome. The alias name is a lot easier. The sdX and devX do change. That's why $DEVICE is passed in as an environment variable to the device script. You can use $DEVICE in the built in device script. UD handles the proper device assignment. The alias name works for the consistentcy you are looking for. There is no reason to implement the serial number for the commands.

Be sure to set up cache_dirs to only cache the shares that you want included. If you don't specify the included shares, it will cache anything it finds at /mnt/. Things like the system share don't need to be cached and will definitely put a load on cache_dirs.

You have disk errors: Feb 26 11:06:20 Tower kernel: scsi_io_completion_action: 812 callbacks suppressed Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2596 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2596 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2596 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2596 CDB: opcode=0x88 88 00 00 00 00 05 10 38 4a f0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: blk_print_req_error: 812 callbacks suppressed Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746961136 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2597 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2597 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2597 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2597 CDB: opcode=0x88 88 00 00 00 00 05 10 38 4a f0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746961136 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: buffer_io_error: 401 callbacks suppressed Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370142, async page read Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2598 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2598 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2598 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2598 CDB: opcode=0x88 88 00 00 00 00 05 10 38 50 e0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746962656 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2599 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2599 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2599 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2599 CDB: opcode=0x88 88 00 00 00 00 05 10 38 50 e0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746962656 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370332, async page read Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2602 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2602 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2602 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2602 CDB: opcode=0x88 88 00 00 00 00 05 10 38 56 d0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746964176 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2603 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2603 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2603 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2603 CDB: opcode=0x88 88 00 00 00 00 05 10 38 56 d0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746964176 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370522, async page read Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2604 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2604 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2604 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2604 CDB: opcode=0x88 88 00 00 00 00 05 10 38 5c c0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746965696 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2605 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2605 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2605 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2605 CDB: opcode=0x88 88 00 00 00 00 05 10 38 5c c0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746965696 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370712, async page read Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2606 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2606 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2606 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2606 CDB: opcode=0x88 88 00 00 00 00 05 10 38 62 b0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746967216 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2607 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2607 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2607 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2607 CDB: opcode=0x88 88 00 00 00 00 05 10 38 62 b0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746967216 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370902, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371092, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371282, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371472, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371662, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371852, async page read Feb 26 11:06:22 Tower kernel: sd 7:0:2:0: Power-on or device reset occurred ### [PREVIOUS LINE REPEATED 1 TIMES] ### Feb 26 11:06:24 Tower kernel: sd 7:0:15:0: Power-on or device reset occurred Things to look at: Power supply. Cabling - power and/or data. If you're running three drives at once, I'd suspect a power supply issue.

Please post your full server diagnostics.

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:

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.