--GOzekVbrLdOLv44p
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Wed, Oct 20, 2004 at 01:07:54PM +0200, Alan Barrett wrote:
> piixide0:0: lost interrupt
> type: ata tc_bcount: 0 tc_skip: 0
> piixide0:0: lost interrupt
> type: ata tc_bcount: 16384 tc_skip: 0
> piixide0:0:0: intr with DRQ (st=0x58)
> wd0e: device timeout writing fsbn 745600 of 745600-745631 (wd0 bn 35682930; cn 17423 tn 19 sn 18), retrying
> wd0: soft error (corrected)
Can't explain why it might happen exactly once per boot, but could it
simply be the drive trying to remap sectors? Does turning off
write-cache prevent it, or at least cause it to stop on the second and
subseqent times through (ie, once it's remapped successfuly)?
If so, you probably want to overwrite the whole disk this way, or at
least run with write cache off through as much write activity as you
can create. Making sure the whole disk is presently readable (with
dd) or at least all the data is (with dump) would also be a great
idea.
You'll need to change the write-cache setting from single-user mode
before letting cgdconfig/etc run, obviously. On most machines, this
setting also seems to survive a soft reboot.
Hm. Perhaps the sector in question is only written to during fsck, and
perhaps not ever read again? A superblock backup or something?
--
Dan.
--GOzekVbrLdOLv44p
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)
iD8DBQFBdtDDEAVxvV4N66cRAsyXAKCJ1BiI+cueVs+KZ9Qu1qDBw66woACfQXy9
iwbvvqmNweL28lXxeB1OrE0=
=fcE6
-----END PGP SIGNATURE-----
--GOzekVbrLdOLv44p--