JonathanM

What is the output of "mount" at the console?

post the current contents of the templates folder

As long as all the drives are still connected, parity or unraid doesn't care which physical bay / connector is used. It tracks the drives by serial number. The logical slots in the Unraid GUI won't be effected.

Have to set the new config before you change the assignments.

Probably easier to use

If you are using the 7 series beta, you simply define another pool with the 2 disks and select RAID1 either BTRFS or ZFS. If you are still on the 6.x release, the array is still necessary, but you can assign any old drive, even a USB, to disk1 and then define all the different pools with whatever RAID levels you want.

It's a little complicated. Parity1 doesn't care what order the disks are in, as long as they are all there. Parity2 uses disk slot number as well, so it's invalid when you move slots around. There is no easy way to tell unraid to only rebuild parity2, so you have to set a new config with all the drives where you want them, WITHOUT assigning parity2, and select that parity is already valid, start the array, cancel the automatic parity check, stop the array, add parity2 back, allow it to build. All this assumes the drive being removed is properly zeroed, that can take a very long time. Most people just take the risk of being unprotected while parity is being rebuilt when removing a drive slot. That assumes all your drives are healthy, but if you don't think all your drives are healthy that needs to be addressed BEFORE going through this drastic of a procedure.

Not without rebuilding the parity2 slot.

tools, new config, apply

If you click the "Add container" button on the docker page you should be able to select your user templates.

Do you have any way to check the temperature of the heatsink in the final configuration, i.e. case closed?

They are part of the Unassigned Devices plugin.

That means any data written is suspect, as it all flows through RAM. Likely all the recovery attempts while the bad RAM was installed caused more issues and corruption. When the machine can pass a long memtest, preferably more than 24 hours, then you can start recovery efforts.

That means the VPN isn't configured or connecting properly. Look through the supervisor.d log after a failed attempt for clues.

https://github.com/binhex/documentation/blob/master/docker/faq/help.md Have you gone through binhex's docs?

For a test, set the VPN to no, and see if the interface loads.

Have you run the diskspeed benchmarks?

Install this and run the benchmarks, both drive and controller.

ZFS drives in the parity array are single volume, and can't correct corruption. If you want ZFS to correct bit corruption you must use multi drive volumes with the appropriate RAID level in pools. Don't use ZFS in the parity array if you want bit correction.

Mover isn't the only thing that will write to drives, if an existing file is overwritten, the writes will happen on the disk where the file exists.

Go to the apps tab and search for factory reset.

I like nomachine.

You can customize your windows installation and optimize it for VM install. https://schneegans.de/windows/unattend-generator/

You can use any disks you want in pools, and select pretty much any RAID level. There is no requirement to use the Unraid array in version 7, you can set up whatever arrangement of pools you want. "Cache" in the Unraid context is an old term, pools now can be used as the main storage if you want.

Is the array stopped?