Hi all. Can someone help me troubleshoot. I finally got things setup the way I wanted and decided it was time to leave the server up and running. Now I have an issue where the server crashes and reboots. See diagnostic report attached. I have not gotten ones for most recent crash where it did not reboot itself. Any help is appreciated. 

anontower-diagnostics-20230926-2342.zip

Enable the syslog server and post that after a crash.

 

So, I turned on syslog server. My parity drive on the array had a red x. I ran self test everything looked fine. I unmounted started it up. Stopped it. Reassigned same drive. Passed parity check (supposedly). Cause when I came to check the array was stopped. When I started it back up the red x was back. Ran another self test short one this time and the server rebooted. See diagnostics attached. 

tower-diagnostics-20231001-0711.zip

Something I just noticed. After this reboot the drive is not even showing on the unassigned devices list (bizarre). 

Diags are after rebooting so we can't see what happened but if the drive is not appearing swap cables with a different disk to see if it's a connection issue or bad disk.

That's weird I definitely ran diagnostics after the server rebooted. No useful info? 

10 minutes ago, myongha said:

That's weird I definitely ran diagnostics after the server rebooted

That's what I posted, syslog starts over after every reboot, so not much to see.

Unplugged hard drive. Reseated sas card. Moves power connector around for sas. Removed random molex that was not being used. Turned system on wiped drive with issue. Passed smart test  Reassigned drive as parity. Started the array and parity sync worked. Also unscheduled mover (heard this was a problem with 6.12.x) Array has been up a couple days. Tbd