JorgeB

As of now keys are lifetime.

Basically yes, for the backup you can also only backup the config folder, unless you've created some custom script or other files elsewhere the config is all you need.

Crossflash the controller with LSI IT mode.

Possibly a controller issue, though problem appeared to start with a disk first, in any case recommend updating LSI firmware to latest since it's on a very old one, and check all connections.
 
May 11 00:48:19 Tower kernel: mpt2sas_cm0: fault_state(0x4101)! May 11 00:48:19 Tower kernel: mpt2sas_cm0: sending diag reset !! May 11 00:48:20 Tower kernel: mpt2sas_cm0: diag reset: SUCCESS  

One of the SATA controllers is being passed-through to VFIO-PCI
 
0a:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci  
That's why Unraid loses contact with all those disks.

Suggest leaving them all as default, since the changes those settings should not make much difference, unless you go to extreme values but likely in that case it would degrade performance, Unraid basically auto tunes those, except for the scheduler, for for general storage I didn't find much difference changing that, but you can try for yourself if you want.

https://forums.unraid.net/topic/86337-are-my-smart-reports-bad/?do=findComment&comment=800888
 

Macvlan call traces are usually the result of having dockers with a custom IP address and can end up crashing the server, upgrading to v6.10 or later and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

If it's a default raid1 pool you can just unassign the bad SSD and start the array, when you have a new one just add it to the pool.

Please post the diagnostics during a copy attempt.

Try adding them as devices, in the VM config add a new vdisk, set to manual and them specificy the device, /dev/sdX

Try rebooting and if it still doesn't start after that post new diags.

This will happen if for example that share exists (partially or fully) in a single device pool.

Click on the pool, scroll down to the "balance status" section, choose "convert to raid1 mode" and click balance.

Should work, the controller is just an Asmedia 1164, and those are known to work with Unraid.

In that case it might have died, it would still be a good idea to test it with a different board to confirm if you have one available.

No valid filesystem is being detected on disks 1 and 2, assuming they were also xfs you can force to see if it makes a difference, click on both disks and change the fs from auto to xfs and try again.

Dec 21 17:50:05 Godaam root: Warning: The kernel is still using the old partition table. Dec 21 17:50:05 Godaam root: The new table will be used at the next reboot or after you Dec 21 17:50:05 Godaam root: run partprobe(8) or kpartx(8) Just reboot and re-format and it should be good.

Yes, but you mentioned:
so easy to test.
 
That's about right with default writing mode, see turbo write.

Use
rsync -av /mnt/disk4/ /mnt/disk1/  

Suggest staying with that release for now, then try v6.12 when available, it will use a different kernel.
 
 

Nope, but the disk is cleared on the background, array is still available. 

Run the first part of this:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
 

Delete/rename /boot/config/network.cfg and network-rules.cfg and reboot, settings will go back to default, which is a bond with all NICs and DHCP.