October 30, 20232 yr For the last few weeks I have been dealing with an unRAID machine that keeps freezing up. I have been running this machine for over 4 years, but for some reason it has been freezing occasionally. I connected a monitor to it so I could try to figure something out. The only thing that I can tell is what time it stops responding. My only recourse is to hard boot it and kick off another parity check. I am not sure where to start looking in the diagnostics file. I am assuming this is hardware related because I was running 6.12.4 just fine for a few months, any my 4 year old hardware might be starting to fail. gurley-diagnostics-20231030-1738.zip
November 2, 20232 yr Author On 10/31/2023 at 4:02 AM, JorgeB said: Enable the syslog server and post that after a crash. Server crahed yesterday at 10:05 pm. Here is the syslog. syslog-172.25.106.62.log
November 2, 20232 yr Community Expert Nov 2 03:43:31 Gurley kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Nov 2 03:43:31 Gurley kernel: ? _raw_spin_unlock+0x14/0x29 Nov 2 03:43:31 Gurley 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)).
November 2, 20232 yr Author I appreciate the help. I haven't touched that setting ever, how would macvlan get enabled suddenly? Or, what else would change that would make it make a difference? The only physical change I made was adding a 2.5Gbps NIC because the onboard NIC stopped responding.
November 2, 20232 yr Community Expert 1 hour ago, rtgurley said: I haven't touched that setting ever, how would macvlan get enabled suddenly? It's quite common that users that didn't have issues start having after upgrading Unraid, and it's not only this latest release.
November 2, 20232 yr Author Server crashed again at about 14:45 today. Is it possible that the mother board is flaking out on me. Should I try to get log files from there? syslog-172.25.106.62.log
November 3, 20232 yr Community Expert Switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
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.