Hello

 

Having corrected a 1000+ Paity Sync Errors , and replaced a disk last month, had errors on Night 1 of the new parity Check, so have stopped the check , and im now running a correcting check.

 

Can anyone see from the logs, why this is happening?

mordor-diagnostics-20250502-1529.zip

Were they all correcting checks?

I ran a correcting check, that corrected the errors, then ran a non correcting check, which returned no errors.

Then on this months scheduled check that ran last night, it picked up 51, so I stopped that check and starting a correcting check , which is 33% complete , and has corrected the 51 errors.

 

I have noted this from the logs though

 

May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:60:b8:b9:be/04:00:51:02:00/40 tag 12 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)

 

Which doesnt look good

May 2 15:36:02 Mordor kernel: ata4.00: exception Emask 0x10 SAct 0x900038e0 SErr 0x48d0002 action 0xe frozen May 2 15:36:02 Mordor kernel: ata4.00: irq_stat 0x04400040, connection status changed May 2 15:36:02 Mordor kernel: ata4: SError: { RecovComm PHYRdyChg CommWake 10B8B LinkSeq DevExch } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:28:b8:ad:be/04:00:51:02:00/40 tag 5 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:30:b8:b1:be/04:00:51:02:00/40 tag 6 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:38:b8:c1:be/04:00:51:02:00/40 tag 7 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:58:b8:b5:be/04:00:51:02:00/40 tag 11 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:60:b8:b9:be/04:00:51:02:00/40 tag 12 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:68:b8:bd:be/04:00:51:02:00/40 tag 13 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:e0:b8:a5:be/04:00:51:02:00/40 tag 28 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4.00: failed command: READ FPDMA QUEUED May 2 15:36:02 Mordor kernel: ata4.00: cmd 60/00:f8:b8:a9:be/04:00:51:02:00/40 tag 31 ncq dma 524288 in May 2 15:36:02 Mordor kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) May 2 15:36:02 Mordor kernel: ata4.00: status: { DRDY } May 2 15:36:02 Mordor kernel: ata4: hard resetting link May 2 15:36:08 Mordor kernel: ata4: link is slow to respond, please be patient (ready=0) May 2 15:36:12 Mordor kernel: ata4: COMRESET failed (errno=-16) May 2 15:36:12 Mordor kernel: ata4: hard resetting link May 2 15:36:17 Mordor kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 2 15:36:17 Mordor kernel: ata4.00: configured for UDMA/133 May 2 15:36:17 Mordor kernel: ata4: EH complete

Reboot, run a correcting check now, if it finds errors run another one, all without rebooting, and post new diags.

Shall do, will take a few days, but will let you know

Correcting check has now finished, logs attached, now rebooting, and will run another check

mordor-diagnostics-20250503-1522.zip

17 hours ago, mraerosmith said:

now rebooting

It would be better without rebooting, but still post those if it finds more errors.

Finished with no errors, logs attached.

 

Anything else I need 2 to be aware of?

mordor-diagnostics-20250505-0917.zip

Should be fine, but just keep monitoring future checks.

A further question, if the parity check has failed and then is ok and repairs itself after the check, is there any chance of file data corruption?

1 hour ago, mraerosmith said:

A further question, if the parity check has failed and then is ok and repairs itself after the check, is there any chance of file data corruption?

If the data was already corrupt then fixing parity to correspond to the disks is not going to fix that issue.   If you are concerned about that you want a way to detect data corruption.   For XFS this means keeping external checksums while BTEFS and ZFS have built-in detection of data corruption.   Note that none of these will always correct corruption, just detect it.

im using btrfs for my array disks, im not concerned per say, just the 2nd month I have had parity errors, and wondering if this is damging my files, how do I tell with btrfs

Since it btrfs, you can scrub the disks to confirm all the data is OK