JorgeB

Difficult to follow, at leas for me, what you have done, please post a screenshot of the current array and the diagnostics.

It's not, but it is with the UD preclear disk plugin.

Mover logging is disabled.

Depends on what's on cache, enable the mover logging, run the mover and then post the diagnostics.

Log if filled with call traces, difficult to look for anything else.

You can install add-on NICs.

The problem appear to be the log tree, after it's the backup is complete you can try: btrfs rescue zero-log /dev/nvme0n1p1 And if that doesn't work format. Btrfs is currently the only option for pools.

NICs might be going bad, if one goes it's expected that the other goes at the same time, but it won't hurt to upgrade to see if there's any difference, you should upgrade anyway since v6.9.32 is quite old now. That's because of the earlier crash.

Difficult to say, you can first try a different Unraid version, like v6.10.3, if you see the same issues with the very different kernel it's likely hardware. Oct 2 17:51:37 ShadowRaid kernel: FAT-fs (sda1): FAT read failed (blocknr 32) Oct 2 17:51:37 ShadowRaid kernel: device offline error, dev sda, sector 2080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Oct 2 17:51:37 ShadowRaid kernel: FAT-fs (sda1): FAT read failed (blocknr 32) Oct 2 17:51:37 ShadowRaid kernel: device offline error, dev sda, sector 2080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Oct 2 17:51:37 ShadowRaid kernel: FAT-fs (sda1): FAT read failed (blocknr 32)

File system is damaged, see here for some recovery options: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

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

When nothing is logged it points to a hardware problem, and hence very difficult to diagnose remotely, one thing you can try is to boot the server in safe mode with all docker/VMs disable, 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.

It crashed again: Oct 1 13:44:26 fs kernel: DMAR: DRHD: handling fault status reg 2 Try updating to v6.10.3 or v6.11.0 since from v6.10.3 DMA remapping is no longer used, and that appears to be what's causing the problem.

Without nothing logged it's difficult to say, maybe it was a one time thing, if it wasn't I would downgrade to v6.10.3 first to see if it's update related, since that's the biggest change.

Syslog from the diags starts over after every boot, that's why I asked for the log from the syslog server, it might catch something. Most likely unrelated to the problem but after boot disk4 is already showing what look like connection issues, replace the SATA cable.

If you are not sure I'd wait for the next parity check, last one was definitely correct, so if the next one finds errors there's still a problem, if it doesn't you are likely fine and in that case the 1st one was likely noncorrect.

Install the tips and tweaks plugin and lower vm.dirty_background_ratio to 1 and vm.dirty_ratio to 2, this sometimes helps servers with a lot of RAM, not that 64GB is a lot, but it won't hurt to try.

I find that hard to believe, but it's not impossible I guess, tried to search for the error you are getting flashing but didn't find anything relevant, might be because the current firmware is not from LSI, though SAS2FLASH it's not detecting any issues before beginning.

Use the server normally and monitor the pool for errors. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582

Next suspect would be a disk, are you sure the previous check was correct?

It's not logged as a disk problem and SMAR looks OK, still a good idea to run an extended test to confirm.

Best bet for now is to use this driver:

Just create a new flash drove, restore the backup and replace the key, more info below: https://wiki.unraid.net/Manual/Changing_The_Flash_Device

Sorry, I didn't read the complete post, no idea about why it's crashing, I've never used NFS, someone else might be able to help.

If you have a backup you just need to restore it, are all the array/pool devices the same since the backup or were there any changes?