(SOLVED) Server becomes unresponsive

[S0ulDrag0n]

When I first started my UNRAID server, I started on an old Intel machine with 8gb of memory. Enjoying my experience, I then decided to move my server into another server (AMD Threadripper 3960X) that was beefier and was not used as often as before.

 

Everything went well, and I decided to upgrade my memory as well in that new server from 32 gb to 128 gb.

 

However, ever since the move and the upgrade, the server occasionally becomes unresponsive (can't reach UNRAID web UI or docker containers) and I have to perform an unclean shutdown. I've run memtests and the memory seems to be fine, but I feel as if I can't completely rule it out.

 

I have attached my server diagnostics along with a recent syslog log. It recently occurred this morning around 9:30-10 AM, but the output doesn't seem to be logged.

 

I will try hooking up a monitor to consistently monitor the output for now. In the meantime, perhaps someone could take a look and see whether there is anything worth noting in the logs I've collected.

sarva-diagnostics-20220914-1920.zip

syslog.txt

Edited September 23, 2022 by S0ulDrag0n
Forgot to attach syslog

[JorgeB]

Start here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

[S0ulDrag0n]

Thanks Jorge!

 

I have read that post before and I believe c-states should be disabled. I did realize my memory configuration is off from the recommended settings, so I will try disabling the XMP profile and monitoring it for a few days.

[S0ulDrag0n]

Issue is resolved as my server has been running smooth for the last week. C-states were disabled, but I didn't match the memory speed to the number of sticks I had. I kind of got greedy trying to have the max speed from the DIMMs over the stability of the server.

 

Thanks!

Edit: This also addressed the execution errors with Docker

Edited September 23, 2022 by S0ulDrag0n
Forgot to mention additional info that may help others