March 2, 20224 yr Hello Forum, my Unraid Server crashed now the third time after in a time window of est. three weeks. System was rock stable until the first Kernel Panic. I attached a picture of the error message as well some diagnostic data. I could use a hint here, where to look. Is it RAM, is it the USB Stick? Or even something else? Thank you for your help and support. nacrana-syslog-20220302-2139.zip nacrana-diagnostics-20220302-2239.zip
March 2, 20224 yr 1 hour ago, Nacrana said: Unraid Server crashed now the third time after in a time window of est. three weeks. Your syslog appears to be right after a reboot. Anything that might have been in the log related to the crashes is lost when you reboot since it is only in RAM. For this reason you should set up the syslog server and mirror to the flash or designate a share in which to save the syslog so the syslog persists even after reboots. Here is a good tutorial on setting up the syslog server.
March 3, 20224 yr Author 9 hours ago, Hoopster said: Your syslog appears to be right after a reboot. Anything that might have been in the log related to the crashes is lost when you reboot since it is only in RAM. For this reason you should set up the syslog server and mirror to the flash or designate a share in which to save the syslog so the syslog persists even after reboots. Here is a good tutorial on setting up the syslog server. Thank you, i will do that!
March 31, 20224 yr Author Alright, it crashed again. A few minutes ago. I attached the last thing i saw before i rebooted the machine. I pull the syslog from the stick in a few minutes and attach that too. E: syslog attached E2: Diagnostic zip attached syslog-47.13.37.222.log nacrana-diagnostics-20220331-1551.zip Edited March 31, 20224 yr by Nacrana
March 31, 20224 yr 6 hours ago, Nacrana said: Alright, it crashed again Your syslog shows several call traces. They do not all appear to be the same. I am no expert on call traces, but a few of these will eventually lock up your server. I am familiar with macvlan call traces as those used to lock up my system. These were caused by IP addresses assigned to docker containers on br0. Your call traces are not of this variety but they do indicate some other problem(s) related to CPU calls. Hopefully, someone who can interpret the cause of your call traces will chime in.
April 1, 20224 yr Solution I see MACVLAN in the log. If you are using docker containers with unique IPs, you should try 6.10RC4 and switch your Docker custom network type to IPVLAN that was introduced in 6.10 for that reason. The setting is in Settings / Docker Settings. You may have to switch to advanced view.
April 1, 20224 yr Author 5 hours ago, ChatNoir said: I see MACVLAN in the log. If you are using docker containers with unique IPs, you should try 6.10RC4 and switch your Docker custom network type to IPVLAN that was introduced in 6.10 for that reason. The setting is in Settings / Docker Settings. You may have to switch to advanced view. I will look into it. Thank you for your tip.
June 2, 20224 yr Author Just a update. The crashes never happened after switching to the RC Channel. The Issue seems completly gone with 6.10. Edited June 2, 20224 yr by Nacrana
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.