hmnd

Members
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

hmnd's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I did quite a bit of searching and, at the risk of jinxing myself again, I think I've finally found the solution to this. First thing I did was add the following kernel boot parameter: rcu_nocbs=0-11, thanks to the post below. That should be added by clicking flash in the Main section and adding it directly after append under all the Syslinux config boxes starting with Unraid OS. Next, I added /usr/local/sbin/zenstates --c6-disable to my /boot/config/go file, per the post below. That disables C6, and I had already disabled Global C-state Control in BIOS before. My server has now been running for 18 hours straight without issue, and hopefully it'll survive through the night. I figured I'd document what I did here, in case anyone encounters the same issue in the future.
  2. Yeah, and I'm unsure how to proceed at this point... So far I've replaced PSU, memtested RAM, disabled global c state and cool n quiet on CPU. Also installed latest mobo firmware that was released a couple weeks ago. Any other ideas?
  3. I mean that nothing was logged pertaining to the crash. Just stuff a few hours before and the boot up from after the crash.
  4. @Frank1940 @itimpi @bonienl Just crashed again. Syslog did save through the crash but there's nothing logged prior to it booting up again.
  5. I hadn't, but I've disabled global c-state (I think that's what it was called in bios) and I've got 3 hrs of uptime so far, so that may be it! Hopefully I haven't jinxed myself...
  6. @Frank1940 Got the new PSU in and still no dice. Any other ideas?
  7. Did a bunch of memtests a week ago and all passed. I think this is it. I checked and turns out the only component I neglected to replace in my rebuild last year was the PSU. Ordered a new one for tomorrow, so hopefully that'll fix it. I'll update here with what happens. Thanks!
  8. I actually have a bunch of UPS's I can try with and a second one I tried just now had the same issue. Lowered the sensitivity on the UPS, as it was on high. Hopefully that fixes it.
  9. Oh! You're right. I think I may need to replace my UPS. Can you tell what caused the shutdown or is it just up to speculation?
  10. I've scheduled parity checks to run monthly, but I keep getting a parity check started every few hours, which is causing all my docker containers to stop working. I've attached diagnostics if that helps (bigmac-diagnostics-20190518-0156.zip). Thanks in advance!