November 24, 20232 yr Hello, I seek you help because my UnRaid did 2 Kernel panics this night and I cant figure out from where they come from. First was in the start of the night, second was at 3h33 in the morning. unraid-diagnostics-20231124-0932.zip
November 24, 20232 yr Solution Forget that for now, the issue is already visible in the after boot log: Nov 24 09:25:26 UnRaid kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Nov 24 09:25:26 UnRaid kernel: ? _raw_spin_unlock+0x14/0x29 Nov 24 09:25:26 UnRaid kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.
November 24, 20232 yr Author 2 minutes ago, JorgeB said: Enable the syslog server and post that after a crash. Ok, thx, I just enabled it
November 24, 20232 yr Author 1 minute ago, JorgeB said: Forget that for now, the issue is already visible in the after boot log: Nov 24 09:25:26 UnRaid kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Nov 24 09:25:26 UnRaid kernel: ? _raw_spin_unlock+0x14/0x29 Nov 24 09:25:26 UnRaid kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot. Yes I saw that someone else had this problem and that you pointed at the same problem, I switched ipvlan this morning while troubleshooting. I'll keep you updated if this was the problem.
November 24, 20232 yr 5 minutes ago, Padi said: I switched ipvlan this morning Don't forget to reboot after the switch.
December 7, 20232 yr Author On 11/24/2023 at 11:47 AM, JorgeB said: Forget that for now, the issue is already visible in the after boot log: Nov 24 09:25:26 UnRaid kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Nov 24 09:25:26 UnRaid kernel: ? _raw_spin_unlock+0x14/0x29 Nov 24 09:25:26 UnRaid kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot. This was the problem. Had no crash since I changed it. Thx
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.