From: "Axel H. Siebenwirth" <axel@hh59.org>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.3 - (IDE) hda: drive not ready for command errors
Date: Fri, 1 Feb 2002 17:48:13 +0100 [thread overview]
Message-ID: <20020201164813.GA14296@neon> (raw)
In-Reply-To: <20020201153303.A1508@prester.hh59.org> <5.1.0.14.2.20020201160018.026603b0@pop.cus.cam.ac.uk>
In-Reply-To: <5.1.0.14.2.20020201160018.026603b0@pop.cus.cam.ac.uk>
Hi Anton!
On Fri, 01 Feb 2002, Anton Altaparmakov wrote:
> I was about to send the drive (IBM 7200rpm 41GiB) back for replacement when
> I as last resort tried to upgrade the firmware of the drive.
>
> After the upgrade the drive started working again, fully passed the Drive
> Fitness Test (IBM utility) and it has been working for a few weeks non-stop
> in my file server RAID-1 array since then.
The thing is that they come up now, just since I installed 2.5.3. Might
there be a hope that it is a kernel-related issue (new IDE driver...). Drive
has been working fine ever since till now.
Best regards,
Axel Siebenwirth
P.S.: Would like to write to my WinXP NTFS Partition, is there some hope MS
will ever give out exact specs (they don't, do they?) to have write
funtionality properly implemented? Is there some other way to contribute?
next prev parent reply other threads:[~2002-02-01 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 14:33 2.5.3 - (IDE) hda: drive not ready for command errors axel
2002-02-01 16:06 ` Anton Altaparmakov
2002-02-01 16:48 ` Axel H. Siebenwirth [this message]
2002-02-01 17:52 ` Andreas Dilger
2002-02-02 2:44 ` Anton Altaparmakov
2002-02-02 9:26 ` Jens Axboe
2002-02-02 19:10 ` Axel H. Siebenwirth
2002-02-02 21:48 ` Andre Hedrick
2002-02-02 23:28 ` Jens Axboe
2002-02-02 23:58 ` Jens Axboe
2002-02-05 15:32 ` Holger Lubitz
2002-02-05 16:09 ` Anton Altaparmakov
2002-02-05 16:57 ` Holger Lubitz
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=20020201164813.GA14296@neon \
--to=axel@hh59.org \
--cc=aia21@cam.ac.uk \
--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