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 <address@hidden> wrote:
From: Daniel Santos <address@hidden>
Subject: [Bug-ddrescue] Errsize decreasing while errors increasing?
To: address@hidden
Received: Sunday, January 3, 2010, 6:43 AMHi 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
|