Posted August 18, 20213 yr How do I tell which drive is ATA2.00? Is it the cable? Drive? Controller? Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/40:b8:d0:fe:f0/05:00:5d:00:00/40 tag 23 ncq dma 688128 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/80:c0:10:04:f1/00:00:5d:00:00/40 tag 24 ncq dma 65536 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/40:c8:90:04:f1/05:00:5d:00:00/40 tag 25 ncq dma 688128 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/40:d0:d0:09:f1/05:00:5d:00:00/40 tag 26 ncq dma 688128 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/40:d8:10:0f:f1/01:00:5d:00:00/40 tag 27 ncq dma 163840 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2: hard resetting link Aug 17 18:21:27 UNRAID kernel: ata2: link is slow to respond, please be patient (ready=0) Aug 17 18:21:31 UNRAID kernel: ata2: COMRESET failed (errno=-16) Aug 17 18:21:31 UNRAID kernel: ata2: hard resetting link Aug 17 18:21:37 UNRAID kernel: ata2: link is slow to respond, please be patient (ready=0) Aug 17 18:21:37 UNRAID kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 17 18:21:38 UNRAID kernel: ata2.00: configured for UDMA/33 Aug 17 18:21:38 UNRAID kernel: ata2: EH complete Aug 17 18:21:38 UNRAID kernel: ata2.00: exception Emask 0x10 SAct 0x7f0 SErr 0x4890000 action 0xe frozen Aug 17 18:21:38 UNRAID kernel: ata2.00: irq_stat 0x08400040, interface fatal error, connection status changed Aug 17 18:21:38 UNRAID kernel: ata2: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/00:20:90:a1:f1/04:00:5d:00:00/40 tag 4 ncq dma 524288 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/40:28:90:a5:f1/05:00:5d:00:00/40 tag 5 ncq dma 688128 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/40:30:d0:aa:f1/05:00:5d:00:00/40 tag 6 ncq dma 688128 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/00:38:10:b0:f1/03:00:5d:00:00/40 tag 7 ncq dma 393216 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/40:40:10:b3:f1/05:00:5d:00:00/40 tag 8 ncq dma 688128 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/40:48:50:b8:f1/05:00:5d:00:00/40 tag 9 ncq dma 688128 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/00:50:90:bd:f1/04:00:5d:00:00/40 tag 10 ncq dma 524288 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2: hard resetting link Aug 17 18:21:44 UNRAID kernel: ata2: link is slow to respond, please be patient (ready=0) Aug 17 18:21:48 UNRAID kernel: ata2: COMRESET failed (errno=-16) Aug 17 18:21:48 UNRAID kernel: ata2: hard resetting link unraid-diagnostics-20210817-1822.zip
August 18, 20213 yr Community Expert 1 hour ago, claira said: How do I tell which drive is ATA2.00? Aug 17 12:39:27 UNRAID kernel: ata2.00: ATA-11: ST14000NE0008-2JK101, ZHZ69WVE, EN01, max UDMA/133 Aug 17 12:39:27 UNRAID kernel: ata5.00: ATA-11: ST14000NM001G-2KJ103, ZL29Q6L7, SN02, max UDMA/133 Aug 17 12:42:02 UNRAID kernel: md: import disk9: (sdb) ST14000NE0008-2JK101_ZHZ69WVE size: 13672382412 Aug 17 12:42:02 UNRAID kernel: md: import disk29: (sdd) ST14000NM001G-2KJ103_ZL29Q6L7 size: 13672382412 Aug 17 12:49:49 UNRAID kernel: md: recovery thread: recon D9 Q ... Aug 17 12:53:03 UNRAID kernel: ata5: hard resetting link Aug 17 12:59:19 UNRAID kernel: ata2: hard resetting link So, disk9 (D9) and disk29 (parity2, Q), the 2 rebuilding disks. SMART for both looks OK. Anything these disks have in common (controller, power cable)?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.