I am only going to answer part of your questions, ask one, and add
something.
- will ddrescue automatically stop when it
reaches the end of the used portion of the partition (315720 MB in
my case) or must I end it with CTRL+C?
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.
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.
And now to add something. You had previously asked:
"Any way I can check if the MFT was
recovered successfully now?"
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.
Scott
On 11/15/2013 2:18 PM, Andrej Trobentar
wrote:
On 11/13/2013 12:18 AM, Scott D wrote:
Andrej,
I see you show 9.20% rescued at this time. I am curious, do
you remember what the percentage was from ddru_ntfsbitmap? If
you don't remember for sure, you could run ddrescuelog on the
domain file to find out:
"ddrescuelog -t domain_logfile"
"Rescued" will = used space that you are trying to recover,
and "non-tried" will = free space that you are ignoring
Here's my status so far :
current pos: 270988 MB, current status: copying
domain size: 500104 MB, in 1 area(s)
rescued: 106890 MB, in 2718 area(s) ( 21.37%)
non-tried: 350152 MB, in 3470 area(s) ( 70.01%)
errsize: 43061 MB, errors: 2438 ( 8.61%)
non-trimmed: 43057 MB, in 4026 area(s) ( 8.60%)
non-split: 0 B, in 0 area(s) ( 0%)
bad-sector: 4617 kB, in 5340 area(s) ( 0.00%)
I have now come to an area (around 270GB) where my disk starts to
fail and fail and even power cycling doesn't help, so I tried this
command to hopefully skip the troubled area :
"ddrescue -m /tmp/domain_logfile -vvvv -i 275GB -n /dev/sdb1
/tmp/Image.img /tmp/Image.log"
and now my disc slowly continues again. When the drive fails again
I'll continue with the command :
"ddrescue -m /tmp/domain_logfile -vvvv -n /dev/sdb1 /tmp/Image.img
/tmp/Image.log"
If my drive comes again to a troubled area (and even power cycling
doesn't help) I'll just adjust the -i parameter as before.
Now to my question :
- will ddrescue automatically stop when it reaches the end of the
used portion of the partition (315720 MB in my case) or must I end
it with CTRL+C?
- what's the next step after that?
Greetings from Slovenia,
Andrej.
_______________________________________________
Bug-ddrescue mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
|