JorgeB

Couple of DIMMs are dual rank, so speed should be set @ 1866MT/s, also make sure power supply idle control is correctly set:
 
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 

Only eth0 should have a gateway assigned, remove it from the other interfaces.

OK, logs is clean now, first lets cancel the btrfs balance, to do that:

 
mkdir /temp mount -o skip_balance /dev/sdj1 /temp  
If mount is successful type:
btrfs balance cancel /temp  
then
umount /temp  
Now unassign cache1, start array, stop array, re-assign both cache devices, start array and post new diags.

Please don't create multiple threads about the same thing, see my reply in your other post.

Run a scrub, then check that in the output all errors were corrected.

Unassign all cache devices, start array, stop array, re-assign all cache devices, start array, that should do it.

Try adding 30 secs or so to the shutdown timeout.

This device is being pass-trough to the Windows VM:
 
<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source>  
And it is the NIC:
06:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I225-V [8086:15f3] (rev 03) Subsystem: Micro-Star International Co., Ltd. [MSI] Ethernet Controller I225-V [1462:7d32]  
When you change/add/remove hardware it's normal for some devices to change address, so you might need to adjust.

Docker image is corrupt, delete and recreate.

Looks more like a flash drive problem, also make sure it's using a USB 2.0 port.

I can't see unassinged devices number in the diags, but since there's only one unassigned disk I assume it's the 6TB Seagate, if yes the disk looks OK, so just mount it UD and if all looks good format disk 14 and copy the data over.

See if this applies to you, if yes, upgrading to v6.10 and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.:
 
https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
See also here:
https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

See if this applies to you, if yes, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.:
https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
See also here:
https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Looks like the typical Ryzen onboard controller issue, it's quite common with some Ryzen servers, usually mostly under load, look for a BIOS update but best option might be to use an add-on controller.

If the files copied to a share already exist Unraid will overwriting them on the same disk, so it was probably that.

Try booting in safe mode.

You can't delete all the config files, create a new Unraid install then copy only the key.

If you mean there are 12 drives using the same cable from the PSU it's likely a problem.

If you don't assign any data disks they won't be at risk.

Parity is invalid, autostart will start to work once it's synced.

For now I would replace the cables and try to sync the new parity again.
 
CRC errors are usually the SATA cable, for parity and like mentioned need to see the SMART report first, but for now looks like power/connection problem.

That works assuming current cache is btrfs, you'll know when the btrfs operations are done when the stop array button is available again.

Check filesystem on disk 12

Tools -> New config -> Keep all assignments -> Apply
 
Then start array.
 
 

https://wiki.unraid.net/Shrink_array