Page MenuHomePhabricator

SATA errors for stat1004 in the dmesg
Closed, ResolvedPublic

Description

After the reimage of stat1004 we noticed the following error in the dmesg:

[Tue Apr 11 14:54:51 2017] ata1.00: status: { DRDY }
[Tue Apr 11 14:54:51 2017] ata1.00: failed command: READ FPDMA QUEUED
[Tue Apr 11 14:54:51 2017] ata1.00: cmd 60/80:e8:80:d0:b3/00:00:00:00:00/40 tag 29 ncq dma 65536 in
         res 40/00:58:00:e0:b3/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[Tue Apr 11 14:54:51 2017] ata1.00: status: { DRDY }
[Tue Apr 11 14:54:51 2017] ata1.00: failed command: READ FPDMA QUEUED
[Tue Apr 11 14:54:51 2017] ata1.00: cmd 60/00:f0:00:d1:b3/04:00:00:00:00/40 tag 30 ncq dma 524288 in
         res 40/00:58:00:e0:b3/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[Tue Apr 11 14:54:51 2017] ata1.00: status: { DRDY }
[Tue Apr 11 14:54:51 2017] ata1: hard resetting link
[Tue Apr 11 14:54:51 2017] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Tue Apr 11 14:54:51 2017] ata1.00: NCQ Send/Recv Log not supported
[Tue Apr 11 14:54:51 2017] ata1.00: NCQ Send/Recv Log not supported
[Tue Apr 11 14:54:51 2017] ata1.00: configured for UDMA/133
[Tue Apr 11 14:54:51 2017] ata1: EH complete
[Tue Apr 11 14:54:51 2017] ata1: limiting SATA link speed to 3.0 Gbps

I have never seen the above error but it could be related to a faulty SATA? Chris, did you encounter it before by any chance?

Reading from the internet it seems that various people either replaced the SATA cable or checked the PSU's voltage.

Event Timeline

@elukey That is not a disk issue....What mode do you want the server to be in? Raid mode or AHCI?

@Cmjohnson sorry for the late response, didn't notice your answer!

So we have two sw raid10 already running, so I'd say AHCI (so not hw raid) but please let me know if I am completely off track or not :)

@elukey we will need to coordinate a time to try and replace the sata cable and/or check settings.

The issue seemed transient, didn't see any trace of it anymore in dmesg. Will re-open if necessary :)