VoNpo Posted August 24, 2017 Share Posted August 24, 2017 (edited) Hi, I have problem that my unraid system totally freezes randomly. (max 1-2 times in month.) Whole system freezes and it won't even response to keyboard which is connected to unraid box. Not even _ letter blinking in command line, so only way to fix is do unclean reboot. Any ideas which could cause this? Parts: Motherboard: Supermicro X11SSM-F Ram: 8GB Samsung M391A1G43DB0-CPB x 2 (16GB total) CPU: Intel Xeon E3-1240v6 PSU: EVGA SuperNOVA P2 850w Edited August 29, 2017 by VoNpo Quote Link to comment
JorgeB Posted August 24, 2017 Share Posted August 24, 2017 Did you already update your bios to fix the Skylake HT bug? Quote Link to comment
VoNpo Posted August 24, 2017 Author Share Posted August 24, 2017 (edited) 1 hour ago, johnnie.black said: Did you already update your bios to fix the Skylake HT bug? Haven't heard of that bug before, will try update bios. EDIT: Just updated bios and firmware, let's see if this solve my problem! Edited August 24, 2017 by VoNpo Quote Link to comment
VoNpo Posted August 29, 2017 Author Share Posted August 29, 2017 (edited) I updated BIOS and IPMI firmware and server has worked without any problems until now. Now it freezed in different way. Connected monitor shows repeately these two lines, never seen these before crond[1785]: exit status 137 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null crond[1785]: exit status 137 from user root /etc/rc.d//rc.diskinfo --daemon &> /dev/null Edit: I just run few passes of memtest86 without any errors Edited August 29, 2017 by VoNpo Quote Link to comment
stormense Posted September 27, 2017 Share Posted September 27, 2017 (edited) Same here. Skylake refresh I5. I try to remove CA Auto Update Applications and se if thats help. Edited September 29, 2017 by stormense Quote Link to comment
stormense Posted September 29, 2017 Share Posted September 29, 2017 (edited) Haswell Refresh Core i5-4670K, GA-B85M-DS3H Gigabyte motherboard and latest BIOS from 2015/08/25. Pray that the year 2015 BIOS help. Edited October 1, 2017 by stormense Quote Link to comment
stormense Posted October 8, 2017 Share Posted October 8, 2017 Yes it helps but the UniFi docker now freeze Unraid. Gonna uninstall it. Quote Link to comment
bonienl Posted October 8, 2017 Share Posted October 8, 2017 On 8/29/2017 at 5:00 PM, VoNpo said: Connected monitor shows repeately these two lines, never seen these before crond[1785]: exit status 137 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null crond[1785]: exit status 137 from user root /etc/rc.d//rc.diskinfo --daemon &> /dev/null This is from the preclear plugin. Check if there is an update available. Quote Link to comment
stormense Posted October 9, 2017 Share Posted October 9, 2017 (edited) On 2017-10-08 at 8:26 AM, stormense said: Yes it helps but the UniFi docker now freeze Unraid. Gonna uninstall it. Nope, now the freeze had started again. Once a day. Parity check every day. Edited October 9, 2017 by stormense Quote Link to comment
stormense Posted October 11, 2017 Share Posted October 11, 2017 Try with VM offline and still freeze once a day. Quote Link to comment
stormense Posted October 24, 2017 Share Posted October 24, 2017 I uninstall Zone Miner and then no freeze yet. De docker settings from me was to store on my Array. Quote Link to comment
stormense Posted November 5, 2017 Share Posted November 5, 2017 (edited) Fine till today. Starting Krusader and Unraid freeze. I think it was a mistake to purchase this buggy system. Fun but unstable, Ubuntu server is boring but solid. Edited November 5, 2017 by stormense Quote Link to comment
Squid Posted November 5, 2017 Share Posted November 5, 2017 (edited) 50 minutes ago, stormense said: Fine till today. Starting Krusader and Unraid freeze. I think it was a mistake to purchase this buggy system. Fun but unstable, Ubuntu server is boring but solid. Million possible reasons for random crashes. Most are related to hardware. And, without diagnostics / a syslog from Fix Common Problems in troubleshooting mode, or a screenshot of what's on the locally attached monitor, not much anyone can do to help you. Have you tried to run a memtest as a start? If you're running 4 sticks of RAM, are they a match set and on the QVL list? How's the power supply doing? Edited November 5, 2017 by Squid Quote Link to comment
stormense Posted November 6, 2017 Share Posted November 6, 2017 (edited) 21 hours ago, Squid said: Million possible reasons for random crashes. Most are related to hardware. And, without diagnostics / a syslog from Fix Common Problems in troubleshooting mode, or a screenshot of what's on the locally attached monitor, not much anyone can do to help you. Have you tried to run a memtest as a start? If you're running 4 sticks of RAM, are they a match set and on the QVL list? How's the power supply doing? Fix Common Problems: No errors found, no Warnings found I have a UPS "unclean shutdown detected of your server" and that because I must force a shutdown when the system freeze. Memtes = nothing. And here the log when I run the docker Krusader and system freezes. Nov 5 21:35:17 Tower ntpd[1715]: line 86 column 10 syntax error, unexpected T_String, expecting T_EOC Nov 5 21:35:17 Tower ntpd[1715]: syntax error in /etc/ntp.conf line 86, column 10 Nov 5 21:35:17 Tower ntpd[1715]: line 87 column 10 syntax error, unexpected T_String, expecting T_EOC Nov 5 21:35:17 Tower ntpd[1715]: syntax error in /etc/ntp.conf line 87, column 10 Nov 5 21:35:17 Tower ntpd[1715]: line 88 column 10 syntax error, unexpected T_String, expecting T_EOC Nov 5 21:35:17 Tower ntpd[1715]: syntax error in /etc/ntp.conf line 88, column 10 Nov 5 21:36:19 Tower root: Fix Common Problems: Error: unclean shutdown detected of your server ** Ignored Nov 6 19:26:27 Tower root: Fix Common Problems: Error: unclean shutdown detected of your server ** Ignored Nov 6 19:42:05 Tower root: Fix Common Problems: Error: unclean shutdown detected of your server ** Ignored Edited November 6, 2017 by stormense 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.