JorgeB

Do they spin down in maintenance mode?

Enable the syslog server and post that if it crashes again.

Could be an issue with that specific container and the newer Docker engines, so it may be worth to retest after a downgrade.

Scrub the pool and if there aren't any uncorrectable errors, reset the stats and keep monitoring; if more errors show up, there's still a problem.

Nope, I also have some, look for a BIOS update.

Jun 5 16:16:22 Chimaera emhttpd: error: get_fs_sizes, 8551: Input/output error (5): statfs: /boot Jun 5 16:16:22 Chimaera kernel: sd 12:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jun 5 16:16:22 Chimaera kernel: sd 12:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Jun 5 16:16:22 Chimaera kernel: sd 12:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Jun 5 16:16:22 Chimaera kernel: sd 12:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 21 c0 00 00 01 00 Jun 5 16:16:22 Chimaera kernel: critical medium error, dev sda, sector 8640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jun 5 16:16:22 Chimaera kernel: FAT-fs (sda1): FAT read failed (blocknr 6592) Flash drive problem.

Look in the syslog for the list of correct file(s), delete/restore them from a backup, then run another scrub to confirm 0 errors and reset the stats, then keep monitoring the pool; if new errors show up, there's still a problem.

Nvidia is still using a driver; it could be just the order they are initiated with both kernels. Try binding the GPU to vfio-pci

If the GPU is still being passed there it would explain the issue, see if the hardware IDs didn't change; they can change with a kernel update.

Missing files and filesystem corruption is possible, but typically only after the filesystem is not mounting and you repair the filesystem; in this case, xfs_repair, if the corruption is bad enough, can move some lost files/folders to lost+found, never seen that happen without logged signs of corruption and the user then runing xfs_repair.

Both are set to array only, so the mover won't touch them. Also, note that you need to disable the Docker and VM services first.

You can try reseating them, or testing just two, then the other two.

Not in the diags posted: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3909] Kernel driver in use: nvidia Kernel modules: nouveau, nvidia_drm, nvidia Unraid is likely using the monitor output, hence the blinking cursor.

Unlikely that is a drive problem; once you believe the issue is resolved (note that it could also be an old issue, and the stats were never reset), scrub the pool, and post the results.

A pool pass minimum, more if possible.

Please post the diagnsotics.

Is the monitor connected to the Nvidia GPU?

That behavior seems strange to me, but it's such a large pool, so it may be different than I expect. I've also done some tests, and sometimes when resilvering multiple devices, it doesn't do any parallel resilver; other times, it does parallel for all; sometimes only a couple of the devices are resilvered in parallel, but not all, still I don't know why the difference; investigating. In any case, my recommendation for now would be to just let it finish.

If actual files are missing, something or someone must have deleted them.

First thing is to check filesystem on the emulated disk6, and make sure you don't rebuild it on top of the old disk for now

Best to disable mover logging, to avoid log spam, unless you are having some issues with the mover.

btrfs is detecting data corruption, start by runing memtest

Server rebooting by itself is almost always a hardware problem, or bad power.

May 20 04:49:23 Chimaera rc.nginx: Starting Nginx server daemon... May 20 04:49:30 Chimaera rc.nginx: Nginx server daemon... Failed. Nginx is failing to start, reboot in safe mode and post new diags.

Enable mover logging, run the mover and post the diagnostics.