ChloeMelody Posted February 3, 2019 Share Posted February 3, 2019 (edited) Hi. I have recently changed my motherboard (Asrock b450m pro4) and CPU (AMD Ryzen 2700X) and the web UI become inaccessible roughly every 1 to 2 hours and I then have to do a hard shutdown by pressing the case button. I have run Memtest for around 3 cycles and it gave me 0 errors. I already had the same problems with the same model of motherboard that I had sent back to buy a new one, but on the old one the same type of crash happened after roughly one day, two if lucky. Before starting unraid with the new hardware, I just reinstalled Unraid on another USB key and just transferred my shares and applications. In the meantime, I was using another motherboard running an Intel i7 and on Unraid 6.6.6. but the docker where frequently corrupted obligating me to soft restart the server but didn't happen with the Ryzen CPU. Here's the docker that are usually running with the Ryzen: Krusader, RDP-Calibre, Plex. I'm wondering if any of you could help me pinpoint the problems with my installation to hopefully be able to fix the problems. FCPsyslog_tail.txt tower-diagnostics-20190203-0254.zip Edited February 3, 2019 by ChloeMelody added diagnostics Quote Link to comment
trurl Posted February 3, 2019 Share Posted February 3, 2019 In addition to that log tail go ahead and give us the diagnostics Quote Link to comment
ChloeMelody Posted February 3, 2019 Author Share Posted February 3, 2019 3 minutes ago, trurl said: In addition to that log tail go ahead and give us the diagnostics tower-diagnostics-20190203-0254.zip Quote Link to comment
trurl Posted February 3, 2019 Share Posted February 3, 2019 Are you overclocking? Is your BIOS up-to-date? Quote Link to comment
ChloeMelody Posted February 3, 2019 Author Share Posted February 3, 2019 Just now, trurl said: Are you overclocking? Is your BIOS up-to-date? All of the overclocking settings in the bios are on default, and the bios is up to date too. Quote Link to comment
JorgeB Posted February 3, 2019 Share Posted February 3, 2019 There are known issues with Ryzen and Linux, this might help: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/?do=findComment&comment=2816 Quote Link to comment
ChloeMelody Posted February 10, 2019 Author Share Posted February 10, 2019 On 2/3/2019 at 1:59 PM, johnnie.black said: There are known issues with Ryzen and Linux, this might help: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/?do=findComment&comment=2816 Thanks for the link. I have disabled global c state and changed the "Power Supply Idle Control" to "typical current idle". I have also applied the 'fix' that Spaceinvaderone suggested in his video (rcu_nocbs=0-16). It now crashes 'only' after around 17 hours of uptime, and I then have to hold the power button to do an unclean shutdown. Recently I have noticed that the rcu_nocbs=0-16 was supposed to be rcu_nocbs=0-15 so I changed it and now I am waiting to see if it would crash again or not. 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.