> >Well, the device is busy because its mounted. You should boot up into single
> >user mode(-s when it asks for the kernel name) and then try and run badsect
> >on it. It way work, I can't say I;ve tried it but its worth a go :)
> 	No .. if the filesystem is mounted, you can't access the block
> device period. Only the fix to badsect (which is in post-1.2) which turns
> around and accesses the character (raw) device for the hanky-panky part
> will do it.
Yeah, thats what I meant, I thought it didn't mount anything(except / or course)
so then you could access the block device.

> 	I have thought about it, since I own a total of three old cheap
> drives with bad sectors and have done manual discoveries of bad sectors
> using "dd skip=??" .. 
Hmm, could be very useful =)

Seeya
Darius
~~~~~~