Looking for a sanity check here.  Parity check kicked off last night at 6PM.  A few minutes into the parity check a bunch of errors like the below popped up.  I've ordered replacement SAS->SATA cables for my HBA drives, and replacement SATA cables for my motherboard-connected drives.  Anything else I should be looking for?  I've attached diagnostics.

 

Oct  6 18:10:08 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED
Oct  6 18:10:08 Tower kernel: ata3.00: cmd 60/f8:a8:68:53:ab/03:00:0c:00:00/40 tag 21 ncq dma 520192 in
Oct  6 18:10:08 Tower kernel:         res 40/00:80:60:3f:ab/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Oct  6 18:10:08 Tower kernel: ata3.00: status: { DRDY }
Oct  6 18:10:08 Tower kernel: ata3: hard resetting link
Oct  6 18:10:14 Tower kernel: ata3: found unknown device (class 0)
Oct  6 18:10:18 Tower kernel: ata3: softreset failed (1st FIS failed)
Oct  6 18:10:18 Tower kernel: ata3: hard resetting link
Oct  6 18:10:24 Tower kernel: ata3: found unknown device (class 0)
Oct  6 18:10:26 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct  6 18:10:26 Tower kernel: ata3.00: configured for UDMA/133
Oct  6 18:10:26 Tower kernel: ata3: EH complete

 

tower-diagnostics-20231007-0824.zip

Edited October 7, 20232 yr by adammerkley

You might also want to check the power cabling to the drives

8 minutes ago, itimpi said:

You might also want to check the power cabling to the drives

 

Ah good point.  I'll check that too.  Thanks!

I replaced all of the SAS-SATA cables for drives connected to my HBA, and the SATA cables for drives connected to the motherboard.  I also removed the molex splitters I had deployed to deliver power to the backplane/drive cages.

 

Just completed a parity check with no errors.