JorgeB

Current set shutdown timeout is not long enough, stop the array manually and time how long it takes for the array to stop, add a few seconds and set that as your VM shutdown timeout, then add 30 seconds or so to that value and set that as the general Unraid timeout.

Enable this then post that syslog after a crash, also post the complete diagnostics.

Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/

There are still some issues, but it can be used, I have several btrfs RAID5 pools, but also have good backups.

No, and those errors after spin down are not that uncommon, and not a real problem, sometimes changing the disks APM level or disabling it helps.

Not the disk errors, looks like disks 9 and 10 dropped offline.

Disk looks OK, replace or swap cables/slot with another disk and try again.

That's normal, free space is always trimmed, you can check the log for the plugin output.

When this happens Unraid saves the diags in the flash drive, those could give a clue on what's causing it.

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

Unraid currently only supports one array, pools use btrfs, and can use any of the available btrfs profiles, including raid5/6, but note that those are still considered experimental.

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.