Re: "DriveReady SeekComplete" errors with new hard drive
My 2c, I've seen this about 5 times since I started doing Linux about 8
years ago. Every time it was just before the HDD was unusable, and one of
the drives was brand new.
--
Arthur H. Johnson II, arthur@usol.com
AIM: bytor4232
YIM: arthurjohnson
IRC: By-Tor@irc.debian.org
On Mon, 23 Jun 2003, Alex Malinovich wrote:
> --=-o0WDZ3r/09wVmFj/W1Pw
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
>
> I just recently added a new hard drive to my firewall machine and I'm
> seeing the following errors:
>
> Jun 17 06:05:59 Bigbrother kernel: hdc: dma_intr: status=3D0x51 {
> DriveReady SeekComplete Error }
> Jun 17 06:05:59 Bigbrother kernel: hdc: dma_intr: error=3D0x40 {
> UncorrectableError }, LBAsect=3D10914399, sector=3D10914224
> Jun 17 06:05:59 Bigbrother kernel: end_request: I/O error, dev 16:01
> (hdc), sector 10914224
>
> Looking through the kernel documentation, I see mention of a similar
> error:
>
> hda: set_multmode: status=3D0x51 { DriveReady SeekComplete Error }
> hda: set_multmode: error=3D0x04 { DriveStatusError }
>
> These seem similar enough, except for the "dma_intr" vs "set_multmode"
> parts differing. And something tells me that those differences might, in
> fact, be rather substantial.
>
> Is anyone familiar with this error? Is it anything to be concerned
> about? Is there any way to fix it? I've heard that getting a "DriveReady
> SeekComplete" error could be a sign of imminent drive failure, but this
> drive is almost brand new. I've never had any problems with it before.
> And, as far as I've been able to tell, it isn't losing any data or
> behaving in any other strange way. Any suggestions?
>
> --=20
> Alex Malinovich
> Support Free Software, delete your Windows partition TODAY!
> Encrypted mail preferred. You can get my public key from any of the
> pgp.net keyservers. Key ID: A6D24837
>
> --=-o0WDZ3r/09wVmFj/W1Pw
> Content-Type: application/pgp-signature; name=signature.asc
> Content-Description: This is a digitally signed message part
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
>
> iD8DBQA+9sd/BPYwh6bSSDcRAvnGAJ0RHPgFtMXNe4FLUFWwGO3kIAqnogCfYqo1
> FgDdIr9nU1pE1edwB+Yxqwk=
> =ZUAT
> -----END PGP SIGNATURE-----
>
> --=-o0WDZ3r/09wVmFj/W1Pw--
>
Reply to: