Dear Andrew and others, I'm very glad to say that after running ddrescue for 3 and a half days, and soon in the first retry, it was able to read the 5GiB of errors and no one was left!
Then I mounted the partition of the cloned disk on Linux, and immediately I saw that all of my files were there. Very good! I remember that before starting to clone the disk, it was flagged to run chkdsk. I tried to boot from the cloned device, Windows boot screen showed up, but suddenly the computer restarted. And it kept doing that in a loop. No luck with Safe Mode too. I tried then to boot with "Last Known Good Configuration", and it worked flawlessly. I run chkdsk from Windows, it sad there were some (unimportant, I think) errors, and it flagged chkdsk for the next boot again. Chkdsk runs, says there are no errors, the computer restarts, chkdsk runs again, again, and again until I select the Last Good Config. option. Running chkdsk from Windows installation CD doesn't show any error also. I really can't figure out how to get out from this loop and why running chkdsk from different places show different results. Any ideas or should I resinstall Windows? Thank Andrew for the fast answer and Antonio for developing this very nice tool! Daniel 2010/1/3 andrew zajac <[email protected]> > Hi Daniel. > > It's splitting the errors into smaller pieces. So as the total amount of > unread space decreases, the number of individual spaces with errors > increases. For example, if there is one error spot 100 blocks long and a > block is recovered in the middle of that, then you are left with two errors > spots which will have a smaller total size. > > As for the data recovered being good or not, that depends. If the > filesystem was corrupted before you started the recovery, you will be > recovering a corrupted filesystem. The difference is that you can't repair > a corrupted filesystem on a damaged drive - it will make the problem worse > and increase your data loss. > > Once you have finished imaging, you can try to repair the filesystem on the > image. Make a copy of the image and work on the copy, actually. > > If the filesystem is not repairable, you can use file carving software to > recover individual files. > > Good luck. > > > --- On *Sun, 1/3/10, Daniel Santos <[email protected]>* wrote: > > > From: Daniel Santos <[email protected]> > Subject: [Bug-ddrescue] Errsize decreasing while errors increasing? > To: [email protected] > Received: Sunday, January 3, 2010, 6:43 AM > > > Hi all, > > I'm trying to rescue a 160 GiB Western Digital drive that started taking > longer and longer to boot. Smart tells that it has no bad sectors, but > something around 735 pending sectors. > ddrescue has been running for 3 days now, and so far the results are > approximately 122GiB rescued, 38GiB errsize, and 12350 errors. > But why do errors increase, while errsize is decreasing? > And these 122GiB that are already recovered, are thay really good data, or > could they be also corrupted? > > I'm very confident that ddrescue will be able to do a good job. I'll keep > the list informed of new results. > > Thanks for the attention, > Cheers from Brazil > > -----Inline Attachment Follows----- > > _______________________________________________ > Bug-ddrescue mailing list > [email protected] <http://mc/[email protected]> > http://lists.gnu.org/mailman/listinfo/bug-ddrescue > > > ------------------------------ > The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! > *Get it Now for Free!* <http://downloads.yahoo.com/ca/internetexplorer/> >
_______________________________________________ Bug-ddrescue mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-ddrescue
