Hello,

 

a few weeks ago, my Unraid server started having the problem that after a while of operating normally it is no longer responsive. The Server ist still running but neither the WebGUI is loading or any of my Docker containers. The only way to regain access is by restarting the system physically. This is obviously not ideal. It happened roughly 4 times in the last 2-3 weeks.

 

There is a disk (Disk3) that has a UDMA CRC error count of 200. However, it does not seem to be increasing. I doubt that this is the main issue, but please correct me if I'm wrong.. I plan on replacing the disk anyway.

 

I will attach a system log that I created shortly after the reboot which was at: Dec  2 18:50:41.

I tried to make sense of the logs before that time but I'm not sure what to look for.

 

Any help would be appreciated.

 

Thank you.

server1-diagnostics-20231202-1859.zip

Enable the syslog server and post that after a crash.

 

Ok, I will. I just had the problem again, but I didn't set the syslog up properly. I will have to wait a couple of days for the crash to happen again.

 

Thanks.

Edited December 8, 20232 yr by Einzigstes

On 12/3/2023 at 12:09 PM, JorgeB said:

Enable the syslog server and post that after a crash.

 

 

It did happen again yesterday. I tried to access the GUI at 8:30pm, 25.12.2023 but no response.

I looked through the syslog file, but on that day at least, there aren't any Errors at all. Do I need to set up a remote syslog server?

 

In the logs there are a bunch of errors from the cache pool filling up. This is a seperate problem that should already be fixed.

syslog-10.10.10.2 - 25.12.2023.log server1-diagnostics-20231226-0916.zip

Dec 22 09:30:16 Server1 kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Dec 22 09:30:16 Server1 kernel: ? _raw_spin_unlock+0x14/0x29
Dec 22 09:30:16 Server1 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.

On 12/26/2023 at 12:07 PM, JorgeB said:

Dec 22 09:30:16 Server1 kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Dec 22 09:30:16 Server1 kernel: ? _raw_spin_unlock+0x14/0x29
Dec 22 09:30:16 Server1 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.

 

So far there haven't been any crashes. I'll see if this has solved the problem. Thank you!