ZombieLord

I am also experience random crashes with an R730 over the last few months and see the same events in my IDRAC Lifecycle Logs: 2023-10-31T16:31:34-0500 SEL9901 OEM software event. 2023-10-31T16:31:31-0500 SEL9901 OEM software event. 2023-10-31T16:31:27-0500 SEL9901 OEM software event. 2023-10-31T16:31:24-0500 OSE0001 A runtime critical stop occurred. Will try switching my Docker custom network type over to Ipvlan and see if that resolves it. Update: Looks like its a known issue that should be resolved in 6.12.4: https://docs.unraid.net/unraid-os/release-notes/6.12.4/ Fix for macvlan call traces The big news in this release is that we have resolved issues related to macvlan call traces and crashes! The root of the problem is that macvlan used for custom Docker networks is unreliable when the parent interface is a bridge (like br0), it works best on a physical interface (like eth0) or a bond (like bond0). We believe this to be a longstanding kernel issue and have posted a bug report. If you are getting call traces related to macvlan, as a first step we recommend navigating to Settings > Docker, switch to advanced view, and change the "Docker custom network type" from macvlan to ipvlan. This is the default configuration that Unraid has shipped with since version 6.11.5 and should work for most systems. However, some users have reported issues with port forwarding from certain routers (Fritzbox) and reduced functionality with advanced network management tools (Ubiquity) when in ipvlan mode. For those users, we have a new method that reworks networking to avoid this. Tweak a few settings and your Docker containers, VMs, and WireGuard tunnels should automatically adjust to use them: Settings > Network Settings > eth0 > Enable Bonding = Yes or No, either work with this solution Settings > Network Settings > eth0 > Enable Bridging = No Settings > Docker > Host access to custom networks = Enabled Note: if you previously used the 2-nic docker segmentation method, you will also want to revert that: Settings > Docker > custom network on interface eth0 or bond0 (i.e. make sure eth0/bond0 is configured for the custom network, not eth1/bond1) When you Start the array, the host, VMs, and Docker containers will all be able to communicate, and there should be no more call traces!