Cautiously Back in the Saddle

[ere109]

Supermicro finally replaced my motherboard. (The LSI SAS controller seemed to have died in the old board shortly after install.) I didn't want to neatly pack everything back together, only to discover a problem. So I'm going to run the system open and leave the door to my office closed for a day or so. It's been running for six hours with one drive connected to the new LSI controller. Before bed, I'll shut down and connect five more drives to the controller - my RaidZ2 pool. That's the spot I'm scared of. It was shortly after I finished transferring about 12TB of data to my pool that the old controller bit the dust. Supermicro said they couldn't reproduce the issue in two nights of testing, so I don't have definitive proof/confidence that it isn't something. But I'm working on it, and will update as I go.

 

[ere109]

I just spent three hours installing new SATA cables and cleaning the case up, before I hit the power. My GUI is unresponsive, which has often been a sign that a drive went down. Not good. My only remaining opinions:
* Bad PSU (currently running a Corsair RM550x, system only reports 190w usage)
* Bad Seagate Hard Drives (five running together in close quarters, and they do get hot to the touch)

Any other logical troubleshooting steps? I've got a spare PSU, so could start there, unless someone else has a better idea.

 

[ere109]

After a reboot, the GUI is back up - and I have access to my ZFS shares.