April 14, 20179 yr Hello, I'm coming to you guys after about of week of troubleshooting and researching this, but I'm at wits and and I can't figure this out. I have my UnRAID running on the following machine: MB: AB350M Pro4 AM4 mATX AMD Motherboard CPU: Ryzen 7 1700 RAM: Crucial 16GB DDR4-2400 ECC (CT16G4WFD824A) GPU: PNY GTX 740 I have my unRAID installed on a SanDisk Cruzer Fit 8GB (connected via internal USB 2 4 pin header) & the machine connected via a TP Link TL-SG108 The issue: the system works, it boots, and when it's on, it works beautifully. However, after a few hours (sometimes days, sometimes 2 hours, sometimes 6) it goes down and totally unresponsive, both via GUI and on the machine itself. Sometimes the display connected to the box goes blank, other times it'll display the usual screen that appears when you first bootup (login) When this occurs, I can't use PuTTY to get into it, and the router ceases to detect the server. Initially I was using a different switch and different USB stick, I changed both to what I listed above and the issue still occurs. After making the hardware changes listed above, the screen no longer goes blank and the router still detects the server, but I still cannot login to the GUI. I attempted to run diagnostics, but it hangs afterwards. This morning, the box did display something, which I've attached. I've run memtest for an entire day with no errors. Currently the server is running absolutely no VM or dockers. Any help would be so welcome, please let me know if more info is needed.
April 14, 20179 yr Community Expert Did you check the Ryzen thread, try the suggestions on this post:
April 14, 20179 yr Author I did browse that thread but that solution seems like the one thing I somehow didn't find or try, I'm going to give it a go as soon as I can and I'll update. If that's what it is I owe you big time!
April 16, 20179 yr Author Just a bit of an update in case anybody has this issue and comes across this thread during troubleshooting, I made the change suggested in the link johnnie.black posted and so far we're looking at 1 day and 16 hours of uptime, a record for this box. I'd rather not cry wolf just yet, but it's looking good.\ EDIT: Final update, server is rock solid, with a couple minor hiccups here and there, but I no longer worry about whether or not my server is running. Edited May 6, 20179 yr by drd0ctor
Archived
This topic is now archived and is closed to further replies.