server crash/unresponsive

[XceRpt]

I've ran fine for 2months no issues. parity was due to start on 3/1 . Came home from work and everything is unresponsive . I cant see anything in the log to pinpoint the problem other than a correction then it was offline apparently until i rebooted at 19:36. I've had issues in the past of crashing only during parity check and changed ram speed in bios and thought issues were resolved. Any help appreciated. Thanks.

syslog-192.168.0.229.log

tower-diagnostics-20220301-1951.zip

Edited March 2, 2022 by XceRpt

[ChatNoir]

6 hours ago, XceRpt said:

parity was due to start on 3/1

Looks like it did start indeed :

Mar  1 00:00:07 Tower kernel: mdcmd (38): check 
Mar  1 00:00:07 Tower kernel: md: recovery thread: check P ...
Mar  1 00:00:30 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar  1 07:23:09 Tower kernel: md: recovery thread: P corrected, sector=9371259176
Mar  1 07:31:39 Tower kernel: md: recovery thread: P corrected, sector=9530211888
Mar  1 19:36:47 Tower root: Delaying execution of fix common problems scan for 10 minutes
Mar  1 19:36:47 Tower unassigned.devices: Mounting 'Auto Mount' Devices...
Mar  1 19:36:47 Tower emhttpd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/nvidia.patch/script" >/dev/null 2>&1

 

While your RAM speed do look good, did you also check the C-State part of the FAQ ?

 

[XceRpt]

18 hours ago, ChatNoir said:

 

While your RAM speed do look good, did you also check the C-State part of the FAQ ?

I think i've went thru that before, but will double check. As of right now i restarted parity and it's at 84% and still going. I was just curious if there was anyway to tell why it happened but theres not much info in the log.