The option in TESTDISK (that will attempt using the $MFT mirror, which is NOT a copy of the $MFT, as said, but just it's "incipit") is clearly explained here: Yes, but as said there is NO $MFT copy ANYWHERE. ![]() To me your English is fine (or fine enough), I see more problems (NO offence intended ) in the logic behind it.īut I wanted to restore the copy of the MFT (on an NTFS volume) with TestDisk and I couldn't see where is the option for process it. I can't see possibility for re-create this problem in a partition, purposelyĮdited by u2o, 19 August 2011 - 04:09 AM. When I crash again with this problem, I will notify how I could fix it if I succeed. Thank you all for information, ideas and applications mentioned! Imagine a partition with 400 GB of files, programs, games and documents! I think it's impossible to recover by that way. Beyond the amount of knowledge needed, no one can get an idea of the exact number of files on a disk, especially if I will try to recover a disk that isn't mine. I do not think it's a good idea to do a manual work for this. Btw, have you recovered anything from the original? I think rebuilding/fixing a (severely) damaged $MFT needs lots of manual work, and just thinking about it gives me a headache. ![]() But I wanted to restore the copy of the MFT (on an NTFS volume) with TestDisk and I couldn't see where is the option for process it. My problem was not retrieve the data, I had done it. TESTDISK has a "fix $MFT" feature, but basically it just uses the $MFT_Mirror to fix it, (and as you might be familiar with $MFT_Mirror should be called $MFT_Mirror:Incipit as it stores only the first few records of the $MFT): May help, but if you are thinking of something like CHKDSK that will repair it "automagically", it simply won't happen. ![]() You see the point is that the question is pointless, it greatly depends on the type and extension of the damage the $MFT had.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |