Mailing List Archive: SATA eating my disk, port reset, destroying unrelated data

SATA eating my disk, port reset, destroying unrelated data

Nov 4, 2007, 12:58 PM

Post #1 of 3 (390 views)

Dear all!

(please Cc me for answers)

Since about 5 days I am having serious problems with my SATA drive:

kernel 2.6.22 (from Debian/sid)
hardware nv

Sometimes at boot time, often/always at disk io intense stuff:

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x2
ata1.00: (BMDMA stat 0x25)
ata1.00: cmd 35/00:00:2a:6f:c0/00:04:0c:00:00/e0 tag 0 cdb 0x0 data 524288 out
res 51/84:10:1a:72:c0/84:01:0c:00:00/e0 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete

Even worse, sometimes the reset does not work ...

ata1: device not ready (errno=-16), forcing hardreset
ata1: hard resetting port
ata1 SRST failed (errno=-19)
ata1: reset failed (errno=-19), retrying in 10 secs
...

(typed from a digital photo, nothing remains in the logs)

After this I need to do a cold boot otherwise the drive is really in a
bad state and not even the bios gets it right.

Interestingly the whole stuff DID work for a long time until I did too
many things at the same time: 2 x svn up, copying 40G from the SATA
drive to an USB drive, aptitude upgrade. Before I did regularly the same
stuff (like svn up etc), but this time it was too much, it seems.

Apropos data hosing: After the first incident some data on my windows
partitions (/dev/sda1) was hosed, programs missing, chkdisk necessary
etc.

I attach dmesg (from the current boot with a succeeding soft reset, I
interrupted the svn process before the SATA drives goes into hard reset
failures), .config, lspci -v output.

Are there any chances that using 2.6.23 will improve/fix this? Any other
suggestions?

I would consider it an hardware problem, but since it started at one big
io thingy and is persistent since then I am a bit sceptic.

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at> Vienna University of Technology
Debian Developer <preining@debian.org> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
ARTHUR It's not a question of whose habitat it is, it's a question of
how hard you hit it.
--- Arthur pointing out one of the disadvantages of gravity,
--- Fit the Tenth.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy

Re: SATA eating my disk, port reset, destroying unrelated data [ In reply to ]

hancockr at shaw

Nov 7, 2007, 4:22 PM

Post #2 of 3 (347 views)

Permalink

Norbert Preining wrote:
> Dear all!
>
> (please Cc me for answers)
>
> Since about 5 days I am having serious problems with my SATA drive:
>
> kernel 2.6.22 (from Debian/sid)
> hardware nv
>
> Sometimes at boot time, often/always at disk io intense stuff:
>
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x2

Serror 0x400000 means a handshake error. Usually Serror indications are
due to a hardware problem (bad SATA cable, power or drive problem).

> ata1.00: (BMDMA stat 0x25)
> ata1.00: cmd 35/00:00:2a:6f:c0/00:04:0c:00:00/e0 tag 0 cdb 0x0 data 524288 out
> res 51/84:10:1a:72:c0/84:01:0c:00:00/e0 Emask 0x10 (ATA bus error)
> ata1: soft resetting port
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete
>
> Even worse, sometimes the reset does not work ...
>
> ata1: device not ready (errno=-16), forcing hardreset
> ata1: hard resetting port
> ata1 SRST failed (errno=-19)
> ata1: reset failed (errno=-19), retrying in 10 secs
> ..
>
> (typed from a digital photo, nothing remains in the logs)
>
> After this I need to do a cold boot otherwise the drive is really in a
> bad state and not even the bios gets it right.

If even the BIOS cannot reset properly then that also really points to a
hardware problem..

>
> Interestingly the whole stuff DID work for a long time until I did too
> many things at the same time: 2 x svn up, copying 40G from the SATA
> drive to an USB drive, aptitude upgrade. Before I did regularly the same
> stuff (like svn up etc), but this time it was too much, it seems.
>
> Apropos data hosing: After the first incident some data on my windows
> partitions (/dev/sda1) was hosed, programs missing, chkdisk necessary
> etc.
>
> I attach dmesg (from the current boot with a succeeding soft reset, I
> interrupted the svn process before the SATA drives goes into hard reset
> failures), .config, lspci -v output.
>
> Are there any chances that using 2.6.23 will improve/fix this? Any other
> suggestions?
>
> I would consider it an hardware problem, but since it started at one big
> io thingy and is persistent since then I am a bit sceptic.

--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Re: SATA eating my disk, port reset, destroying unrelated data [ In reply to ]

htejun at gmail

Nov 11, 2007, 7:57 PM

Post #3 of 3 (338 views)

Permalink

Robert Hancock wrote:
> Norbert Preining wrote:
>> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x2
>
> Serror 0x400000 means a handshake error. Usually Serror indications are
> due to a hardware problem (bad SATA cable, power or drive problem).
>
>> ata1.00: (BMDMA stat 0x25)
>> ata1.00: cmd 35/00:00:2a:6f:c0/00:04:0c:00:00/e0 tag 0 cdb 0x0 data
>> 524288 out
>> res 51/84:10:1a:72:c0/84:01:0c:00:00/e0 Emask 0x10 (ATA bus
>> error)

And error register value 0x84 - ICRC (CRC error on ATA bus) and ABRT
(command abort) - agrees with what SError indicates. You're
experiencing transmission errors.

>> ata1: soft resetting port
>> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata1.00: configured for UDMA/133
>> ata1: EH complete
>>
>> Even worse, sometimes the reset does not work ...
>>
>> ata1: device not ready (errno=-16), forcing hardreset
>> ata1: hard resetting port
>> ata1 SRST failed (errno=-19)
>> ata1: reset failed (errno=-19), retrying in 10 secs
>> ..
>>
>> (typed from a digital photo, nothing remains in the logs)
>>
>> After this I need to do a cold boot otherwise the drive is really in a
>> bad state and not even the bios gets it right.
>
> If even the BIOS cannot reset properly then that also really points to a
> hardware problem..

Also, firmware on some harddrives die solidly when transmission errors
occur. Maybe yours is one. There's nothing much the driver can do
about both the transmission error and the drive locking up afterward.
If the transmission errors occur frequently, the chance is that either
your drive or power supply is dying. As for the drive lock up, maybe
firmware update will help.

* "smartctl -a /dev/sda" might report something interesting.

* Connect the drive to different SATA and power connector and see if the
problem persists.

* Connect the drive to a separate power supply and see if the problem
persists.

--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Mailing List Archive

Mailing List Archive

Attached Files: