Hello all,

 

Running into kernel panics after doing an OS update. 

Also recently replaced the flash drive in case that was a possible point of failure.

 

Attached are my logs. 

 

My monitor states:

Kernel panic - not syncing: Fatal Exception in interrupt

Kernel Offset: disabled

 

Cache drive shows as passed but has 466 errors. Should I pull that and swap it? is it as simple as swapping it and restoring from the back up plugin on the new drive?

 

 

blackpearl-diagnostics-20230906-1451.zip

There are macvlan call traces, switch to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

5 hours ago, JorgeB said:

There are macvlan call traces, switch to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

 

So the networking settings are enough to cause Kernel Panics and frequent reboots?

 

I canceled parity checks upon boot and the server is being reported as stable by my end users. Seems to only/mostly occur when performing a parity check. 

5 minutes ago, Discordant said:

So the networking settings are enough to cause Kernel Panics

This and can crash the server yes, if the server reboots on its own that's usually a hardware issue.

Well, I'm not sure I understand how it can trigger a kernel panic but I went into the settings nad toggled it to ipvlan and it seems to be solid now. Up to 18 hours uptime w/ parity check running and is rock solid for my end users. 

 

Will check back in but hoping it really was that simple. Thanks! Is there anything to change on a per container basis now that this setting has been toggled?

29 minutes ago, Discordant said:

Is there anything to change on a per container basis now that this setting has been toggled?

Should not be needed for most cases.