IDE drives normally handle mapping bad blocks internally - the
	fact you've seen a bad block probably indicates that its run out
	of space to map out blocks - that disk could really be a dyin'...

	What you've done is pretty much how 'badsect' would handle the
	bad block. The other option is bad144, but I don't know if it
	will work in your case...

- Thought for the day... "I miss my dog"

On 12 Jul 1997, Matthias Scheler wrote:

> 	Hi,
> 
> one of my NetBSD 1.2 systems has a bad block on one of its hard disks:
> 
> Jul 12 15:38:51 jehova /netbsd: wd0e: hard error reading fsbn 227651 of 227648-227679 (wd0 bn 338915; cn 557 tn 6 sn 31)
> 
> Because I don't have time to replace that harddisk in the next few weeks
> I would like to know if there's a way to tell the filesystem not to touch
> that block again. For now I renamed the file with the bad block in it
> to keep the space occupied and redownloaded it.
> 
> -- 
> Matthias Scheler                                http://home.owl.de/~tron/
>