From: Raphael Manfredi <Raphael_Manfredi@pobox.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [2.6.30.5] Diagnosing an IDE lockup with SMART long tests
Date: Fri, 4 Sep 2009 07:35:33 +0200 [thread overview]
Message-ID: <20090904053532.GA26812@chram.org> (raw)
In-Reply-To: <51f3faa70909021724v45d2902ewdb10d5f4a188f2be@mail.gmail.com>
Quoting Robert Hancock:
: Is it always this drive that's failing? I see there's a second of the
: same model, does it show the same behavior?
:
: > ata1.00: ATA-6: HDS722512VLAT80, V33OA60A, max UDMA/100
: > ata1.00: 241254720 sectors, multi 16: LBA48
:
: If only that particular drive shows this problem, then I would start
: to suspect a hardware fault with that drive. The fact that it fails
: with both IDE and libata (and with ata_piix, which is a really
: commonly used and tested libata driver) rather points in that
: direction.
That was a very good diagnosis.
I switched my two Hitachi drives for Maxtors, and the problem
went away. I was able to do a SMART long test on all my drives
without lockups and without any kernel complaints on the console.
Thanks a lot, I had no idea these Hitachi drives had a bad firmware.
Looking at the tags on the drives, they were manufactured late 2003
and early 2004.
Raphael
prev parent reply other threads:[~2009-09-04 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6661.1251822466@nice.ram.loc>
[not found] ` <4A9DF3E9.9090309@gmail.com>
[not found] ` <20090902111927.GA4590@chram.org>
2009-09-02 14:42 ` [2.6.30.5] Diagnosing an IDE lockup with SMART long tests Robert Hancock
2009-09-02 14:52 ` Raphael Manfredi
2009-09-03 0:24 ` Robert Hancock
2009-09-04 5:35 ` Raphael Manfredi [this message]
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=20090904053532.GA26812@chram.org \
--to=raphael_manfredi@pobox.com \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).