JonathanM

Sure, as long as the surge protector with all the computers and stuff has continous power when you switch the UPS source power off. If you can cut the power to the UPS without unplugging it you don't need that surge protector in line with it. Most wall sockets in the US don't have switches so I specified a switchable surge protector to provide a way to turn off the power to the UPS without disturbing the earth connection. Not quite sure I understand this. Computers and stuff should have a constant source of power throughout the test, the only thing switched is the UPS input. The reason I specified a surge protector for the critical equipment is to have them all on the same circuit with some level of protection from power issues. Do you have a way to figure out the power draw of the servers and network equipment? The test accuracy depends on the dummy load being close to the actual load.

Unbalanced plugin, or Dynamix File Manager plugin

Temporarily obtain 2 surge protecter power strips with switches. We need to turn off the power without breaking the ground circuit, so no yanking plugs out of the socket. Obviously starting with both servers safely shut down, along with everything else you plan to plug into the UPS. Plug all the power cords that will go to the UPS into surge protector 1. Plug the UPS input into surge protector 2 Make a (hopefully measured) educated guess on max power draw of everything plugged into surge protector 1. Bonus points if you have an accurate wattmeter to feed surge protector 1. Leave the USB connection from the UPS going to Unraid 1. This is why you need surge protectors instead of yanking the plug. Very bad things can happen if the UPS ground isn't tied back to the PC when it loses power. Fire up the UPS with nothing but the USB lead and power input connected. Boot up all the equipment on surge protector 1. Start a non-correcting parity check on both Unraid servers, and have everything started and loaded like it would in a worst case unattended power outage. Read the power draw if you have meter of some sort. Connect a similar draw non critical load to the output of the UPS. Good candidates are halogen work lights, incandescent lights if you have any around any more, space heaters on low, use your imagination to find enough load. Now you are ready to start the actual testing portion. This should be done with observation only, resist the urge to manually intervene. You should have a way to watch the dashboard of both Unraids. Turn off the surge protector feeding the UPS to start the "power failure". Observe the loads connected to the UPS, look for flickering lights or fan speed variations on the heater, whatever you have connected. Remember to turn off any tech not connected to UPS, to accurately simulate a power outage. Optionally for a more thorough test disconnect your outbound internet if you can do so safely, unless you are using cellular WAN, as a real power outage may drop the WAN outside of your control. Watch to see if you get notifications on the Unraid dashboards of a power failure. If everything is working to plan, Unraid 2 should start the shutdown process cleanly after 5 minutes. When it shuts down, you can adjust the load on the UPS to match, maybe turn off one of the lights connected. After the 10 minutes has elapsed, hopefully Unraid 1 starts a clean shutdown. When it's done, you can adjust the load on the UPS if you want. At this point if the UPS is still running the dummy loads, you can call it a success, depending on what you observed. Other considerations. After draining the batteries on a UPS, make sure you account for recharge time before depending on it for more backup, since a typical recharge rate is 10 to 20 times slower. If the UPS was running on battery for 15 minutes, allow at least 3 hours recharge time. SLA UPS batteries, the most common type, get touchy about being drained more than 50%. Their capacity and lifetime is reduced the deeper the discharge, so try to stay in the top of the curve. If you are discharging too deeply, reduce the time on battery parameter. Personally my secondary loads like client pc's, VM's, etc are all set to shut down after a minute or two of power outage. Keep in mind you can install apcupsd clients on any VM's hosted on Unraid to get them cleanly shut down prior to the main timeouts and reduce the shutdown time. If during the test the batteries are drained before the timed shutdown is done, you need to upsize the UPS, or restructure to multiple UPS since you are aiming for less than 50% drain, and you can't shorten the delay meaningfully. If the communication path between devices is broken or interrupted, the shutdown signal will be lost. Make sure all network infrastructure can outlast the full shutdown period. I recommend NOT trying to have things automatically recover after a power loss event. Much better to manage the recovery hands on, watching and controlling, especially checking UPS battery condition to ensure enough capacity to handle another shutdown if power goes out again during the boot up process.

Possibly the emulated chipset is different, and / or the virtio or other drivers are different.

Only when they would want a data drive larger than 10TB. The parity drives in Unraid are totally independent, the only rule is that they must be equal or larger than any single data drive. How the OP explained the situation was Parity1 - 10TB Parity2 - 10TB Failed data - 8TB Replacing either P1 or P2 with the 14TB and using the 10TB as the replacement for the failed data drive is perfectly fine. P - 14TB P - 10TB D - 10TB

https://docs.unraid.net/unraid-os/manual/storage-management/#upgrading-parity-disks

Why? Is this not fully contained and self hosted?

binhexe's FAQ, specifically Q24, details what is needed. Since you posted your PIA credentials openly you need to change them ASAP. Further discussion on this topic should be continued in the support thread for the container,

If that enclosure does not have 1 SATA data cable per drive going to the motherboard or an SAS cable to a HBA, you are probably going to have continual problems using it. You didn't give us much to go on for troubleshooting, diagnostics would have been helpful, so these guesses are pretty much shots in the dark.

Yes and no. My theory didn't work, if it did, the disk slot being rebuilt would be mounted already. Let the rebuild complete, and wait for @JorgeB

Is there not a checkbox to allow you start? Post a full screenshot of the main page.

You would backup inside the VM, then restore to a bare metal disk. If you want to be safe, remove all the disks that are assigned to the array or pools plus the Unraid USB stick, and restore. Then if something goes wrong you can just plug everything back in.

Not that I'm aware of. My best idea would be to use backup software to make an image then restore it. Windows backup may work for you, acronis is another option.

Yep

Rename the EFI- folder to just EFI

Maybe the expander remapped the partitions? @JorgeBmay have a better option, but I seem to remember the solution was to unassign one drive at a time, start the array, stop the array, reassign the drive, let it rebuild. Several hours for each drive. Whatever you do, don't remove more than one drive at a time. To test my solution, unassign one drive, start the array, and see if the emulated drive mounts properly.

Dynamix File Manager plugin

When you enabled the docker service, an empty image was created to hold the container executables. Kind of a preallocation.

At this point you may as well format the drive and write your backup to it, run the make bootable, and see what happens. If it gives you errors while formatting or writing your backup to it, proceed with a new drive.

Drives in the classic Unraid array can't be trimmed, so SSD's may see performance loss over time. If you assign a parity drive, writes to the array are speed limited by the parity drive.

I'm unclear what you are asking. If a pool is a single disk it can be formatted XFS, multi drive pools can use either BTRFS or ZFS.

Currently the Unraid "array" is the classic individually formatted data drives with one or two parity drives. Files are not striped across drives, so each drive has its own free space. Pools are single or groups of disks that can utilize BTRFS or ZFS RAID levels. You can have multiple pools, but are required to have 1 and only 1 "array". In a future Unraid release the classic "array" will become just another pool type. Until then, you must have at least a single drive occupying disk1 in the classic array. Also, the built in mover currently only moves files between the array and a designated pool, no pool to pool moves with the built in mover. All root folders and their contents on the array and all pools are combined into the "user shares".

No, just disable the docker service and run the server normally to see if it still freezes. Does it freeze if that container is not running?