problems after replacing drive rebuilding

threiner · October 30, 2023

i get this error after replacing a drive

Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/40:10:d8:de:03/05:00:00:00:00/40 tag 2 ncq dma 688128 in
Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/80:18:18:e4:03/00:00:00:00:00/40 tag 3 ncq dma 65536 in
Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/40:48:58:87:04/05:00:00:00:00/40 tag 9 ncq dma 688128 in
Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:49:34 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:49:34 Tower kernel: ata9.00: cmd 60/40:f0:18:cf:03/05:00:00:00:00/40 tag 30 ncq dma 688128 in
Oct 30 11:49:34 Tower kernel: res 40/00:58:d8:0f:05/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:49:34 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:49:34 Tower kernel: ata9: hard resetting link
Oct 30 11:49:34 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320)
Oct 30 11:49:35 Tower kernel: ata9.00: configured for UDMA/133
Oct 30 11:49:35 Tower kernel: ata9: EH complete
Oct 30 11:50:15 Tower kernel: ata9.00: exception Emask 0x10 SAct 0xc00400 SErr 0x4010000 action 0xe frozen
Oct 30 11:50:15 Tower kernel: ata9.00: irq_stat 0x80400040, connection status changed
Oct 30 11:50:15 Tower kernel: ata9: SError: { PHYRdyChg DevExch }
Oct 30 11:50:15 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:50:15 Tower kernel: ata9.00: cmd 60/40:50:58:fa:05/05:00:00:00:00/40 tag 10 ncq dma 688128 in
Oct 30 11:50:15 Tower kernel: res 40/00:60:d8:5b:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:50:15 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:50:15 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:50:15 Tower kernel: ata9.00: cmd 60/40:b0:d8:a4:05/05:00:00:00:00/40 tag 22 ncq dma 688128 in
Oct 30 11:50:15 Tower kernel: res 40/00:60:d8:5b:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:50:15 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:50:15 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:50:15 Tower kernel: ata9.00: cmd 60/40:b8:18:aa:05/05:00:00:00:00/40 tag 23 ncq dma 688128 in
Oct 30 11:50:15 Tower kernel: res 40/00:60:d8:5b:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:50:15 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:50:15 Tower kernel: ata9: hard resetting link
Oct 30 11:50:16 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320)
Oct 30 11:50:16 Tower kernel: ata9.00: configured for UDMA/133
Oct 30 11:50:16 Tower kernel: ata9: EH complete
Oct 30 11:50:47 Tower kernel: ata9: limiting SATA link speed to 1.5 Gbps
Oct 30 11:50:47 Tower kernel: ata9.00: exception Emask 0x10 SAct 0x380280 SErr 0x4010000 action 0xe frozen
Oct 30 11:50:47 Tower kernel: ata9.00: irq_stat 0x80400040, connection status changed
Oct 30 11:50:47 Tower kernel: ata9: SError: { PHYRdyChg DevExch }
Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:38:d8:86:06/05:00:00:00:00/40 tag 7 ncq dma 688128 in
Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:48:18:d7:06/05:00:00:00:00/40 tag 9 ncq dma 688128 in
Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:98:58:12:07/05:00:00:00:00/40 tag 19 ncq dma 688128 in
Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/40:a0:98:17:07/05:00:00:00:00/40 tag 20 ncq dma 688128 in
Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:50:47 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:50:47 Tower kernel: ata9.00: cmd 60/80:a8:d8:1c:07/00:00:00:00:00/40 tag 21 ncq dma 65536 in
Oct 30 11:50:47 Tower kernel: res 40/00:00:d8:3c:07/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:50:47 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:50:47 Tower kernel: ata9: hard resetting link
Oct 30 11:50:48 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 310)
Oct 30 11:50:48 Tower kernel: ata9.00: configured for UDMA/133
Oct 30 11:50:48 Tower kernel: ata9: EH complete
Oct 30 11:51:20 Tower kernel: ata9.00: exception Emask 0x10 SAct 0xe400000 SErr 0x4010000 action 0xe frozen
Oct 30 11:51:20 Tower kernel: ata9.00: irq_stat 0x80400040, connection status changed
Oct 30 11:51:20 Tower kernel: ata9: SError: { PHYRdyChg DevExch }
Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/40:b0:58:05:08/05:00:00:00:00/40 tag 22 ncq dma 688128 in
Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/40:c8:58:7c:07/05:00:00:00:00/40 tag 25 ncq dma 688128 in
Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/40:d0:98:81:07/05:00:00:00:00/40 tag 26 ncq dma 688128 in
Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:51:20 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED
Oct 30 11:51:20 Tower kernel: ata9.00: cmd 60/80:d8:d8:86:07/00:00:00:00:00/40 tag 27 ncq dma 65536 in
Oct 30 11:51:20 Tower kernel: res 40/00:80:d8:63:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 11:51:20 Tower kernel: ata9.00: status: { DRDY }
Oct 30 11:51:20 Tower kernel: ata9: hard resetting link
Oct 30 11:51:21 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 310)
Oct 30 11:51:21 Tower kernel: ata9.00: configured for UDMA/133
Oct 30 11:51:21 Tower kernel: ata9: EH complete

JorgeB · October 30, 2023

That's usually a power/connection problem, replace/swap both cables.

threiner · October 30, 2023

33 minutes ago, JorgeB said:

That's usually a power/connection problem, replace/swap both cables.

how do i find out what drive it is ?

JorgeB · October 30, 2023

You'd need to post the diags.

threiner · October 30, 2023

2 minutes ago, JorgeB said:

You'd need to post the diags.

sure

tower-diagnostics-20231030-1423.zip

JorgeB · October 30, 2023

Disk3

threiner · October 30, 2023

thank you can i find this also out allone? where do i need to look ?

JorgeB · October 30, 2023

lsscsi.txt in the diags will map the ATA# to the disk identifier, but depending on the controller it may not show the ATA# so sometimes you need to use other ways.

threiner · October 30, 2023

now i get this...

Oct 30 16:14:37 Tower kernel: ata1: EH complete
Oct 30 16:14:37 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x20000000 SErr 0x4890000 action 0xe frozen
Oct 30 16:14:37 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Oct 30 16:14:37 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
Oct 30 16:14:37 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Oct 30 16:14:37 Tower kernel: ata1.00: cmd 60/40:e8:d8:1b:01/05:00:00:00:00/40 tag 29 ncq dma 688128 in
Oct 30 16:14:37 Tower kernel: res 40/00:e8:d8:1b:01/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 16:14:37 Tower kernel: ata1.00: status: { DRDY }
Oct 30 16:14:37 Tower kernel: ata1: hard resetting link
Oct 30 16:14:43 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Oct 30 16:14:46 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Oct 30 16:14:46 Tower kernel: ata1.00: configured for UDMA/133
Oct 30 16:14:46 Tower kernel: ata1: EH complete
Oct 30 16:14:46 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps
Oct 30 16:14:46 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x600 SErr 0x4890000 action 0xe frozen
Oct 30 16:14:46 Tower kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Oct 30 16:14:46 Tower kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
Oct 30 16:14:46 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Oct 30 16:14:46 Tower kernel: ata1.00: cmd 60/40:48:98:8b:01/05:00:00:00:00/40 tag 9 ncq dma 688128 in
Oct 30 16:14:46 Tower kernel: res 40/00:48:98:8b:01/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 16:14:46 Tower kernel: ata1.00: status: { DRDY }
Oct 30 16:14:46 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Oct 30 16:14:46 Tower kernel: ata1.00: cmd 60/80:50:d8:90:01/00:00:00:00:00/40 tag 10 ncq dma 65536 in
Oct 30 16:14:46 Tower kernel: res 40/00:48:98:8b:01/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 30 16:14:46 Tower kernel: ata1.00: status: { DRDY }
Oct 30 16:14:46 Tower kernel: ata1: hard resetting link

threiner · October 30, 2023

tower-diagnostics-20231030-1616.zip

JorgeB · October 30, 2023

It's still disk3, did you swap ports or cables?

threiner · October 30, 2023

i swap cabels and ports, the drive is also precleared without any issue... i am starting to think it could be an issue with the powersuply as the errors are quite random

threiner · November 12, 2023

I changed the power supply, and the errors disappeared.

problems after replacing drive rebuilding

Recommended Posts

threiner

Link to comment

JorgeB

Link to comment

threiner

Link to comment

JorgeB

Link to comment

threiner

Link to comment

JorgeB

Link to comment

threiner

Link to comment

JorgeB

Link to comment

threiner

Link to comment

threiner

Link to comment

JorgeB

Link to comment

threiner

Link to comment

threiner

Link to comment

Join the conversation