jonathanm

Do you have any incoming ports open to the internet?

Power supply.

Do you have a folder named "cache" on any of your array disks?

No.

VNC doesn't support sound. https://en.wikipedia.org/wiki/Comparison_of_remote_desktop_software

As long as the power outage doesn't effect your internet connection to the server, then you can be notified.

Try removing both cache disks from the pool and starting the array, then stop the array and assign both disks at at the same time.

If something drastic was changed, it's easier to troubleshoot if you have to take affirmative action to update the script for the new executable than to have the script suddenly start failing because of a change in the file and you have no idea what happened. Imagine if for instance the behaviour of fusermount 3 required a new command line switch to make it work like fusermount 2 in certain circumstances. If your script didn't know it was working with the new fusermount, it wouldn't be able to detect the need for different parameters. I don't know if that's the case for this specific application, but in general it makes sense to have unique names for unique executables.

Before you get your containers all sorted, I'd recommend finishing the reiserfs to xfs migration that you seem to have started. You have plenty of free space, so now is the time to reorganize, before you start committing more data to the array.

Sounds like you taped pins 14 and 13, not 2 and 3. https://www.tomshardware.com/news/hdd-sata-power-disable-feature,36146.html

Hmm. Are you showing beta7?

References?

Licensing issues. https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/

If you use the rsync commands documented in the sticky reiserfs to xfs conversion thread it will copy the folders intact with all the contents. If you use midnight commander, it's up to you to make sure the source and destination are correct, i.e. /mnt/disk1 on the left pane and /mnt/disk2 on the right. For the purposes of this exercise, NEVER operate in the /mnt/user tree. All commands and paths must reference /mnt/diskX and /mnt/diskY for source and destination. I personally recommend rsync vs. mc, for the simple reason that verification of a complete copy is easier to manage with rsync.