Re: [Bug-ddrescue] Help rescuing my 500GB disk

[Andrej Trobentar]

On 11/15/2013 11:16 PM, Scott Dwyer wrote:

Ddrescue will exit when it is done doing what you told it to do, considering all the options you provided it. The only thing the domain file does is cause ddresuce to only make attempts at the areas specified in the domain file (in this case the used portion of the partition). So when it is done trying the area specified in the domain file (again, considering all the other options provided to ddrescue), it will exit on its own. So to clarify, when using a domain file and ddrescue exits normally, ddrescue is done with its attempt at recovering that area with the options you provided. If you stop providing the domain file, then ddrescue will continue its attempts on the entire disk (partition in your case). You can actually go back to using a domain file at any time and ddresuce will again only make attempts the area specified. I will let someone else discuss the options you are using, and what would be next.

Thanks for the great explanation ;)

Now for my question: I am curious, were any/many errors reported when you ran ddru_ntfsbitmap? If you did not delete it, then "ntfsbitmap_rescue_report.log" would have this information. Not that it matters that much, as any errors or unread parts of the extracted bitmap file will be filled with FF to ensure there will not be any missed areas.

Here's the ntfsbitmap_rescue_report.log - I guess everything is OK :

__bootsec.log
__bootsec

current pos:         0 B,  current status: finished
domain size:       512 B,  in    1 area(s)
    rescued:       512 B,  in    1 area(s)  (100%)
  non-tried:         0 B,  in    0 area(s)  (  0%)

    errsize:         0 B,  errors:       0  (  0%)
non-trimmed:         0 B,  in    0 area(s)  (  0%)
  non-split:         0 B,  in    0 area(s)  (  0%)
 bad-sector:         0 B,  in    0 area(s)  (  0%)
..............................................................................
__mftbitmap.log
__mftbitmap

current pos:     3221 MB,  current status: finished
domain size:      1024 B,  in    1 area(s)
    rescued:      1024 B,  in    1 area(s)  (100%)
  non-tried:         0 B,  in    0 area(s)  (  0%)

    errsize:         0 B,  errors:       0  (  0%)
non-trimmed:         0 B,  in    0 area(s)  (  0%)
  non-split:         0 B,  in    0 area(s)  (  0%)
 bad-sector:         0 B,  in    0 area(s)  (  0%)
..............................................................................
_part0__bitmapfile.log
__bitmapfile

current pos:     3221 MB,  current status: finished
domain size:    15265 kB,  in    1 area(s)
    rescued:    15265 kB,  in    1 area(s)  (100%)
  non-tried:         0 B,  in    0 area(s)  (  0%)

    errsize:         0 B,  errors:       0  (  0%)
non-trimmed:         0 B,  in    0 area(s)  (  0%)
  non-split:         0 B,  in    0 area(s)  (  0%)
 bad-sector:         0 B,  in    0 area(s)  (  0%)

Keep an eye out for the next release of ddrutility, which hopefully will be sometime this weekend. I am adding an option to ddru_ntfsbitmap that will allow creation of a second domain file that will be just for the MFT. This would allow someone to attempt recovery of the MFT first, and also see the errors of just the MFT, which could help with some decisions about how to proceed with the recovery.

Will do, that will be a great feature \o/

Greetings,

        Andrej.