Hello,

Two hours ago, two disks were disabled, so I followed the normal procedure: stop, remove, add them back, and restart. However, the same two disks were disabled again immediately, leading to all disks showing as unavailable.

When I attempted this process a second time, the second parity disk also became disabled. Could you please help with this issue? I've attached the diagnostics

tower-diagnostics-20241116-1948.zip

Edited November 16, 20241 yr by alhatmy

Update; Implemented a New Config > Same slots > Parity is already valid. So far, it's been working fine for about 10 minutes. Could you explain what might have caused this issue and if it's likely to happen again?

 

Question: Can I initiate a new parity check now? Or to remove and reads the 1st Parity (disabled and never complete the built)? 

 

I've also attached new diagnostics.
 

tower-diagnostics-20241116-2229.zip

Edited November 16, 20241 yr by alhatmy

It was a problem with the HBA:

 

Nov 16 19:29:55 Tower kernel: mpt2sas_cm0: SAS host is non-operational !!!!

 

If it happens again, make sure it's well seated and sufficiently cooled, you can also try a different PCIe slot.

3 minutes ago, JorgeB said:

It was a problem with the HBA:

 

Nov 16 19:29:55 Tower kernel: mpt2sas_cm0: SAS host is non-operational !!!!

 

If it happens again, make sure it's well seated and sufficiently cooled, you can also try a different PCIe slot.

 

Thanks. I'm currently using two HBAs, but I'm not certain which ones.. Or it's from the motherboard. So far, I haven't made any changes and everything has been working for 12+ hours.
 

Question: Can I initiate a new parity check now? Or should I remove and re-add the first parity "which was disabled and never completed building - to rebuild"?

 

If the parity drive is no longer disabled then you can simply run a parity check as hopefully it is (or at least mostly) correct.  You might want to make it a 'Correcting' check in case there are a few parity errors that need fixing.