Re: libata/sata errors on ich[?]/maxtor

From: Samuel Masham
Date: Wed Mar 22 2006 - 04:56:40 EST

Hi Again All, Alan,

On 17/03/06, Samuel Masham <samuel.masham@xxxxxxxxx> wrote:
> Hi Alan,
> On 17/03/06, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
> > On Gwe, 2006-03-17 at 13:37 +0900, Samuel Masham wrote:
> > > As you can see from the printk's here this error continues and the for
> > > every access (write?) to the drive you just have to wait for a
> > > timeout.
> >
> > Eventually the drive will be offlined.
> really? I can test that easily enough if nothing else :)

When is it (should it) going to offline the drive? its been spitting
out these messages (about set per min?) for 4 hours at the moment with
no change bar the sector number increasing by 2 each time...

> > > ata1: command 0x35 timeout, stat 0xd1 host_stat 0x61
> > > ata1: translated ATA stat/err 0xd1/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> > > ata1: status=0xd1 { Busy }
> > > SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8000002
> > > Current sd08:12: sense key Aborted Command
> > > Additional sense indicates Scsi parity error
> >
> > It thinks there is a communication (eg cable problem), at least that is
> > how it has mapped the error report. Not something I'd expect to see in
> > the SATA case on several machines so it could be some kind of setup
> > error or timing incompatibility in the driver.
> Well Its cheep enough to get another cable and test that.

Done. The new short cable showed no difference in behavior.

So left with the timing/setup error... Anyone with any ideas?

> > What is attached to that controller (SATA and PATA items)

as I said before there are two hardisks

> Ata Maxtor 6Y080M0 SCSI sda 0
> Ata Maxtor 6V250F0 SCSI sdb 0

(Remember the problem is ONLY with the second drive... and according
to others any in the 6Vxxx series shows this same issue?)

...and there is a cdrom drive attached via pata

(I think its on the same controller... the 6300ESB seems to do just
about everything...)

hdparm -I /dev/hda


ATAPI CD-ROM, with removable media
Model Number: SAMSUNG CD-ROM SN-124
Serial Number:
Firmware Revision: N103
Likely used CD-ROM ATAPI-1
DRQ response: 50us.
Packet size: 12 bytes
LBA, IORDY(can be disabled)
DMA: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns

As Ian mentioned maxtor have release a new version of the drive
firmware ... but... The 6V250F0 drive that shows this lockup IS
running the latest drive firmware which I discovered after a rather
long exchange with Maxtor...

I have had a bit of a look at the sata spec and would just like to
confirm that the drive is configured to disable the NCQ (as the Maxtor
support seemed to stress this point). From what i can see this is done
in the Device Configuration Overlay...

>From the spec

4.8. Device Configuration Overlay
4.8.1. Definition

WORD 8: Serial ATA command / feature sets supported
This word enables configuration of command sets and feature sets.
Bit 0 indicates whether native command queuing shall be
supported by the device. When
set to one, the drive shall support native command queuing.
When cleared to zero, drive
support for native command queuing shall be disabled ....

So anyone got any ideas how to read this?

Or anything else to check / try...

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at