JorgeB

Mar 9 22:42:41 Tower12 kernel: md: sync done. time=36575sec Mar 9 22:42:41 Tower12 kernel: md: recovery thread: exit status: 0 Rebuild finished.
 
btrfs errors are about the docker image, delete and re-create, and try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), this might have been the source of the main issues.

I would recommend at least checking the cables, both power and SATA, or ideally replacing them to rule them out.

You are correct, behavior changed in the current release, going to find out when and report it since like you've experience this is a problem.
 
Not really my area but I'll also inquire about that, it would make things easier if that's possible to do.

See if this helps:
 
 

It's not logged as a disk problem and SMART looks OK, check/replace cables to rule that out and re-sync parity.

Controller problem:
 
Feb 22 18:52:07 Mordor kernel: megaraid_sas 0000:02:00.0: 236535 (730425127s/0x0020/DEAD) - Fatal firmware error: Line 255 in ../../hw/tempsensor.c Feb 22 18:52:07 Mordor kernel: Feb 22 18:52:07 Mordor kernel: megaraid_sas 0000:02:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009 Feb 22 18:52:07 Mordor kernel: megaraid_sas 0000:02:00.0: FW in FAULT state Fault code:0x10000 subcode:0x0 func:megasas_wait_for_outstanding_fusion Feb 22 18:52:07 Mordor kernel: megaraid_sas 0000:02:00.0: resetting fusion adapter scsi1. Feb 22 18:52:07 Mordor kernel: megaraid_sas 0000:02:00.0: Outstanding fastpath IOs: 160 Feb 22 18:52:07 Mordor kernel: megaraid_sas 0000:02:00.0: Reset not supported, killing adapter scsi1.  
Also note that RAID controllers are not recommended.

Unraid driver is crashing, reboot and post new diags after trying to format again.

Check filesystem on disk2.

Now it's showing a different issue:
 
Feb 28 18:56:07 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 30425088 wanted 58737 found 58225  
Docker image is corrupt, you need to re-create.

Yep, failed SMART test.

Array is started in maintenance mode, so the disks won't be mounted.

If it's just a log problem this should help:
btrfs rescue zero-log /dev/sdl1 If it mounts after that make sure backups are up to date because it can fail again in the near future, and if it does recommend re-formatting.

Symptoms look like when a SAS drive is formatted with type1/type2 protection, though nothing about that on SMART, but I've seen that before, so try low level formatting the drives without any protection, more info here:
 
https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078

https://forums.unraid.net/topic/110835-help-with-a-sas-drive/
 
 

Which disk has the filesystem problem? Log is showing issues with disk2, looks like a power/connection problem.

Not seeing anything else detected, so likely a hardware issue.

This SATA controller is being passed-through to the VM, so when it starts Unraid will lose all connected disks, just edit the VM and correct that.
 
08: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: ahci Kernel modules: ahc i

You can always update manually, download the zip, extract all the bz* files (plus changes.txt) overwriting the existing ones and reboot.

Please reboot, if it still doesn't start post new diags, note that you should always a have a backup of that file.

Based on the transid looks like the docker image is new, try restoring the containers by going to Apps -> Previous Apps

It's not logged as a disk problem and SMART looks fine, so most likely a power/connection problem, could also be spin down related.

Try this:
https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009
 

Run memtest

If you use the iGPU try blacklisting it to prevent the driver from loading.
 
https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0#Linux_Kernel

If you are using the default high-water allocation method only once all the drives above have less than 1TB free will anything be written to that disk.

Emulated disk is mounting, assuming contents look correct you can rebuild on top, possibly a good idea to first replace/swap cables to rule them out if it happens again.