JorgeB

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.

Try uninstalling/reinstalling the My Servers plugin, rebooting the server should also help.

You are having issues with this cache disk:
 
Model Family: Western Digital Purple (Pro) Device Model: WDC WD30PURX-64P6ZY0  
Run an extended SMART test on it.

There was another user with the same device, a quirk has already been added, it should work for the next Unraid release.

There are errors identifying multiple disks, swap cables from a known good to a known bad and see if it follows cable or disk.

Check/replace cables but if disk1 is no longer detected you'll need to rebuild the array without it.

Mar 2 10:08:17 Oracle kernel: nvme0n1: I/O Cmd(0x2) @ LBA 2272992, 32 blocks, I/O Error (sct 0x2 / sc 0x81) MORE DNR Mar 2 10:08:17 Oracle kernel: critical medium error, dev nvme0n1, sector 2272992 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0  
Yep, looks like a failing device.

Start here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 
For the PCIe errors see if this helps:
https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009
 

This type of errors can be intermittent, if it happens again and it's logged as a disk problem as these were, consider replacing it.

Stop array, unassign all pool devices, start array, stop array, re-assign all pool devices, start array and you're done.