JorgeB

Run a read check.

Nothing relevant logged before the crash, see this if you haven't yet:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 

btrfs, the only option for now for multiple device pools, can change raid levels online.

See here:
https://wiki.unraid.net/Manual/Changing_The_Flash_Device#What_to_do_if_you_have_no_backup_and_do_not_know_your_disk_assignments:

Stop array, click on disk1 and change the filesystem from "Auto" to "XFS", repeat for disk2, start array and post new diags.

Start here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 

This.

Check the dat one Tools -> Registration -> Replaceable

Both pools show mounted:
 
/dev/nvme0n1p1 954G 22G 931G 3% /mnt/cache /dev/sdb1 112G 40G 71G 37% /mnt/vm  
But the syslog also shows a double mount attempt, which is weird, please reboot and post new diags after array start.

Problem is right after spin up, could be related to that, for now suggest disabling spin down for that drive only to confirm.

You can do a new config, but the best way would be to use a non RAID controller

If the kernel boot options didn't help suggest using different NVMe devices.

If they are all assigned to the array run a parity check, for drive testing purposes it's basically the same as running an extend SMART test.

Yes, previous one failed but last one passed, these errors can be intermittent, you can try adding parity2 again but any more errors from that disk and I would replace it.

/mnt/user must not be used for any extra mounts, correct that and reboot.

According to the diags there's something else writing to disk11, stop that and speed should increase by a lot.

SSD drive is filliping up the log with ATA errors, replace cables to see if they go away and post new diags after array start.

Looks like a clear bitflip:

 
3034 = 1011 1101 1010 265178 = 0100 0000 1011 1101 1010  
Run memtest, if you need to try and recover some data see here.

Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

Possibly this:
 

See if this helps:
https://unraid.net/blog/ssl-certificate-update-2

Or some issue with your config, you could recreate the flash drive and restore only the minimum from the backup, like the key, disk and pool assignments and docker templates.

That confirms the partition is not getting created.
 
Change the SATA controller from IDE to AHCI/SATA, it's a know problem with those chipsets in IDE mode.

Based on the trasnid the docker image you are using is new, if the appdata is correct you can just recreate a new image.

Looks like a SATA controller problem, it's dropping out together with all connected disks, try using an add-on controller if available, or a different board.