sata disk errors

[mgladwin]

Hey all, I'm getting these errors and no matter what I try, I cant seem to get on top of them. This disk was originally on a Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) controller (getting same errors) so I moved it to the onboard SATA controller and seemingly still getting the errors. I have replaced the sata cable a few times with no luck. Its a brand new disk so technically should be good..

 

However I may have to many HDD's in this system for the current power supply and I do have molex connectors piggy backed a few times to get the right amount of power connectors I need but these errors happen when all other disks are spun down. So i figure it could be a power issue but not so much a lack of power, but maybe quality of power coming through the piggy back cables etc??

 

I have done a fair bit of reading on this and typically its power or sata cable issue. I'm leaning towards power as its a new disk and getting same errors on different controllers but thought i would ask here before i make my next move. The power supply is a 500W model and I think has a single 32A 12v rail from memory.

 

I have only ever seen these errors on this same disk. All the other disks connected to either the onboard controller or the LSI controller have never had an issue that i am aware of.

Dec 19 01:43:13 Tower kernel: ata6.00: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
Dec 19 01:43:13 Tower kernel: ata6.00: irq_stat 0x00400040, connection status changed
Dec 19 01:43:13 Tower kernel: ata6: SError: { HostInt PHYRdyChg 10B8B DevExch }
Dec 19 01:43:13 Tower kernel: ata6.00: failed command: READ DMA EXT
Dec 19 01:43:13 Tower kernel: ata6.00: cmd 25/00:00:58:23:03/00:01:f9:00:00/e0 tag 13 dma 131072 in
Dec 19 01:43:13 Tower kernel:         res 50/00:00:57:22:03/00:00:f9:00:00/e0 Emask 0x50 (ATA bus error)
Dec 19 01:43:13 Tower kernel: ata6.00: status: { DRDY }
Dec 19 01:43:13 Tower kernel: ata6: hard resetting link
Dec 19 01:43:19 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 19 01:43:19 Tower kernel: ata6.00: configured for UDMA/133
Dec 19 01:43:19 Tower kernel: ata6: EH complete
Dec 19 02:17:55 Tower kernel: ata6.00: exception Emask 0x52 SAct 0x0 SErr 0x4890c00 action 0xe frozen
Dec 19 02:17:55 Tower kernel: ata6.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Dec 19 02:17:55 Tower kernel: ata6: SError: { Proto HostInt PHYRdyChg 10B8B LinkSeq DevExch }
Dec 19 02:17:55 Tower kernel: ata6.00: failed command: READ DMA EXT
Dec 19 02:17:55 Tower kernel: ata6.00: cmd 25/00:00:b8:62:9a/00:02:6a:01:00/e0 tag 12 dma 262144 in
Dec 19 02:17:55 Tower kernel:         res 50/00:00:47:0a:dd/00:00:7b:00:00/e0 Emask 0x52 (ATA bus error)
Dec 19 02:17:55 Tower kernel: ata6.00: status: { DRDY }
Dec 19 02:17:55 Tower kernel: ata6: hard resetting link
Dec 19 02:18:01 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 19 02:18:01 Tower kernel: ata6.00: configured for UDMA/133
Dec 19 02:18:01 Tower kernel: ata6: EH complete
Dec 19 02:21:03 Tower kernel: ata6.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen
Dec 19 02:21:03 Tower kernel: ata6.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Dec 19 02:21:03 Tower kernel: ata6: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
Dec 19 02:21:03 Tower kernel: ata6.00: failed command: READ DMA EXT
Dec 19 02:21:03 Tower kernel: ata6.00: cmd 25/00:00:b8:5d:10/00:02:6b:01:00/e0 tag 24 dma 262144 in
Dec 19 02:21:03 Tower kernel:         res 50/00:00:cf:ba:00/00:00:e9:00:00/e0 Emask 0x50 (ATA bus error)
Dec 19 02:21:03 Tower kernel: ata6.00: status: { DRDY }
Dec 19 02:21:03 Tower kernel: ata6: hard resetting link
Dec 19 02:21:08 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 19 02:21:08 Tower kernel: ata6.00: configured for UDMA/133
Dec 19 02:21:08 Tower kernel: ata6: EH complete

Diagnostics attached.

 

Look forward to hearing what others thoughts might be.

 

Cheers.

 

tower-diagnostics-20201221-1019.zip

[trurl]

28 minutes ago, mgladwin said:

quality of power coming through the piggy back cables

Seems like a possibility.

[mgladwin]

4 hours ago, trurl said:

Seems like a possibility.

Do you know the best way to fix this? I believe the power supply and single rail is big enough but how do you go about getting the connectors you need?

Its something I have wanted to "fix" for a while but its never really been an issue until now so Ive just left it.

Edited December 21, 2020 by mgladwin