Unraid keeps randomly hanging around once a week and requires a hard reboot. I enabled mirroring syslog to flash but I don't seem to see anything in syslog-previous.txt from the last few days which is weird, unless I'm missing something. I also am tracking CPU, memory usage, etc. and it doesn't seem to have any spikes around that time, unless the spike is breaking my tracking as well.

tower-diagnostics-20250719-2000.zip

Edited July 20, 2025Jul 20 by grantland

There appears to be a container constantly restarting; see if you can find which one by looking at their uptimes.

Thanks for the tip, I found a container that was in a restart loop and resolved the issue that was causing it. Will see if that resolves the issue.

By the way, how did you see that a container was restarting?

Jul 19 20:00:51 Tower kernel: eth0: renamed from vetha9b8f2f

Jul 19 20:00:51 Tower kernel: br-ca0905249d55: port 4(vethb74d4c8) entered blocking state

Jul 19 20:00:51 Tower kernel: br-ca0905249d55: port 4(vethb74d4c8) entered forwarding state

Jul 19 20:00:51 Tower kernel: docker0: port 10(veth023db8b) entered blocking state

Jul 19 20:00:51 Tower kernel: docker0: port 10(veth023db8b) entered disabled state

Jul 19 20:00:51 Tower kernel: veth023db8b: entered allmulticast mode

Jul 19 20:00:51 Tower kernel: veth023db8b: entered promiscuous mode

Jul 19 20:00:52 Tower kernel: eth0: renamed from veth2c7c93a

Jul 19 20:00:52 Tower kernel: docker0: port 10(veth023db8b) entered blocking state

Jul 19 20:00:52 Tower kernel: docker0: port 10(veth023db8b) entered forwarding state

Jul 19 20:00:52 Tower rc.docker: overseerr: started successfully!

Lines like these on the syslog, these are normal when the containers start or get updated, not 24/7