When I'm running Parity check my speed is x00 KB/s from around 140 MB/s that I usualy get. When I looke at the sys log, I found this error getting spamed non-stop. When Parity check is not running error is going away.

 

Sep  4 21:53:23 Tower kernel: ata2.00: exception Emask 0x52 SAct 0x7f SErr 0x4070c02 action 0xe frozen
Sep  4 21:53:23 Tower kernel: ata2.00: irq_stat 0x00400000, PHY RDY changed
Sep  4 21:53:23 Tower kernel: ata2: SError: { RecovComm Proto HostInt PHYRdyChg PHYInt CommWake DevExch }
Sep  4 21:53:23 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED
Sep  4 21:53:23 Tower kernel: ata2.00: cmd 60/40:00:88:b0:19/05:00:00:00:00/40 tag 0 ncq dma 688128 in
Sep  4 21:53:23 Tower kernel:         res 40/00:20:c8:c0:19/00:00:00:00:00/40 Emask 0x52 (ATA bus error)
Sep  4 21:53:23 Tower kernel: ata2.00: status: { DRDY }
Sep  4 21:53:23 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED
Sep  4 21:53:23 Tower kernel: ata2.00: cmd 60/40:08:c8:b5:19/05:00:00:00:00/40 tag 1 ncq dma 688128 in
Sep  4 21:53:23 Tower kernel:         res 40/00:20:c8:c0:19/00:00:00:00:00/40 Emask 0x52 (ATA bus error)
Sep  4 21:53:23 Tower kernel: ata2.00: status: { DRDY }
Sep  4 21:53:23 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED
Sep  4 21:53:23 Tower kernel: ata2.00: cmd 60/80:10:08:bb:19/00:00:00:00:00/40 tag 2 ncq dma 65536 in
Sep  4 21:53:23 Tower kernel:         res 40/00:20:c8:c0:19/00:00:00:00:00/40 Emask 0x52 (ATA bus error)
Sep  4 21:53:23 Tower kernel: ata2.00: status: { DRDY }
Sep  4 21:53:23 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED
Sep  4 21:53:23 Tower kernel: ata2.00: cmd 60/40:18:88:bb:19/05:00:00:00:00/40 tag 3 ncq dma 688128 in
Sep  4 21:53:23 Tower kernel:         res 40/00:20:c8:c0:19/00:00:00:00:00/40 Emask 0x52 (ATA bus error)
Sep  4 21:53:23 Tower kernel: ata2.00: status: { DRDY }
Sep  4 21:53:23 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED
Sep  4 21:53:23 Tower kernel: ata2.00: cmd 60/40:20:c8:c0:19/05:00:00:00:00/40 tag 4 ncq dma 688128 in
Sep  4 21:53:23 Tower kernel:         res 40/00:20:c8:c0:19/00:00:00:00:00/40 Emask 0x52 (ATA bus error)
Sep  4 21:53:23 Tower kernel: ata2.00: status: { DRDY }
Sep  4 21:53:23 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED
Sep  4 21:53:23 Tower kernel: ata2.00: cmd 60/40:28:08:c6:19/05:00:00:00:00/40 tag 5 ncq dma 688128 in
Sep  4 21:53:23 Tower kernel:         res 40/00:20:c8:c0:19/00:00:00:00:00/40 Emask 0x52 (ATA bus error)
Sep  4 21:53:23 Tower kernel: ata2.00: status: { DRDY }
Sep  4 21:53:23 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED
Sep  4 21:53:23 Tower kernel: ata2.00: cmd 60/40:30:48:cb:19/05:00:00:00:00/40 tag 6 ncq dma 688128 in
Sep  4 21:53:23 Tower kernel:         res 40/00:20:c8:c0:19/00:00:00:00:00/40 Emask 0x52 (ATA bus error)
Sep  4 21:53:23 Tower kernel: ata2.00: status: { DRDY }
Sep  4 21:53:23 Tower kernel: ata2: hard resetting link
Sep  4 21:53:29 Tower kernel: ata1: found unknown device (class 0)
Sep  4 21:53:29 Tower kernel: ata2: found unknown device (class 0)
Sep  4 21:53:33 Tower kernel: ata1: softreset failed (1st FIS failed)
Sep  4 21:53:33 Tower kernel: ata1: hard resetting link
Sep  4 21:53:33 Tower kernel: ata2: softreset failed (1st FIS failed)
Sep  4 21:53:33 Tower kernel: ata2: hard resetting link
Sep  4 21:53:36 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep  4 21:53:37 Tower kernel: ata2.00: configured for UDMA/33
Sep  4 21:53:37 Tower kernel: ata2: EH complete
Sep  4 21:53:38 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep  4 21:53:38 Tower kernel: ata1.00: configured for UDMA/33
Sep  4 21:53:38 Tower kernel: ata1: EH complete

 

tower-diagnostics-20230904-2144.zip

Edited September 5, 20232 yr by Amiaki

Check/replace cables for disk2 and try again.

@JorgeB Looks like resetting conection helpled. I diid all the drive just in case but, I'm sure it was disk2. How did you figure it out in the logs?

Edited September 5, 20232 yr by Amiaki

The problem looked like a connection issue.