With so few errors you could look into using ntfscluster to find what if any files are in those sectors. Here is a link for how to do that. FYI your cluster size is 4096. Ntfscluster also has a sector option which would then use 512 for a dividing number. https://radagast.ca/linux/how-to-find-the-ntfs-filename-associated-with-a-bad-block-using-linux.html https://www.unix.com/man-page/linux/8/ntfscluster/
How did you install ddrutility on Rasbian in the first place? If you followed the standard instructions, you already ran make during the installation process. You need to do that again but with a modified makefile edited as described. I do not know of any way to do anything with just the MFT and mapfile, even though that is all that is required. Your only options are try to to recompile ddrutility with the modified makefile, or use something other than a Raspberry Pi that does not have an ARM processor....
I think I can see what is happening, but it shouldn't happen. A signed character with a value of 0xF6 is being considered positive when it should be considered a negative value by the system. It would seem your system is defaulting to an unsigned character. What OS are you using, and what is your computer architecture? I am curious about the system and why it is like this. Can you run the following command and provide me the dmesg.txt file? dmesg > dmesg.txt In the source file "makefile" you can...
Please provide the output from the following commands: sudo fdisk -lu /dev/sda sudo lsblk -f /dev/sda sudo xxd -s 659554304 -l 512 /dev/sda fdisk is to verify it is still the same disk from your post lsblk should show the partition types and verify the targeted one is ntfs xxd will provide a hex dump of the partition boot sector to verify that it is a valid ntfs boot sector The error indicates it is not a valid ntfs boot sector.
I am glad you found that you could use the older version. I no longer support ddrutility, so any issues will not be fixed. But since it is open source, maybe a fix could be found by yourself or someone else. I am sure I had information on here that stated it is no longer supported, but that information seems to be gone.
First, I am no longer actively supporting ddrutility. Second, your question is beyond the scope of the project. You now know what files are corrupt, so you can extract (copy) them to work with them. You would need to find a tool that repairs .jpg files. Chkdsk will not repair any files at all, it is only for attempting to repair (if not poorly) a corrupt file system, so that missing files could be possibly found. But it can also cause loss of file access, depending on the situation. I would only...
There is no new version of ddrutility. My new project is HDDSuperClone, but it is not open source. I don't know for sure if ddrutility is still compatible with the latest version of ddrescue, as I don't test it anymore. But I don't have any reports that it is not compatible. Regards, Scott
Hi Guillaume, Congratulations on your (95%) success! I even learned something that I did not know about using cp to copy sparse files. You did a very good job of explaining things. And thank you very much for your donation :) Regards, Scott