Does using the raw partition ('badsect /rwd0f/BAD 1919748') help?

                   David/abs             (david@mono.org)

 System Manager, Southern Studios, Box 59, London N22 1AR.  +44 181 888 8949 

 http://www.mono.org    ---<Monochrome>---   (** Largest UK Internet BBS **)  
 http://www.netbsd.org _/Free-un*x alpha,amiga,arm32,atari,hp300,i386,mac68k
 http://www.openbsd.org \mvme68k,mvme88k,pc532,pica,pmax,sparc,sun3,vax,x68k


On Wed, 22 May 1996, Terry Moore wrote:

> Anybody used badsect on NetBSD 1.0?  I just grew a bunch of bad blocks
> on my IDE drive, causing fsck to fail.  I would like to be able to 
> limp through the evening.  Badsect(8) seems like a good way to do 
> this; or at least, a good way to get fsck to tell me more about what 
> is clobbered.  [Yes, I know that the drive is soon to be history, 
> and will deal with longer term problems tomorrow or so.]
> 
> Unfortunately, when I use:
> 
> 	# mount /wd0f	 		-- mounting the device
> 	# badsect /wd0f/BAD 1919748 	-- per the man page
> 
> I get:
> 	/dev/wd0f: device busy
> 
> I checked the sources and could find nothing obviously wrong, and
> (other than the ref to /etc/badsect in the manpage) verified
> that the manpage usage seems to match the apparent intent of the
> code....
> 
> --Terry
> tmm@mcci.com	tel: +1-607-277-1029	fax: +1-607-277-6844
>