From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Is my SATA/400GB drive dying?
Date: Mon, 13 Feb 2006 22:16:08 +0900 [thread overview]
Message-ID: <dsq0qp$egf$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0602130659420.21772@p34>
Please try to not break the threading, just reply to your post.
Justin Piszcz wrote:
> There are different errors at the end of the lines:
>
> 0xb/00/00 and 0x3/11/04
>
> Anyone know what these mean?
>
> [31230.223511] ata6: status=0x51 { DriveReady SeekComplete Error }
> [31230.223515] ata6: error=0x04 { DriveStatusError }
> [37209.844015] ata6: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ
> 0xb/00/00
> [37209.844022] ata6: status=0x51 { DriveReady SeekComplete Error }
> [37209.844026] ata6: error=0x04 { DriveStatusError }
> [37861.648959] ata6: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ
> 0xb/00/00
> [37861.648965] ata6: status=0x51 { DriveReady SeekComplete Error }
> [37861.648970] ata6: error=0x04 { DriveStatusError }
> [37978.030178] ata6: no sense translation for status: 0x51
> [37978.030185] ata6: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ
> 0x3/11/04
> [37978.030188] ata6: status=0x51 { DriveReady SeekComplete Error }
>
>
> On Mon, 13 Feb 2006, Justin Piszcz wrote:
>
>> I turned off smartd and when I cat /dev/zero > /mnt/disk/file, I get
>> the following errors:
>>
>> [37978.030178] ata6: no sense translation for status: 0x51
>> [37978.030185] ata6: translated ATA stat/err 0x51/00 to SCSI
>> SK/ASC/ASCQ 0x3/11/04
>> [37978.030188] ata6: status=0x51 { DriveReady SeekComplete Error }
I know you are feeling uneasy at best, but I have more or less the same
problems with two Raptors (WD740GD) on two Asus P5GCD-V Deluxe (ICH6) MBs. I
had to pull them out of the box to use the boxes, because they were
constantly freezing...
Report is here:
http://linux.tar.bz/reports/oopses/char/2.6.15.1-K01_P4_server.3.dmesg
(and the dirs above)
So far I got one or two "me too" responses, but that was all. I think the
last working kernel was 2.6.11, but that is a bit too old to test now and
then I was not using libata, AFAIR.
Now one of the boxes uses Seagate ST3250823AS (25d uptime) and the other an
old PATA WDC WD102BB (yes that is only 10GB!).
How reproducible is yours?
We might file to bugzilla? (So far I always had the attention on LKML quick
enough)
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
next prev parent reply other threads:[~2006-02-13 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 11:58 Is my SATA/400GB drive dying? Justin Piszcz
2006-02-13 12:00 ` Justin Piszcz
2006-02-13 13:16 ` Kalin KOZHUHAROV [this message]
2006-02-13 15:16 ` David Greaves
2006-02-14 1:17 ` Justin Piszcz
2006-02-14 1:18 ` Justin Piszcz
2006-02-14 10:43 ` Erik Mouw
2006-02-14 19:30 ` Alistair John Strachan
2006-02-14 21:50 ` David Greaves
2006-02-14 23:53 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dsq0qp$egf$1@sea.gmane.org' \
--to=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox