HellDiverUK Posted June 22, 2015 Share Posted June 22, 2015 Jun 22 02:23:10 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x3800000 SErr 0x280100 action 0x6 frozen Jun 22 02:23:10 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error Jun 22 02:23:10 Tower kernel: ata2: SError: { UnrecovData 10B8B BadCRC } Jun 22 02:23:10 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Jun 22 02:23:10 Tower kernel: ata2.00: cmd 60/40:b8:40:51:29/05:00:05:00:00/40 tag 23 ncq 688128 in Jun 22 02:23:10 Tower kernel: res 40/00:bc:40:51:29/00:00:05:00:00/40 Emask 0x10 (ATA bus error) Jun 22 02:23:10 Tower kernel: ata2.00: status: { DRDY } Jun 22 02:23:10 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Jun 22 02:23:10 Tower kernel: ata2.00: cmd 60/40:c0:80:56:29/05:00:05:00:00/40 tag 24 ncq 688128 in Jun 22 02:23:10 Tower kernel: res 40/00:bc:40:51:29/00:00:05:00:00/40 Emask 0x10 (ATA bus error) Jun 22 02:23:10 Tower kernel: ata2.00: status: { DRDY } Jun 22 02:23:10 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Jun 22 02:23:10 Tower kernel: ata2.00: cmd 60/80:c8:c0:5b:29/05:00:05:00:00/40 tag 25 ncq 720896 in Jun 22 02:23:10 Tower kernel: res 40/00:bc:40:51:29/00:00:05:00:00/40 Emask 0x10 (ATA bus error) Jun 22 02:23:10 Tower kernel: ata2.00: status: { DRDY } Jun 22 02:23:10 Tower kernel: ata2: hard resetting link Jun 22 02:23:10 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 22 02:23:10 Tower kernel: ata2.00: configured for UDMA/33 Jun 22 02:23:10 Tower kernel: ata2: EH complete Jun 22 02:23:12 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x78000 SErr 0x280100 action 0x6 frozen Jun 22 02:23:12 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error Jun 22 02:23:12 Tower kernel: ata2: SError: { UnrecovData 10B8B BadCRC } Jun 22 02:23:12 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Jun 22 02:23:12 Tower kernel: ata2.00: cmd 60/40:78:40:61:2c/05:00:05:00:00/40 tag 15 ncq 688128 in Jun 22 02:23:12 Tower kernel: res 40/00:7c:40:61:2c/00:00:05:00:00/40 Emask 0x10 (ATA bus error) Jun 22 02:23:12 Tower kernel: ata2.00: status: { DRDY } Jun 22 02:23:12 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Jun 22 02:23:12 Tower kernel: ata2.00: cmd 60/40:80:80:66:2c/05:00:05:00:00/40 tag 16 ncq 688128 in Jun 22 02:23:12 Tower kernel: res 40/00:7c:40:61:2c/00:00:05:00:00/40 Emask 0x10 (ATA bus error) Jun 22 02:23:12 Tower kernel: ata2.00: status: { DRDY } Jun 22 02:23:12 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Jun 22 02:23:12 Tower kernel: ata2.00: cmd 60/40:88:c0:6b:2c/05:00:05:00:00/40 tag 17 ncq 688128 in Jun 22 02:23:12 Tower kernel: res 40/00:7c:40:61:2c/00:00:05:00:00/40 Emask 0x10 (ATA bus error) Jun 22 02:23:12 Tower kernel: ata2.00: status: { DRDY } Jun 22 02:23:12 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Jun 22 02:23:12 Tower kernel: ata2.00: cmd 60/40:90:00:71:2c/00:00:05:00:00/40 tag 18 ncq 32768 in Jun 22 02:23:12 Tower kernel: res 40/00:7c:40:61:2c/00:00:05:00:00/40 Emask 0x10 (ATA bus error) Jun 22 02:23:12 Tower kernel: ata2.00: status: { DRDY } Jun 22 02:23:12 Tower kernel: ata2: hard resetting link Jun 22 02:23:12 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 22 02:23:12 Tower kernel: ata2.00: configured for UDMA/33 Jun 22 02:23:12 Tower kernel: ata2: EH complete Should I be worried? I've had an issue with the backplane in this machine before, when running Windows. The backplane is running off the Marvell controller on a Supermicro X10SBA. Link to comment
itimpi Posted June 22, 2015 Share Posted June 22, 2015 Those sorts of errors tend to indicate a connection issue (sata/power) or possibly a power supply unable to provide sufficient power. Link to comment
HellDiverUK Posted June 22, 2015 Author Share Posted June 22, 2015 I'm pretty sure it's the backplane. The same bay gave issues when the machine was running Windows (timeouts leading to lack of boot). Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.