jtilles

@Danuel, not really. I'll see the cores spiking when they first start a container, but nothing out of the ordinary.

I have not, do you recommend it? My hardware configuration hasn't been touched in over 3 years, do you think the memory could have gone bad? How long do you suggest to run the test for?

Added to the original post, thanks for the assistance @trurl

My Unraid server crashed yesterday where I had to give it a hard restart. Upon restarting my array couldn't be brought up because it couldn't find my third disk. I initially thought it was a bad hard drive as these things happen, but since it was my newest hard drive and the only one on the LSI expansion card, I plugged the hard drive directly into a sata port on the motherboard. When powering on, Unraid saw it right away and started the array. I thought problem solved, hardware issue, not so fast. When starting my docker containers back up, I would loose network connectivity to the server after a couple of minutes. I couldn't ping the server, I couldn't access the web ui (what I consider a 'crash'), so I was forced to manually cycle power on the server to re-enable connectivity. I tried following this thread as it seemed to be a similar issue but changing my custom docker network from macvlan to ipvlan did not solve the issue. Debugging I have Tried Start Unraid without docker started - does not crash after 30 minutes Start Unraid with docker and no containers - does not crash after 30 minutes Start Unraid with docker and only one container running (NGINXProxyManager) - does not crash after 30 minutes Start Unraid with docker and only one container running (NGINXProxyManager) and update other non-running containers - crashes Start Unraid with docker and only one container running (NGINXProxyManager) and start up secondary container - crashes Delete and reinstall docker image and containers - crashes when reinstalling containers Enable Syslog to write to disk - nothing useful during crash (that I can see) I am going crazy trying to figure this out, please let me know if there is anything further I can provide to have someone help assist me. illesserver-diagnostics-20231230-1636.zip syslog-192.168.0.180.log