JorgeB

You can have two data disks with dual parity, though IMHO it's kind of overkill for just to disks, and it still doesn't replace backups.

I've seen those before after waking up, probably normal.

Not that I'm aware of, and I'm using them without issues, but it does appear network related, try simplifying you network config as much as possible.

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

Sometimes this helps with NVMe devices dropping, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append" and before "initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference.

There's no shutdown logged on those, they appear to be the same ones you posted earlier.

Keys are saved on the disks, new config won't reset that since it doesn't touch the disks, they need to be re-formatted.

When Unraid forces a shutdown it saves the diags in the logs folder of your flash drive, attach latest ones of those here.

I would try that, but there are a number of Ryzen users having call traces with v6.9.x, possibly a kernel thing.

The UD device is very likely only mounting because the other device is also available, try this: Stop the array, if Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array. It after doing this it doesn't mount post new diags after array start.

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

Very strange, that NIC should use the e1000e driver, and Unraid includes it, but don't see any attempt to load it.

Not really, but board/CPU combo would be the first things I would try changing, there have been other Ryzen users with similar issues.

Yes, looks like an issue with the HBA: Apr 20 18:34:05 NAS-NG kernel: mpt2sas_cm0: fault_state(0x2622)! Apr 20 18:34:05 NAS-NG kernel: mpt2sas_cm0: sending diag reset !! Apr 20 18:34:06 NAS-NG kernel: mpt2sas_cm0: diag reset: SUCCESS Have you tried not sleeping the server? Not every hardware supports sleep/wake up correctly.

If there's no data there you can just format, it there is run a filesystem check.

Yep. It's possible.

it's

I just check the total TBW once a month or so to see if it's increasing normally.

This is part of the board, it's the IPMI function, it allows accessing the server over LAN without a keyboard/monitor, and not the reason the board is not posting, try clearing CMOS, reinserting the CPU/RAM, etc, if it still doesn't post you need to do an RMA.

Diags are after rebooting so we can't see what happened, disk looks mostly OK, but there are already some ATA errors on multiple devices: Apr 21 17:09:52 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Apr 21 17:09:52 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Apr 21 17:09:55 Tower kernel: ata3: link is slow to respond, please be patient (ready=0) Apr 21 17:09:56 Tower kernel: ata1: COMRESET failed (errno=-16) Apr 21 17:09:56 Tower kernel: ata4: COMRESET failed (errno=-16) Apr 21 17:09:59 Tower kernel: ata3: COMRESET failed (errno=-16) This is the Intel SCU controller, which is not as rock solid as the normal one, the other 6 ports, could also be a power/connection problem.

There would have been a "all data on this device will be delete at array start" waring after the device, you just needed to stop/start array, or worst case reboot to be able to change the cache slots again.

The number of writes in the GUI is basically meaningless, it varies with the devices, what matters are the TBW, and that is fine, only a few GB were written.

Thanks, happy to report it is fixed.

Yes.

New config will never reset encryption key, that is stored on the devices, you need to re-format them.