Quote:
If the rescue is started with hddsuperclone with the default settings, after it is a bit into phase 1 I am able to diagnose some things from the log. Such things as if it is suffering from some sort of slow responding issue, or has a bad head. I do not yet have any documentation available for how to do that, so I am always willing to help with the diagnosis.
Well, that's kind of you anyway – but I suppose that it also helps you to improve your programs, by trying to figure out unexpected issues and implement specific workarounds. I mentioned HDDSuperTool in
this thread, asking if it could do anything useful in the case I described – what would you have to say about it ? I tried HDDSuperClone for the first time with that ST3000DM001, but at that point it didn't seem to fare any better than ddrescue ; it's possible that I couldn't figure out how to set it properly to get the best possible result. But it seems unlikely that I can salvage significantly more than I already did, i.e. recover at least one of those 6 corrupted video files in its entirety. At least I was hoping that I could learn something from this unfortunate experience (which could have been way worse), but the replies I got have been quite frustrating...
Quote:
Someone just posted in the discussion area of ddrutility with a possible method of targeting ntfs files, using the tools available in ddrutility along with spreadsheet software. It is somewhat complicated and requires multiple steps, and I am not sure the average user could do it, but the concept seems solid. It is a very clever idea, and I am quite impressed with it. If he is successful with the recovery, I may have to post that how-to in some other places.
What discussion are you refering to ? I'm not sure if I understand what you mean by “targeting NTFS files” – aren't those tools already aimed at targeting NTFS files ? (Bitmap and MFT, respectively, for ddru_ntfsbitmap and ddru_ntfsfindbad.)