Unraid Consistently Crashes at 4.2% during Parity Check

[PhoenixI7]

I moved my drives and raid card over to a new system (Intel R2000 server), and now the system crashes to the boot screen whenever I run a parity check (specifically 4.2% in). Initially I thought it could be the CPU overheating, so I replaced the thermal paste because it was old and dry. That didn't help. I saw another thread saying that it could be the PSU but I doubt that is the problem as I have redundant PSUs and the problem still occurs with any combination of them. To me, this seems like a hardware problem, but I've spent the last day ruling out every hardware problem I can think of and it has changed nothing so I am probably wrong. In the process of moving the drives over, I had to create a new USB drive to run Unraid because with the old one the server wouldn't connect to my network. That USB drive is my current suspect. I still have my old USB drive and I am going to try a parity check while running Unraid off that, but if that doesn't work I have no clue what to do. 

 

Edit: the old USB drive failed parity as well 

Edited March 14, 2020 by PhoenixI7

[trurl]

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

 

Also, setup Syslog Server so your syslog will be saved from before the crash:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

 

Have you done memtest?

 

[PhoenixI7]

Here is the zip file

 

I just set up the Syslog Server to mirror to flash

 

Last time I ran memtest it crashed but that was before I replaced the thermal paste so I will run it again.

 

 

tower-diagnostics-20200314-1751.zip

[trurl]

The array is not started in those diagnostics. Get us new diagnostics after starting the array.

[PhoenixI7]

tower-diagnostics-20200314-1910.zip

[JorgeB]

Try enabling the syslog server/mirror then start a parity check and post the syslog after it crashes.

[PhoenixI7]

syslog

[trurl]

The diagnostics you posted earlier indicate parity was invalid. You said you were checking parity, but if parity is invalid then I assume you hadn't built parity yet. So instead of checking parity you were building it. Is that correct?

 

Is that syslog after a crash? Doesn't look like any parity disk was assigned.

[JorgeB]

If it's crashing between logs nothing is being logged, most likely a hardware problem.

[PhoenixI7]

I tried removing the drives to see if it crashes and found that it still does. Which means that parity is not the problem. It keeps crashing at an uptime of 21 - 22 minutes with and without the drives, so it might even be crashing. It could just be rebooting after 20 minutes for some reason. 

Edited March 17, 2020 by PhoenixI7

[PhoenixI7]

I disabled OS watchdog and it hasn't rebooted yet so that appears to have been the problem all along. 

[not2sure]

If you see my post from January 7, 2019. 
I was having problems like this. I shut down the server and pulled the CMOS battery out for a few minutes. Inserted the battery, restarted and the parity rebuild was successful after I did this. Good luck.