pula Posted July 23, 2019 Share Posted July 23, 2019 (edited) Hello! I'm having a bit of difficulty with a fresh install of Unraid. I have only enabled a Time Machine backup share, the Fix Common Issues plugin and installed docker. No containers running, no additional plugins installed. After about 22 hours my webconsole hangs and I am unable to SSH or ping the device. Here are the steps I've taken so far: Memory Test (no errors) New memory (and tested, see screenshot) Different USB drive Putting USB into different slots (USB2 & USB3 slots) --- currently in 2.0 slot Disconnecting all my drives and running on just the USB Check that all cables are secure and snug Check that ram is secure Running Troubleshoot Mode (that is how I captured the logs) Pulling my hair out Here is a complete list of the parts used for my device: https://pcpartpicker.com/list/Rqwm4q What's strange is that it is consistently 22 hours. I'm not sure if that means anything. Sorry if I missed any other details, this is my first time using Unraid or posting help on this forum. If there is anything else I can include or try, please let me know and I'll get on it ASAP. Thanks tower-diagnostics-20190721-2211.zip FCPsyslog_tail.txt tower-diagnostics-20190721-2311.zip tower-diagnostics-20190721-2241.zip Edited July 24, 2019 by pula solved Quote Link to comment
Vr2Io Posted July 23, 2019 Share Posted July 23, 2019 (edited) 1 hour ago, pula said: Running Troubleshoot Mode Still hang after 22hrs ? Jul 21 21:07:36 Tower kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) ### [PREVIOUS LINE REPEATED 11 TIMES] ### Tune C-State in BIOS from auto/enable/disable. Edited July 23, 2019 by Benson Quote Link to comment
JorgeB Posted July 23, 2019 Share Posted July 23, 2019 There are known issues with Linux and Ryzen, most workarounds are discussed here: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/ Quote Link to comment
pula Posted July 23, 2019 Author Share Posted July 23, 2019 Thank you both for the quick responses. I disabled the auto-overclocking options and disabled global C-state. Will let it run overnight and see if my issue persists. Quote Link to comment
pula Posted July 24, 2019 Author Share Posted July 24, 2019 Looks like I've passed the 22 hour mark with no issues. I'm going to mark this solved. Thanks again @Benson& @johnnie.black 1 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.