[solved] System completely locks up in hours.

[Dipskcit]

About a week ago something unknown happened and corrupted my docker image requiring me to load a backup of my appdata. Since then my server becomes completely unresponsive after less than a day of uptime. I've not been able to notice any pattern in when and why it happens, there was a point it was uncharacteristically up for about 36 hours, don't know what caused that either.

 

From trying to leave the log open to scanning with Fix Common Problems I've only come across 2 hints that anything is wrong, first is that for a time Fix Common Problems had an error about detecting a hardware issue and telling me to install mcelog. I did that and at some point that error stopped appearing. The other I've only seen once despite trying to replicate the scenario exactly was a bunch of nginx errors in the log that the system was out of memory. (uploaded as nginx errors.txt)

 

Since this issue make the system unresponsive I can't get a diagnostics file from before a reboot, but I've uploaded one downloaded shortly after rebooting from one of the crashes. Happy to upload any additional info that could help.

 

Unraid Version 6.9.2 2021-04-07

 

Plugins and versions
Dynamix System Temperature - 2020.06.20
Tips and Tweaks - 2021.03.09
CA Auto Update Applications - 2021.03.10
CA Backup / Restore Appdata - 2021.03.13 
Community Applications - 2021.05.16c 
Dynamix Auto Fan Control - 2020.06.21 
Dynamix SSD TRIM - 2020.06.21 
Fix Common Problems - 2021.05.03 
Nerd Tools - 2021.01.08 
User Scripts - 2021.03.10 

 

Hardware
AMD Ryzen 5 1600X - not overclocked
ASRock A320M-ITX
Corsair Vengeance LPX 32 GB (2 x 16 GB) DDR4-2133 - not overclocked
Corsair TXM Gold 550 W 80+ Gold
Samsung 970 Evo Plus 250 GB M.2-2280
6x 4TB HDD

450percent-diagnostics-20210521-1302.zip nginx errors.txt

Edited May 24, 2021 by Dipskcit

[John_M]

In the BIOS, have you set the "Power Supply Idle Control" option to "Typical Current Idle" instead of the default "Low Current Idle"? It can be difficult to find. One route is via the extensive AMD CBS menu. This will prevent the CPU from entering the very lowest power level when idle, a state from which some 1000-series Ryzens are unable to return.

[Dipskcit]

I did consider that but honestly couldn't remember if I had already done so, and being that the system has been just fine for over a year I assumed the issue was something else. I did however do what I should have done and double checked. The setting was on auto, I changed it to the value mentioned and will update with either good news in a few days or bad news in less. 

[John_M]

I don't see anything out of the ordinary in your diagnostics, but they only cover a short period.