February 1, 20197 yr I'm about 3 weeks into my unraid adventure and I have had 4 lock ups. Notice I'm unable to get the web gui, then try pinging the box (no response), and can't ssh into it either. Some changes I've made some my 3rd lock up are, direct fan on my SAS Controllers as they were really hot. I can keep my finger on them now. Plugged into a UPS and reseated the memory. This time I pulled the flash drive before rebooting and attached the logs. Anyone able to help me figure out whats going on. The reboots are completely random. Specs are in my signature. unraid-diagnostics-20190130-0709.zip
February 8, 20197 yr Author Just happened again. This time I had Fix Common Problems set to troubleshoot mode. New logs attached. Wife and I were watching a plex movie when it locked up. Note, we've watched tons of other things before this no issue. Just wanted to let you know what we were doing. unraid-diagnostics-20190207-2103.zip
February 8, 20197 yr Community Expert Did you try any of the Ryzen workarounds? Most are mentioned in this thread:
February 8, 20197 yr Hmmm, so pulling the USB out before rebooting keeps the logs? That will help - I've been having this issue too - Ryzen 1800x.
February 8, 20197 yr Community Expert 1 minute ago, Marshalleq said: Hmmm, so pulling the USB out before rebooting keeps the logs? That will help - I've been having this issue too - Ryzen 1800x. By default logs are only held in RAM. You have to take special action to get them stored elsewhere.
February 8, 20197 yr Seems like I need to take special action. Seems like a dumb feature too - it's not like logs take a lot of space these days.
February 8, 20197 yr 4 hours ago, Marshalleq said: Seems like I need to take special action. Seems like a dumb feature too - it's not like logs take a lot of space these days. By default writes to the USB are kept to an absolute minimum to extend its life. The "Fix common problems" plugin has a diagnostic mode which continually writes the log to the USB.
February 9, 20197 yr Author 16 hours ago, johnnie.black said: Did you try any of the Ryzen workarounds? Most are mentioned in this thread: Thanks, "Global C-state Control" was set to auto. Just changed it to Disabled. Will report back.
Archived
This topic is now archived and is closed to further replies.