I woke up with my whole server not responding, I couldn't SSH or download the logs. So I force rebooted the server and when it came back up my disk5 could had a red x. Please see attached diagnostics.

unnas-diagnostics-20191227-0836.zip

Because of the reboot we can't see what happened, but the disk looks fine, I would recommend replacing/swapping cables just to rule them out and rebuild on top.

Any recommendations going forward to help capture the logs before unraid crashes? 

 

 

If it's crashing regularly see here:

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

 

5minutes after rebooting the server and start the parity check/data rebuild it crashes again.

Please see the logs attachedunnas-diagnostics-20191227-0849.zip

Diags are again just after rebooting.

I'm not sure where to find the syslogs after it crashes but I think this is it. Please take a look.

Thank you

syslog

Looks like a problem with the HBA, it's constantly faulting:

 

Dec 27 10:02:17 unNAS kernel: mpt2sas_cm0: fault_state(0x2622)!

Make sure it's well seated and cooled, you can also try a different PCI slot if availing, failing that try a different HBA.

 

Tried a different PCIe slot and I'm still getting the same fault_state error when rebuilding data. Is the only way to rule it out purchasing another Dell H310? How often do these fail?

Not common, and that error is even more uncommon, I'm more used to see the "sas non-operational" error, but next step would be to test with another HBA, or if it's easier for you try that HBA in another server.

Unfortunately I don't have another HBA on hand. I'll probably buy another one from ebay. I heard there are a lot of fakes and perhaps the one I purchased was a fake since it was cheap and I flashed it myself.