Open GoogleCodeExporter opened 8 years ago
I'm having some trouble erasing a failing usb-drive. I get some I/O errors, and
the device disappears. The errors are not deterministic, so I think a "resume"
feature would work for me. I guess some more problematic situations might need
support for jumping over the broken blocks, to do a best effort erase.
Original comment by toni.ruo...@gmail.com
on 10 Aug 2010 at 9:18
Sorry for the delay responding - I did not have the google code issue tracker
set up to notify me when new issues are opened.
Diskscrub runs on UNIX/linux so unless you have a way to boot Linux on your PC,
such as from one of the livecd distributions, it won't help.
At the moment, diskscrub returns an error if it gets an I/O error back from the
operating system. It's a pretty good idea for a feature to add an option to
ignore these errors (although we can't control the OS's retry/timeout
behavior), or to be able to provide a "skip list" of bad blocks.
I'll put that on the todo list but I may not get to it for a while.
Original comment by garlick....@gmail.com
on 7 Nov 2010 at 4:46
Original comment by garlick....@gmail.com
on 22 Aug 2011 at 4:02
Original comment by garlick....@gmail.com
on 22 Aug 2011 at 4:03
Original issue reported on code.google.com by
nancyli...@yahoo.com
on 21 May 2010 at 3:49