enmesh-parisian-latest Posted June 29, 2023 Share Posted June 29, 2023 My unraid box has been stable for years, however with the latest 6.12.x updates something is causing random crashes. The whole system becomes unresponsive, no output to the monitor or terminal access. It's occurred 4 times now on both 6.12.0 and 6.12.1. Attached is my most recent diagnostics generated after my last crash (sometime in the last hour or two. Any advice would be fantastic, thanks tobor-server-diagnostics-20230629-1742.zip Quote Link to comment
JorgeB Posted June 29, 2023 Share Posted June 29, 2023 Enable the syslog server and post that after a crash. 1 Quote Link to comment
enmesh-parisian-latest Posted June 29, 2023 Author Share Posted June 29, 2023 Thanks, I'll report back on the next crash Quote Link to comment
TheRadRomulan Posted July 2, 2023 Share Posted July 2, 2023 (edited) +1, this just happened to me for the 3rd or 4th time since upgrading to the 6.12.1; I'm reverting to an older version until this gets resolved. Edited July 2, 2023 by TheRadRomulan Quote Link to comment
enmesh-parisian-latest Posted July 7, 2023 Author Share Posted July 7, 2023 Fyi Quote Link to comment
enmesh-parisian-latest Posted July 15, 2023 Author Share Posted July 15, 2023 Hey, so I had a crash yesterday, and one just before these logs were generated. Is there anything here which could identify the problem? syslog-10.0.0.200.log Quote Link to comment
JorgeB Posted July 15, 2023 Share Posted July 15, 2023 Jul 14 06:51:44 tobor-server kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 14 06:51:44 tobor-server kernel: ? _raw_spin_unlock+0x14/0x29 Jul 14 06:51:44 tobor-server kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will 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)). 1 Quote Link to comment
enmesh-parisian-latest Posted July 15, 2023 Author Share Posted July 15, 2023 (edited) 59 minutes ago, JorgeB said: Jul 14 06:51:44 tobor-server kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 14 06:51:44 tobor-server kernel: ? _raw_spin_unlock+0x14/0x29 Jul 14 06:51:44 tobor-server kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will 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)). Interesting, I've never considered that. I have plenty of containers with custom IPs. I'll switch it now and report back. Thanks Edited July 15, 2023 by enmesh-parisian-latest Quote Link to comment
19dubgs3109 Posted September 4, 2023 Share Posted September 4, 2023 Any updates on this? I think I got a very similar issue. I am currently not at home and my unraid machine crashed. I will have someone reboot it and try to change the settings remotely. But any uodate if this worked for you would be much appreciated 👍 Quote Link to comment
enmesh-parisian-latest Posted September 5, 2023 Author Share Posted September 5, 2023 5 hours ago, 19dubgs3109 said: Any updates on this? I think I got a very similar issue. I am currently not at home and my unraid machine crashed. I will have someone reboot it and try to change the settings remotely. But any uodate if this worked for you would be much appreciated 👍 Hey, the ipvlan switch fixed the main crashes (i was getting 1 every 1-2 days). There's still some nagging problem which is causing a random crash every month or so, but I think that's related somehow to my cpu. Quote Link to comment
Recommended Posts
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.