JorgeB

Parity can't usually help with filesystem corruption issues.

No, you can use a share or mirror to the flash drive.

Unfortunately there's nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Enable the syslog server and post that after a crash. P.S. I see you have a 13900K, it may be the Intel stability issues with those CPUs.

xfs_repair is failing, you can try 7.0.0-beta, since it includes a newer version, if the same, the best bet will be using a file recovery app, like UFS explorer.

UDMA CRC error are usually from the SATA connection, but power related issues, be it the PSU or cables/connector, may also possibly cause them.

If it's a docker fork bomb issue, it usually crashes before there are OOM issues.

Thanks for the beer money!

Diags after array start please.

You can delete the new one from cache, as for the old one, you can leave on disk1 or move it cache, important thing is to always have a current backup of that file.

Since disk1 was unmountable a new image would be created on cache, and now that ones takes priority, stop the VM manager, change the path for libvirt from /mnt/user/system/libvirt/libvirt.img to /mnt/disk1/system/libvirt/libvirt.img, then restart the service and see if the VMs are back

Enable the syslog server and post that after you lose access again.

The service now is running, it wasn't in the previous diags, see if there is a duplicate libvirt.img, post the output of: find /mnt -name libvirt.img Wait until you get the cursor back to post the results

Update all plugins, especially Connect, then try again

Server is running OOM, it appears to be a container issue spawning endless processes, see if this helps with the Jellyfin container if you suspect that is the problem: https://forums.unraid.net/bug-reports/stable-releases/61210-cannot-fork-resource-temporarily-unavailable-r3020/?do=findComment&comment=28505 If not, recommend starting the containers one by one until you find the culprit.