skunk Posted April 15, 2023 Share Posted April 15, 2023 Hi there, hoping someone might be able to help. More recently my unRAID server has been locking me out/freezing/becoming inaccessible almost immediately after doing a parity check. The pattern has repeated itself over and over again over the last 2 weeks. Basically I try to access the GUI and I can't and the server isn't responding to ICMPs. I do a hard reset on it, it starts back up, spends the next 24-28 hours doing a parity check- everything working fine during this time. Sometime after the parity check (not exactly sure how long after) it becomes inaccessible again. attached is syslog I pulled after I did a hard reset this morning. I am not sure if I am even providing the correct information here. Any help is greatly appreciated. Thank you! syslog Quote Link to comment
Squid Posted April 15, 2023 Share Posted April 15, 2023 You'll need to post your diagnostics and also enable the syslog server (mirror to flash) and then post the resulting syslog (logs folder on the flash) after a crash Quote Link to comment
skunk Posted April 15, 2023 Author Share Posted April 15, 2023 thank you! Apologies for being such a noob. Attached are the Diagnostics and I have enabled logging to the flash drive. Parity check just started so I expect a crash in 24-30 hours from now and will post the syslog file. Thanks again! tower-diagnostics-20230415-0906.zip Quote Link to comment
skunk Posted April 20, 2023 Author Share Posted April 20, 2023 ok the server crashed again today and this time I had logging turned on. Find the syslog file attached. Any help is greatly appreciated! thank you! syslog (3) Quote Link to comment
Solution JorgeB Posted April 20, 2023 Solution Share Posted April 20, 2023 Apr 16 08:28:43 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Apr 16 08:28:43 Tower 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)). Quote Link to comment
skunk Posted April 20, 2023 Author Share Posted April 20, 2023 Thank you! I have changed this to ipvlan. Will wait to see if I get another crash now. Hope this works out! 1 Quote Link to comment
skunk Posted April 29, 2023 Author Share Posted April 29, 2023 Servers been up for 10 days without a crash. I think that was the issue. Thank you again!! I’ve marked it as the solution. 1 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.