Irithor
Members
-
Joined
-
Last visited
Solutions
-
Irithor's post in Server Experiencing Frequent Intermittent Crashing, Requires Hard Reboot was marked as the answerThanks JorgeB,
I have taken the following steps:
1. Upgraded Motherboard bios to latest version.
2. Reseated RAM and changed from slots A1/B1 to A2/B2 as per manufacturer recommendations.
3. Ran memtest, passed with zero errors.
4. Reseated CPU.
5. Re-adjusted cooler mount pressure.
6. Adjusted the following bios settings (as per recommended elsewhere on the Unraid forums):
- All settings as per Intel recommended defaults.
- Set ASPM from hardware-controlled to software-controlled.
- Disabled power saving.
- Disabled Fast Boot.
- Disabled C-States.
The server has now been running no issues for almost a week which looks promising.
The motherboard in this server has been replaced 3 times, CPU twice and RAM twice, with similar outcomes. So it seems the culprit is likely some funny business with power-saving states, likely software-side, as this was a similar erratic behavior that was caused by installing powertop, ultimately leading to me uninstalling it.
Unfortunately, the downside is the server now has a substantially higher power-draw even at idle which is obviously suboptimal, and will be looking to tweak back in some power-saving settings slowly over the coming weeks. Will update with any major changes.
Thanks again for the help.
-
Irithor's post in High CPU Usage By Docker Service was marked as the answerA scrub won't return anything specifically in regards to Docker Image corruption. Just overall corruption I believe.
I just ended up re-creating the Docker Image and downloading all the images from scratch. I also believe the culprit may be that the Plex Meta Manager container was creating a memory leak due to trying to restart itself in extremely quick succession without just stopping because of a bad update that was pushed that needed to disable part of it's start up process but didn't account for this looping issue.
Between those two things the issue seems to have resolved itself for now.