Read errors while array stopped?

[peteq]

elshaneed-diagnostics-20211012-0819.zip

 

G'day all -- long time lurker, first time poster.

 

I'm seeking a little assistance in interpreting what's going on with my server. I had a redball a few months ago, so I replaced the drive, then got another redball on the new drive which I figured might be related to the HBA card I was using (M1015). So I plugged all array drives into the motherboard SATA ports and am using the HBA for some low priority unassigned drives and an optical drive. I rebuilt back onto the failed drive, ran a parity check which returned 0 errors, and I thought we were good. I also ran short SMART self-tests on all array drives which returned no errors.

 

Things have been stable for about a week so I thought I'd solved everything but this morning I stopped the array to tweak some cache pool stuff and 2-3 minutes later got another redball on the same brand new drive (disk3). I was under the impression that no reading or writing was done while the array is stopped, so I'm confused as to why this happened this morning. As I mentioned, since the last failure I had changed the SATA port form HBA to motherboard, used a different SATA cable, and switched its position in the case/backplane -- so in my mind it's unlikely to be any of these again. Do I just have a dodgy hard drive, and if so is there anything I should be identifying in the diags that would corroborate this?

 

I've posted my diags and would appreciate any insight that the community can offer. As this is my first time posting, please let me know if I've missed any key information and I'll update as soon as I can.

 

Hardware details:

CPU – Intel Core i5 8600k

Motherboard – Gigabyte H370 Aorus Gaming 3

RAM – Team Elite 2x 16GB 2666MHz

Case – Silverstone CS380 (8-bay 3.5" hot swappable with backplane)

PSU – Silverstone Essential ET-650B

HBA – Intel M1015

 

[JorgeB]

Disk dropped offline while unmounting the filesystem, not after array stop:

 

Oct 12 08:15:17 Elshaneed kernel: XFS (md3): Unmounting Filesystem
Oct 12 08:16:20 Elshaneed kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 12 08:16:20 Elshaneed kernel: ata5.00: failed command: FLUSH CACHE EXT
Oct 12 08:16:20 Elshaneed kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 11
Oct 12 08:16:20 Elshaneed kernel:         res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Oct 12 08:16:20 Elshaneed kernel: ata5.00: status: { DRDY }
Oct 12 08:16:20 Elshaneed kernel: ata5: hard resetting link
Oct 12 08:16:26 Elshaneed kernel: ata5: link is slow to respond, please be patient (ready=0)
Oct 12 08:16:30 Elshaneed kernel: ata5: COMRESET failed (errno=-16)
Oct 12 08:16:30 Elshaneed kernel: ata5: hard resetting link
Oct 12 08:16:36 Elshaneed kernel: ata5: link is slow to respond, please be patient (ready=0)
Oct 12 08:16:40 Elshaneed kernel: ata5: COMRESET failed (errno=-16)
Oct 12 08:16:40 Elshaneed kernel: ata5: hard resetting link
Oct 12 08:16:46 Elshaneed kernel: ata5: link is slow to respond, please be patient (ready=0)
Oct 12 08:17:15 Elshaneed kernel: ata5: COMRESET failed (errno=-16)
Oct 12 08:17:15 Elshaneed kernel: ata5: limiting SATA link speed to 3.0 Gbps
Oct 12 08:17:15 Elshaneed kernel: ata5: hard resetting link
Oct 12 08:17:20 Elshaneed kernel: ata5: COMRESET failed (errno=-16)
Oct 12 08:17:20 Elshaneed kernel: ata5: reset failed, giving up
Oct 12 08:17:20 Elshaneed kernel: ata5.00: disabled

 

Since it dropped there's no SMART, but this is usually a power/connection problem.