Please post reports of success or failure using ddrutility here
LINUX based utility for use with gnuddrescue to aid with data recovery
Brought to you by:
maximus57
Menu
▾
▴
Please post any success or failure stories from using ddrutility here. For instance I am interested to see what systems it works and does not work on. It should work on Ubuntu as I use XUbuntu for my tests. I do not run any other Linux systems normally, so I don't know what it will and will not work on unless it is reported to me.
Last edit: maximus57 2014-01-01
I used ddrutility to tell me which files were corrupt after recovering from a failed drive. Thank you!
Hi, I am running on Scientig Linux 6.5 32 bit. I am having this problem when running ddru_ntfsbitmap:
............ Done reading part 0 of $Bitmap...........
Creating ddrescue domain logfile...
end = 239221112320
total_size = 250059350016
Finished creating logfile
total= 239221080064 bytes
used= 87251734528 (36.47%)
free= 151969345536 (63.53%)
ddrescuelog: error in logfile domain_logfile, line 7
ddru_ntfsbitmap took 2.367696 seconds to complete
Line 7 appears to be a duplicate of line 6.
I have found this bug and it will be fixed in the next release. Thanks for pointing it out.
Scott
Version 2.4 has been released and should fix this issue.
Scott
As a fast workaround to make domain I propose to use partclone.ntfs with -D parameter, I tried that and it worked for me.
First I would like to apologize for this short and late reply, but recent events make it lucky that I am even online to reply. And any bug fix will probably not happen soon.
I will try to reproduce that error with the information you provided. If possible it may help me to have the bitmap file, or actually only about the first 1k of it as the error happens at the very beginning. And possibly the debug file from ddru_ntfsbitmap from running with the -D option.
@olegkrutov
I did not know that partclone had that option! It almost makes my ntfsbitmap not needed.
maximus57, partclone.ntfs does not make ddru_ntfsbitmap not needed as it is almost completely not error-proof so it is not possible to create map of partition with bad blocks on $Bitmap :)
Hello again, it's Andy from the bug-ddrescue mailing list here again. :) I've run
sudo ddrescue -f -r-1 /dev/sda /dev/sde ddrlog.backup.txt -m mftdomain_logfile
and recovered (another?) 20kB, 115kB remaining of the MFT. This has taken hours. In the wiki and in the sourcecode (I'm no programmer, I don't know why I looked) I see reference to $MftMirr(or). Is there a way that I can target that instead? Or have I misunderstood again?
Thanks! Andy.
Is there a way to use ntfsfindbad.log inode / filename info with ntfsfindbad_debug.log inode / offset info to produce domain files for specific file extensions, like my sisters .xls files and my .mp3, .flac, .m4a files?
Sorry, there is currently no way to do this, and I do not plan on implementing it. If I were to do anything similar, it would be the ability to recover individual files.
Andy,
Unfortunately the $MFTMirr only contains the first 4 entries of the $MFT (4kB). So it only contains the most critical information to attempt the most basic partition recovery / filesystem repair. The first two entries are for $MFT and $MFTMirr themselves.
The entry for $MFT is a road map to where the MFT actually exists on the disk. The first record of $MFT is actually the record for itself. If that part of $MFT is not readable, I use the MFTMirr to get the entry for $MFT so it can find where it is on the disk. Hope that makes some sense.
Scott
I would like to add that I am considering turning off the ability to post anonymously. It is causing posts to be out of order since I have to approve them before they show up. I hope that doesn't bother anybody.