Bad drive alert and now no matter what I try to replace it with I get errors

RAINMAN · December 11, 2016

I had a smart alert for a bad drive. I replaced this with a brand new 4tb but I am still getting errors in the unraid log.

Dec 11 11:25:33 FILESERVER kernel: ata6.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 11 11:25:33 FILESERVER kernel: ata6.01: failed command: READ DMA EXT

Dec 11 11:25:33 FILESERVER kernel: ata6.01: cmd 25/00:00:cf:1c:85/00:02:02:00:00/f0 tag 0 dma 262144 in

Dec 11 11:25:33 FILESERVER kernel: res 40/00:00:0f:1c:62/00:02:00:00:00/f0 Emask 0x4 (timeout)

Dec 11 11:25:33 FILESERVER kernel: ata6.01: status: { DRDY }

Dec 11 11:25:33 FILESERVER kernel: ata6: soft resetting link

Dec 11 11:25:34 FILESERVER kernel: ata6.00: configured for UDMA/100

Dec 11 11:25:34 FILESERVER kernel: ata6.01: configured for UDMA/33

Dec 11 11:25:34 FILESERVER kernel: ata6: EH complete

Dec 11 11:26:06 FILESERVER kernel: ata6: lost interrupt (Status 0x50)

Dec 11 11:26:06 FILESERVER kernel: ata6.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 11 11:26:06 FILESERVER kernel: ata6.01: failed command: READ DMA EXT

Dec 11 11:26:06 FILESERVER kernel: ata6.01: cmd 25/00:00:0f:70:89/00:02:02:00:00/f0 tag 0 dma 262144 in

Dec 11 11:26:06 FILESERVER kernel: res 40/00:00:0f:1c:62/00:02:00:00:00/f0 Emask 0x4 (timeout)

Dec 11 11:26:06 FILESERVER kernel: ata6.01: status: { DRDY }

Dec 11 11:26:06 FILESERVER kernel: ata6: soft resetting link

Dec 11 11:26:07 FILESERVER kernel: ata6.00: configured for UDMA/100

Dec 11 11:26:07 FILESERVER kernel: ata6.01: configured for UDMA/33

Dec 11 11:26:07 FILESERVER kernel: ata6: EH complete

Dec 11 11:26:44 FILESERVER kernel: ata6: lost interrupt (Status 0x50)

Dec 11 11:26:44 FILESERVER kernel: ata6.01: limiting speed to PIO4

Dec 11 11:26:44 FILESERVER kernel: ata6.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 11 11:26:44 FILESERVER kernel: ata6.01: failed command: READ DMA EXT

Dec 11 11:26:44 FILESERVER kernel: ata6.01: cmd 25/00:00:0f:ea:9c/00:02:02:00:00/f0 tag 0 dma 262144 in

Dec 11 11:26:44 FILESERVER kernel: res 40/00:00:0f:1c:62/00:02:00:00:00/f0 Emask 0x4 (timeout)

Dec 11 11:26:44 FILESERVER kernel: ata6.01: status: { DRDY }

Dec 11 11:26:44 FILESERVER kernel: ata6: soft resetting link

Dec 11 11:26:44 FILESERVER kernel: ata6.00: configured for UDMA/100

Dec 11 11:26:44 FILESERVER kernel: ata6.01: configured for PIO4

Dec 11 11:26:44 FILESERVER kernel: ata6: EH complete

I tried to replace the SATA cable with a brand new one with no change. I changed the port on the sata card (and my SSD is also on that card without any issues) but I am still getting these exceptions. Once it configures for PIO4 it stops erroring but then the CPU usage spikes up to like 40+ and the system is unusable until I stop the parity sync.

I'm testing the drive that said it was bad in another PC and so far it has no reported errors so I am tending to think its not a drive issue.

Im not sure what to check anymore.

Attached system diagnostics.

fileserver-diagnostics-20161211-1131.zip

RAINMAN · December 11, 2016

I noticed in the system log that ata6.01 is actually the 2tb drive. So i replaced the cables on both my 2tb drives also. didnt help...

Dec 11 11:02:33 FILESERVER kernel: ata6.01: ATA-8: ST2000DL003-9VT166, 5YD1KE5J, CC32, max UDMA/133
Dec 11 11:02:33 FILESERVER kernel: ata6.01: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32)

JorgeB · December 11, 2016

You have legacy IDE enable, go to board bios and change SATA controller to AHCI.

RAINMAN · December 11, 2016

Ya it does look like that got changed somehow. I have set it back to AHCI mode and i moved the drives to a different port.

I'm wondering if its a drive problem? That would suck since I already have one that needs to be rebuilt. I have a spare 2tb one but I cant rebuild 2 drives at the same time.

ec 11 13:07:53 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen
Dec 11 13:07:53 FILESERVER kernel: ata9.00: irq_stat 0x80400000, PHY RDY changed

Dec 11 13:07:53 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar }

Dec 11 13:07:53 FILESERVER kernel: ata9.00: failed command: READ DMA

Dec 11 13:07:53 FILESERVER kernel: ata9.00: cmd c8/00:c0:ff:9a:06/00:00:00:00:00/e0 tag 14 dma 98304 in

Dec 11 13:07:53 FILESERVER kernel: res 50/00:00:fe:9a:06/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 13:07:53 FILESERVER kernel: ata9.00: status: { DRDY }

Dec 11 13:07:53 FILESERVER kernel: ata9: hard resetting link

Dec 11 13:07:59 FILESERVER kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

Dec 11 13:07:59 FILESERVER kernel: ata9.00: configured for UDMA/133

Dec 11 13:07:59 FILESERVER kernel: ata9: EH complete

Dec 11 13:08:00 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen

Dec 11 13:08:00 FILESERVER kernel: ata9.00: irq_stat 0x80400000, PHY RDY changed

Dec 11 13:08:00 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar }

Dec 11 13:08:00 FILESERVER kernel: ata9.00: failed command: READ DMA EXT

Dec 11 13:08:00 FILESERVER kernel: ata9.00: cmd 25/00:40:3f:c0:07/00:05:00:00:00/e0 tag 0 dma 688128 in

Dec 11 13:08:00 FILESERVER kernel: res 50/00:00:3e:c0:07/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 13:08:00 FILESERVER kernel: ata9.00: status: { DRDY }

Dec 11 13:08:00 FILESERVER kernel: ata9: hard resetting link

Dec 11 13:08:06 FILESERVER kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

Dec 11 13:08:06 FILESERVER kernel: ata9.00: configured for UDMA/133

Dec 11 13:08:06 FILESERVER kernel: ata9: EH complete

Dec 11 13:08:08 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x1390002 action 0xe frozen

Dec 11 13:08:08 FILESERVER kernel: ata9.00: irq_stat 0x88400000, interface fatal error, PHY RDY changed

Dec 11 13:08:08 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar BadCRC TrStaTrns }

Dec 11 13:08:08 FILESERVER kernel: ata9.00: failed command: READ DMA

Dec 11 13:08:08 FILESERVER kernel: ata9.00: cmd c8/00:c0:bf:86:0a/00:00:00:00:00/e0 tag 23 dma 98304 in

Dec 11 13:08:08 FILESERVER kernel: res 50/00:00:be:86:0a/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 13:08:08 FILESERVER kernel: ata9.00: status: { DRDY }

Dec 11 13:08:08 FILESERVER kernel: ata9: hard resetting link

Dec 11 13:08:14 FILESERVER kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

Dec 11 13:08:14 FILESERVER kernel: ata9.00: configured for UDMA/133

Dec 11 13:08:14 FILESERVER kernel: ata9: EH complete

Dec 11 13:08:15 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x1390002 action 0xe frozen

Dec 11 13:08:15 FILESERVER kernel: ata9.00: irq_stat 0x88400000, interface fatal error, PHY RDY changed

Dec 11 13:08:15 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar BadCRC TrStaTrns }

Dec 11 13:08:15 FILESERVER kernel: ata9.00: failed command: READ DMA EXT

Dec 11 13:08:15 FILESERVER kernel: ata9.00: cmd 25/00:40:3f:75:0b/00:05:00:00:00/e0 tag 29 dma 688128 in

Dec 11 13:08:15 FILESERVER kernel: res 50/00:00:3e:75:0b/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 13:08:15 FILESERVER kernel: ata9.00: status: { DRDY }

JorgeB · December 11, 2016

With AHCI (besides performing better) the errors should only appear on the affected disk, unlike legacy IDE where an issue on the master can also affect the slave (and vice-versa).

Those errors look more like a interface issues (cable/controller) but if you already swapped those then it's probably a bad disk.

RAINMAN · December 11, 2016

I'm so confused. I thought the same its a bad disk or cables but its mostly on ata9 but I have sprinkles of other drives too. And I dont even have an ata12

Maybe my sata controller went poof.

Dec 11 14:03:30 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x1390002 action 0xe frozen
Dec 11 14:03:30 FILESERVER kernel: ata9.00: irq_stat 0x88400000, interface fatal error, PHY RDY changed

Dec 11 14:03:30 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar BadCRC TrStaTrns }

Dec 11 14:03:30 FILESERVER kernel: ata9.00: failed command: READ DMA EXT

Dec 11 14:03:30 FILESERVER kernel: ata9.00: cmd 25/00:00:c7:d2:23/00:04:76:00:00/e0 tag 14 dma 524288 in

Dec 11 14:03:30 FILESERVER kernel: res 50/00:00:c6:d2:23/00:00:76:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 14:03:30 FILESERVER kernel: ata9.00: status: { DRDY }

Dec 11 14:03:30 FILESERVER kernel: ata9: hard resetting link

Dec 11 14:03:37 FILESERVER kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 11 14:03:37 FILESERVER kernel: ata9.00: configured for UDMA/33

Dec 11 14:03:37 FILESERVER kernel: ata9: EH complete

Dec 11 14:05:13 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x1390002 action 0xe frozen

Dec 11 14:05:13 FILESERVER kernel: ata9.00: irq_stat 0x88400000, interface fatal error, PHY RDY changed

Dec 11 14:05:13 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar BadCRC TrStaTrns }

Dec 11 14:05:13 FILESERVER kernel: ata9.00: failed command: READ DMA EXT

Dec 11 14:05:13 FILESERVER kernel: ata9.00: cmd 25/00:00:7f:cc:61/00:04:76:00:00/e0 tag 29 dma 524288 in

Dec 11 14:05:13 FILESERVER kernel: res 50/00:00:7e:cc:61/00:00:76:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 14:05:13 FILESERVER kernel: ata9.00: status: { DRDY }

Dec 11 14:05:13 FILESERVER kernel: ata9: hard resetting link

Dec 11 14:05:20 FILESERVER kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 11 14:05:20 FILESERVER kernel: ata9.00: configured for UDMA/33

Dec 11 14:05:20 FILESERVER kernel: ata9: EH complete

Dec 11 14:05:21 FILESERVER kernel: ata9: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen

Dec 11 14:05:21 FILESERVER kernel: ata9: irq_stat 0x80400000, PHY RDY changed

Dec 11 14:05:21 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar }

Dec 11 14:05:21 FILESERVER kernel: ata9: hard resetting link

Dec 11 14:05:28 FILESERVER kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 11 14:05:28 FILESERVER kernel: ata9.00: configured for UDMA/33

Dec 11 14:05:28 FILESERVER kernel: ata9: EH complete

Dec 11 14:06:41 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen

Dec 11 14:06:41 FILESERVER kernel: ata9.00: irq_stat 0x80400000, PHY RDY changed

Dec 11 14:06:41 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar }

Dec 11 14:06:41 FILESERVER kernel: ata9.00: failed command: READ DMA EXT

Dec 11 14:06:41 FILESERVER kernel: ata9.00: cmd 25/00:00:67:2a:9f/00:04:76:00:00/e0 tag 12 dma 524288 in

Dec 11 14:06:41 FILESERVER kernel: res 50/00:00:66:2a:9f/00:00:76:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 14:06:41 FILESERVER kernel: ata9.00: status: { DRDY }

Dec 11 14:06:41 FILESERVER kernel: ata9: hard resetting link

Dec 11 14:06:47 FILESERVER kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 11 14:06:47 FILESERVER kernel: ata9.00: configured for UDMA/33

Dec 11 14:06:47 FILESERVER kernel: ata9: EH complete

Dec 11 14:07:41 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen

Dec 11 14:07:41 FILESERVER kernel: ata9.00: irq_stat 0x80400000, PHY RDY changed

Dec 11 14:07:41 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar }

Dec 11 14:07:41 FILESERVER kernel: ata9.00: failed command: READ DMA EXT

Dec 11 14:07:41 FILESERVER kernel: ata9.00: cmd 25/00:08:47:34:bd/00:01:76:00:00/e0 tag 12 dma 135168 in

Dec 11 14:07:41 FILESERVER kernel: res 50/00:00:46:34:bd/00:00:76:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 14:07:41 FILESERVER kernel: ata9.00: status: { DRDY }

Dec 11 14:07:41 FILESERVER kernel: ata9: hard resetting link

Dec 11 14:07:47 FILESERVER kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 11 14:07:47 FILESERVER kernel: ata9.00: configured for UDMA/33

Dec 11 14:07:47 FILESERVER kernel: ata9: EH complete

Dec 11 14:09:14 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x1390002 action 0xe frozen

Dec 11 14:09:14 FILESERVER kernel: ata9.00: irq_stat 0x88400000, interface fatal error, PHY RDY changed

Dec 11 14:09:14 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar BadCRC TrStaTrns }

Dec 11 14:09:14 FILESERVER kernel: ata9.00: failed command: READ DMA EXT

Dec 11 14:09:14 FILESERVER kernel: ata9.00: cmd 25/00:00:67:dc:fb/00:02:76:00:00/e0 tag 16 dma 262144 in

Dec 11 14:09:14 FILESERVER kernel: res 50/00:00:66:dc:fb/00:00:76:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 14:09:14 FILESERVER kernel: ata9.00: status: { DRDY }

Dec 11 14:09:14 FILESERVER kernel: ata9: hard resetting link

Dec 11 14:09:20 FILESERVER kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 11 14:09:20 FILESERVER kernel: ata9.00: configured for UDMA/33

Dec 11 14:09:20 FILESERVER kernel: ata9: EH complete

Dec 11 14:09:49 FILESERVER kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen

Dec 11 14:09:49 FILESERVER kernel: ata5: irq_stat 0x00400000, PHY RDY changed

Dec 11 14:09:49 FILESERVER kernel: ata5: SError: { RecovComm Persist PHYRdyChg 10B8B }

Dec 11 14:09:49 FILESERVER kernel: ata5: hard resetting link

Dec 11 14:09:55 FILESERVER kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 11 14:09:55 FILESERVER kernel: ata5.00: configured for UDMA/133

Dec 11 14:09:55 FILESERVER kernel: ata5: EH complete

Dec 11 14:15:08 FILESERVER kernel: ata9.00: exception Emask 0x10 SAct 0x0 SErr 0x390002 action 0xe frozen

Dec 11 14:15:08 FILESERVER kernel: ata9.00: irq_stat 0x88400000, interface fatal error, PHY RDY changed

Dec 11 14:15:08 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar BadCRC }

Dec 11 14:15:08 FILESERVER kernel: ata9.00: failed command: READ DMA EXT

Dec 11 14:15:08 FILESERVER kernel: ata9.00: cmd 25/00:00:bf:7e:e7/00:02:77:00:00/e0 tag 23 dma 262144 in

Dec 11 14:15:08 FILESERVER kernel: res 50/00:00:be:7e:e7/00:00:77:00:00/e0 Emask 0x10 (ATA bus error)

Dec 11 14:15:08 FILESERVER kernel: ata9.00: status: { DRDY }

Dec 11 14:15:08 FILESERVER kernel: ata9: hard resetting link

Dec 11 14:15:14 FILESERVER kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 11 14:15:14 FILESERVER kernel: ata9.00: configured for UDMA/33

Dec 11 14:15:14 FILESERVER kernel: ata9: EH complete

Dec 11 14:16:59 FILESERVER kernel: ata9: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen

Dec 11 14:16:59 FILESERVER kernel: ata9: irq_stat 0x80400000, PHY RDY changed

Dec 11 14:16:59 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar }

Dec 11 14:16:59 FILESERVER kernel: ata9: hard resetting link

Dec 11 14:17:06 FILESERVER kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 11 14:17:06 FILESERVER kernel: ata9.00: configured for UDMA/33

Dec 11 14:17:06 FILESERVER kernel: ata9: EH complete

Dec 11 14:20:39 FILESERVER kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 11 14:20:39 FILESERVER kernel: ata12.00: failed command: SMART

Dec 11 14:20:39 FILESERVER kernel: ata12.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 27 pio 512 in

Dec 11 14:20:39 FILESERVER kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

Dec 11 14:20:39 FILESERVER kernel: ata12.00: status: { DRDY }

Dec 11 14:20:39 FILESERVER kernel: ata12: hard resetting link

Dec 11 14:20:39 FILESERVER kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Dec 11 14:20:39 FILESERVER kernel: ata12.00: failed to get NCQ Send/Recv Log Emask 0x1

Dec 11 14:20:39 FILESERVER kernel: ata12.00: failed to get NCQ Send/Recv Log Emask 0x1

Dec 11 14:20:39 FILESERVER kernel: ata12.00: configured for UDMA/133

Dec 11 14:20:39 FILESERVER kernel: ata12: EH complete

Dec 11 14:25:40 FILESERVER kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 11 14:25:40 FILESERVER kernel: ata12.00: failed command: IDENTIFY DEVICE

Dec 11 14:25:40 FILESERVER kernel: ata12.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 17 pio 512 in

Dec 11 14:25:40 FILESERVER kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

Dec 11 14:25:40 FILESERVER kernel: ata12.00: status: { DRDY }

Dec 11 14:25:40 FILESERVER kernel: ata12: hard resetting link

Dec 11 14:25:40 FILESERVER kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Dec 11 14:25:40 FILESERVER kernel: ata12.00: failed to get NCQ Send/Recv Log Emask 0x1

Dec 11 14:25:40 FILESERVER kernel: ata12.00: failed to get NCQ Send/Recv Log Emask 0x1

Dec 11 14:25:40 FILESERVER kernel: ata12.00: configured for UDMA/133

Dec 11 14:25:40 FILESERVER kernel: ata12: EH complete

Dec 11 14:25:45 FILESERVER kernel: ata9: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen

Dec 11 14:25:45 FILESERVER kernel: ata9: irq_stat 0x80400000, PHY RDY changed

Dec 11 14:25:45 FILESERVER kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar }

Dec 11 14:25:45 FILESERVER kernel: ata9: hard resetting link

Dec 11 14:25:52 FILESERVER kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 11 14:25:52 FILESERVER kernel: ata9.00: configured for UDMA/33

Dec 11 14:25:52 FILESERVER kernel: ata9: EH complete

Dec 11 14:30:25 FILESERVER kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 11 14:30:25 FILESERVER kernel: ata10.00: failed command: IDENTIFY DEVICE

Dec 11 14:30:25 FILESERVER kernel: ata10.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 8 pio 512 in

Dec 11 14:30:25 FILESERVER kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

Dec 11 14:30:25 FILESERVER kernel: ata10.00: status: { DRDY }

Dec 11 14:30:25 FILESERVER kernel: ata10: hard resetting link

Dec 11 14:30:25 FILESERVER kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Dec 11 14:30:25 FILESERVER kernel: ata10.00: configured for UDMA/133

Dec 11 14:30:25 FILESERVER kernel: ata10: EH complete

Dec 11 14:30:49 FILESERVER kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 11 14:30:49 FILESERVER kernel: ata12.00: failed command: SMART

Dec 11 14:30:49 FILESERVER kernel: ata12.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 19 pio 512 in

Dec 11 14:30:49 FILESERVER kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Dec 11 14:30:49 FILESERVER kernel: ata12.00: status: { DRDY }

Dec 11 14:30:49 FILESERVER kernel: ata12: hard resetting link

Dec 11 14:30:49 FILESERVER kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Dec 11 14:30:49 FILESERVER kernel: ata12.00: failed to get NCQ Send/Recv Log Emask 0x1

Dec 11 14:30:49 FILESERVER kernel: ata12.00: failed to get NCQ Send/Recv Log Emask 0x1

Dec 11 14:30:49 FILESERVER kernel: ata12.00: configured for UDMA/133

Dec 11 14:30:49 FILESERVER kernel: ata12: EH complete

RAINMAN · December 11, 2016

I pulled everything apart. reset the cmos, all from scratch and put as many drives as possible on my SATA card instead of the motherboard and so far no errors. 14 hours to rebuild. fingers crossed.

RAINMAN · December 17, 2016

Just to close off this topic with the resolution:

I kept getting errors so I replaced the motherboard/CPU with an intel G3258 and a MSI Z97-G55 SLI (overkill on the motherboard right? but for 37$ how could I not) and there are no errors anymore. I am quite certain that the sata controller or something on the motherboard got fried.

adammerkley · December 17, 2016

Oh man, that motherboard looks great. I think I may upgrade my mobo to that one.

RobJ · December 17, 2016

Another possibility for those errors is bad power, or very flaky power connections.

RAINMAN · December 18, 2016

Oh man, that motherboard looks great. I think I may upgrade my mobo to that one.

It was an open box clearance at Frys. Right place at the right time I suppose.

Bad drive alert and now no matter what I try to replace it with I get errors

Recommended Posts

RAINMAN

Link to comment

RAINMAN

Link to comment

JorgeB

Link to comment

RAINMAN

Link to comment

JorgeB

Link to comment

RAINMAN

Link to comment

RAINMAN

Link to comment

RAINMAN

Link to comment

adammerkley

Link to comment

RobJ

Link to comment

RAINMAN

Link to comment

Join the conversation