September 29, 20178 yr I've been having many hard crashes with rc9f. So far here is my findings for crashing. Safe mode no gui, no docker, no vm, - Runs fine Safe mode no gui, no vm - parity check running Docker running PLEX (only) - Crashes Docker running ruTorrent (only) - crashes Regular mode no gui, no vm - parity check running Docker running PLEX (only) - Crashes Docker running ruTorrent (only) - crashes Regular mode no gui, no vm - parity check canceled Docker running PLEX (only) - ran for a few hours without crashing Docker running ruTorrent (only) - crashes Attached is a diagnostic and photo. Insert existing attachment tidehunter-diagnostics-20170929-1144.zip
September 29, 20178 yr Thank you for the info, however I see nothing out of the ordinary. Since you can make it crash "at will", please boot server, and then open a telnet/ssh window using, e.g., putty, or if not available, click 'Log' button on webgui menu bar. Now make it crash and select/copy/paste the content of the logging window into a post, hopefully that will show the origin of the crash.
September 29, 20178 yr Author root@tidehunter:~# tail /var/log/syslog -f Sep 29 15:58:37 tidehunter ntpd[1815]: Listen normally on 11 vethe8a0118 [fe80::dca1:f1ff:feb1:3ee7%16]:123 Sep 29 15:58:37 tidehunter ntpd[1815]: new interface(s) found: waking up resolver Sep 29 16:00:40 tidehunter ool www[25010]: /usr/local/emhttp/plugins/advanced.buttons/script/docker 'start' 'plex' &>/dev/null & Sep 29 16:01:04 tidehunter emhttpd: req (5): startState=STARTED&cmdCheck=Check&optionCorrect=correct&csrf_token=**************** Sep 29 16:01:04 tidehunter kernel: mdcmd (50): check correct Sep 29 16:01:04 tidehunter kernel: md: recovery thread: check P ... Sep 29 16:01:04 tidehunter kernel: md: using 1536k window, over a total of 3907018532 blocks. Sep 29 16:03:51 tidehunter emhttpd: req (6): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Sep 29 16:03:51 tidehunter emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Sep 29 16:04:23 tidehunter sshd[28670]: Accepted password for root from 192.168.1.4 port 52288 ssh2 Sep 29 16:10:22 tidehunter sshd[29873]: Accepted password for root from 192.168.1.4 port 52470 ssh2 Sep 29 16:13:45 tidehunter autofan: Highest disk temp is 36C, adjusting fan speed from: OFF (0% @ 0rpm) to: 34 (13% @ 240rpm) I had plex, rutorrent and a parity check running. Edited September 29, 20178 yr by fatalfurry
September 29, 20178 yr Author Server locks up, IP is not reachable by web or ssh and Console no longer accepts keyboard commands.Sent from my Nexus 6 using Tapatalk
September 29, 20178 yr 11 minutes ago, fatalfurry said: Server locks up, IP is not reachable by web or ssh and Console no longer accepts keyboard commands. But no messages on console get output just prior to crash? Anything change with your h/w? Run memtest lately? Overclocking (hope not)? Added storage devices?
September 29, 20178 yr Author Nothing in the syslog before this happens. No ocStorage hasn't changed in a few months. I've removed my video card and USB add-on card. I run a Windows 10 vm with these two cards passed through. I was trying to trim down the areas that could cause a crash.I ran a memtest over night last night and it passed.Sent from my Nexus 6 using Tapatalk
October 8, 20178 yr Author Small update. I've diagnosed it to either be a CPU or motherboard issue. I've transitioned my unraid server to older hardware an it's been running SMOOTH for the past week. The weird crashing is still happening on the original hardware with another OS installed. This has nothing to do with unRaid. Thanks everyone! Keep calm and carry on.
Archived
This topic is now archived and is closed to further replies.