--zYM0uCDKw75PZbzx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 03, 2004 at 05:09:49AM -0700, Cameron Kaiser wrote:
> The lost interrupt error is growing to a crescendo as I put more work onto
> this box (1.6.2_RC3, 7300+G3/500, 512MB RAM, Western Digital 40GB drive
> connected to a Tempo Trio ATA/133 [Promise-type controller]).
>=20
> pciide0:0:0: lost interrupt
>         type: ata tc_bcount: 40960 tc_skip: 0
> pciide0:0:0: bus-master DMA error: missing interrupt, status=3D0x21
> wd0a: error reading fsbn 3337248 of 3337248-3337327 (wd0 bn 3337248; cn 3=
310 tn 12 sn 12), retrying
> wd0: (uncorrectable data error)
>=20
> The real problem now is that the error is now uncorrectable, as if the da=
ta
> had been written wrong in the first place. I've tried setting flags to tu=
rn
> off UltraDMA, and this doesn't help.
>=20
> The fsbn is usually consistent in a run. When I back out the database and
> go back to a new backup, a new fsbn suddenly starts going bad, but then r=
eads
> on that fsbn are consistently bad.
>=20
> Suggestions of anything to do short of "replace the hardware" would be ve=
ry
> gratefully appreciated.

Unfortunately if cranking down UltraDMA didn't help, it sounds like your=20
drive is dying. You really shouldn't be getting uncorrectable errors=20
unless the hardware is dying.

Take care,

Bill

--zYM0uCDKw75PZbzx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAoUFiWz+3JHUci9cRAgArAJoCYB6Na52nF0A54sb/Z402YhlBrQCcCsxA
K+X3IMG0Wws8WxGuHhiXe6U=
=iMmA
-----END PGP SIGNATURE-----

--zYM0uCDKw75PZbzx--