JorgeB

See if this applies to you, if yes, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Doesn't look like a disk problem, suggest swapping cables(both power and SATA) or slot with a different disk and see if the issue follows the disk.

The Ryzen related info might also be applicable, if that doesn't help enable the syslog server and post that after a crash.

This suggests the controller uses one or more port multipliers, if yes bandwidth of any SATA port connected to one will be divide by all 5 ports, diags would confirm.

It will autostart the VMs at first array start if array autostart is enabled.

Unfortunately there's nothing relevant logged, does it only crash when running the VM? Also make sure you check this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Yes.

You cannot create new threads, you're supposed to use the existing docker support thread, in this case:

Issues with parity and disk7 also look power/connection related.

Looks like a flash drive issue, not necessarily a bad flash drive, try re-formatting again using diskpart or use a different one to test.

Next time get the diags before rebooting.

Server appears to have started based on that screenshot, errors are likely a corrupt docker image, see if you can get the diagnostics using the console.

Syslog starts over after every boot, enable the syslog server and post that after a crash.

It's anonymized so it's usually fine.

No.