Mizz141 Posted December 16, 2019 Share Posted December 16, 2019 So, I have my Unraid server set-up with Plex, Sonarr, Radarr, Jackett and qBittorrent. My Specs are: Ryzen 3 2400G, ASUS TUF-B450 Motherboard, 32GB Corsair Vengence Memory, 6*10TB Seagate Barracuda Pro's It usually works for a few hours before it outright crashes and wont do anything, cant connect via WebGUI, No Monitor Output, etc. Ive tried getting a different USB (32GB instead of 64GB), and Remounting RAM and CPU. So I cant optain a Log file via the usual means... The Way I """Fixed""" it before was by just reflashing the USB, Let the Parity Sync run, then Installing the Community Plugins-Plugin, and restarting everything... But this isnt a permanent solution in any way or form. Quote Link to comment
JorgeB Posted December 16, 2019 Share Posted December 16, 2019 Ryzen on Linux can lock up due to issues with c-states, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar), or completely disable C-sates. More info here: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/ 1 Quote Link to comment
Mizz141 Posted December 16, 2019 Author Share Posted December 16, 2019 Thanks for the Reply, ill update the Bios and look for the C-Stats settings, if that doesnt work ill reply again... Quote Link to comment
Mizz141 Posted December 16, 2019 Author Share Posted December 16, 2019 Ok, Im Back, And its behaving very very strange now, I only changed the Power Supply Idle Control, and when it boots, it turn on and off in 2 short bursts before giving me a post failed error... I might try unraid now, but I dont like this at all... 2 hours ago, johnnie.black said: Ryzen on Linux can lock up due to issues with c-states, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar), or completely disable C-sates. More info here: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/ Quote Link to comment
binhex Posted December 16, 2019 Share Posted December 16, 2019 Ok, Im Back, And its behaving very very strange now, I only changed the Power Supply Idle Control, and when it boots, it turn on and off in 2 short bursts before giving me a post failed error... I might try unraid now, but I dont like this at all... What memory profile are you using? Just try underclocking speed of the ram, I had stability issues with Corsair vengeance ram with a Ryzen 2700x.Sent from my CLT-L09 using Tapatalk Quote Link to comment
Mizz141 Posted December 17, 2019 Author Share Posted December 17, 2019 Ive underclocked the memory to 2133 and set it to typical current idle, it still crashed after a few hours, ill soon try disabling c-states alltogether and see if that helps... Quote Link to comment
binhex Posted December 17, 2019 Share Posted December 17, 2019 Ive underclocked the memory to 2133 and set it to typical current idle, it still crashed after a few hours, ill soon try disabling c-states alltogether and see if that helps...Have you run memtest to ensure it's not a bad memory module?Sent from my CLT-L09 using Tapatalk Quote Link to comment
Mizz141 Posted December 17, 2019 Author Share Posted December 17, 2019 The system ran around 9 hours before it crashed again, with typical current idle and 2133 memory. Now I cant boot at all, let alone get into BIOS... The screen is just black and nothing happens, the power button just immediately turns it off. I think I just wasted a lot of money... Quote Link to comment
JorgeB Posted December 17, 2019 Share Posted December 17, 2019 It should be withing the warranty period, or did you buy used? Quote Link to comment
Mizz141 Posted December 17, 2019 Author Share Posted December 17, 2019 Its within warranty, what could be wrong? the motherboard? Quote Link to comment
JorgeB Posted December 17, 2019 Share Posted December 17, 2019 If it doesn't even post it's possibly the board, but it can be other issues, like RAM, PSU, etc. Do a CMOS reset, remove all the DIMMs, make sure a speaker is connected and power up, you should hear some beeps, if yes try just one DIMM, if no beeps it's most likely the board. Quote Link to comment
Mizz141 Posted December 17, 2019 Author Share Posted December 17, 2019 I dont have a speaker on hand, Even without RAM, it remains unchanged... Ill remove everything now and prepare for RMA... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.