If your going to continue to use the disk at least turn on S.M.A.R.T. in the BIOS (if it's not on already) and load one of the S.M.A.R.T.-aware tools in the ports directories (like smartmontools) to keep an eye on it. I still think though that it's just a matter of time before you have more problems. Disks are so cheap I can't understand why anyone would want to try nursing one along that's going bad these days.
Ted ----- Original Message ----- From: "Marc G. Fournier" <[EMAIL PROTECTED]> To: "John Nielsen" <[EMAIL PROTECTED]>; <freebsd-questions@freebsd.org> Cc: "Marc G. Fournier" <[EMAIL PROTECTED]>; "Dan Nelson" <[EMAIL PROTECTED]> Sent: Saturday, February 10, 2007 3:17 PM Subject: Re: Bad sector on drive ... > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Didn't work, ended up newfs'ng the file system, since the data on the drive is > recreatable, and seems to have worked fine ... > > the error I was getting was when fsck'ng, so suspect that a file got written > over top of the bad sector and was causng the problem ... > > - --On Saturday, February 10, 2007 11:05:35 -0500 John Nielsen > <[EMAIL PROTECTED]> wrote: > > > On Saturday 10 February 2007 09:47, Marc G. Fournier wrote: > >> --On Saturday, February 10, 2007 01:00:21 -0600 Dan Nelson > >> > >> <[EMAIL PROTECTED]> wrote: > >> > In the last episode (Feb 10), Marc G. Fournier said: > >> >> Short of a reformat, any way of marking the following as bad? :( > >> >> > >> >> Feb 10 02:27:20 ganymede kernel: ad4: FAILURE - READ_DMA > >> >> status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=176887263 Feb > >> >> 10 02:27:25 ganymede kernel: ad4: TIMEOUT - READ_DMA retrying (1 retry > >> >> left) LBA=176887324 Feb 10 02:27:30 ganymede kernel: ad4: TIMEOUT - > >> >> READ_DMA retrying (0 retries left) LBA=176887324 Feb 10 02:27:35 > >> >> ganymede kernel: ad4: FAILURE - READ_DMA timed out LBA=176887324 > >> > > >> > Try writing to the block causing the error, using dd and the seek= > >> > option; if the write succeeds, you're done (and the drive will have > >> > either reused the block or reassigned it to a spare). 176887324 If it > >> > doesn't succeed, copy what you can off the drive and toss it, since all > >> > its spares are used up. > >> > > >> > I think LBA numbers map directly to seek= values assuming you keep > >> > bs=512 and access /dev/ad4 . I'd try reading the bad block with dd to > >> > verify it's the right one before doing a write, though. > >> > >> 'k, how do you use dd to write to a specific sector? > >> > >> dd of=/dev/ad4 seek=176887324 bs=512 if=/dev/null > > > > dd of=/dev/ad4 seek=176887324 bs=512 count=1 if=/dev/zero > > > > JN > > > > > > - ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (FreeBSD) > > iD8DBQFFzlJ14QvfyHIvDvMRAicNAJ9Fvx3B7p8ibsne3lV+HSd6rnkLEwCgmKBz > IsS5cm2DUlwcC3fKbnyiT9c= > =G+Wn > -----END PGP SIGNATURE----- > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"