Testdisk mft and mft mirror are bad

Windows was running chkdsk, battery cleared in the time of that, and lappeak shut down. When I start it up, I get something like:

Disk read errorI tried booting from Window"s disk and also running chkdsk /f /r, that didn"t work-related. I have an additional partition via Linux installed. I tried to run ntfsresolve from tbelow, yet it outputs:

Mounting volume... $MFT need to be non-resident.Faicaused pack $MFT: Input/output errorFAILEDAttempting to correct errors... $MFT should be non-resident.Failed to fill $MFT: Input/output errorFAILEDFaicaused startup volume: Input/output errorChecking for self-situated MFT segment... OK$MFT have to be non-resident.Faibrought about load $MFT: Input/output errorVolume is corrupt. You must run chkdsk.I also tried testdisk to Repair MFT. It additionally errors with:

MFT and also MFT mirror are bad. Faibrought about repair them.What deserve to I carry out at this point? I desire to obtain my records back in the very main location.

You watching: Testdisk mft and mft mirror are bad


windows-10 hard-drive partitioning mft
Share
Improve this question
Follow
asked May 5 "17 at 14:46
*

OverCoderOverCoder
1541010 bronze badges
4
Add a comment |

1 Answer 1


Active Oldest Votes
2
Your output reflects numerous I/O errors, which is not a promising authorize. The a lot of prevalent cause of such errors is failing hardware. Hence, I suspect that you"re looking at a hardware worry -- either somepoint that just coincidentally proved up at this allude or that was somejust how led to by the power failure. (You don"t say why you were running CHKDSK in Windows. If it was bereason the disk was acting up, the hardware problem may have actually predelivered everything else, and also just got worse after the power failure.)

You could desire to examine the SMART condition of the disk. I"m not a Windows skilled, and of course given the nature of the trouble, you can"t execute this from your continual Windows installation. See this question for some pointers on getting SMART information from Linux. Alternatively, you can try doing it from a Windows emergency disk, but I can not help a lot on that method. Note that SMART is a diagnostic tool, not a repair tool. If you check out SMART errors, you"ll understand that the disk is failing, however it will not really assist you recuperate your information beyond understanding that you must gain a brand-new disk. This is much from specific to work, yet it"s worth trying.

If SMART says the disk is failing, stop using it! Some kinds of disk failures can spreview over time, bring about one poor sector to become ten, then a hundred, and so on. Hence, the longer you use the disk, the less likely it is that you"ll be able to recoup information from it. If SMART says there"s a difficulty, shut the computer system dvery own, buy a brand-new disk, and power up aobtain only once you"re ready to relocate information to the brand-new disk.

See more: Help: The Steam Install Folder Is Currently Not Writable Mac

If you perform acquire a brand-new disk, you might perform a low-level copy from the old disk to the brand-new one. Aget, as I"m not a Windows skilled, I can not imply a specific Windows tool to assist with this; however in Linux, you can usage ddrescue, which does its best to recover information from a failing disk and also carry it to another one. There"s a possibility that repair tools could then work-related on the brand-new disk.

In a worst-instance scenario, if you can"t coax the mechanism right into functioning well sufficient to mount the volume, you can use a tool favor PhotoRec to recover individual papers. The last I heard, though, PhotoRec did a poor job of respanning filenames, so you"ll be left via a huge mound of poorly-named documents to kind with. I"ve heard that some Windows-particular devices do a better job of reextending filenames, but I do not know the details, so I can not recommend a details tool.

See more: Candysims4 — The Sims Resource Not Working, Is The Sims Resource As Bad As Everyone Says

One last comment: ntfssolve in Linux does alongside nothing; it simply checks some extremely fundamental NTFS functions and then marks the filesystem as needing repair in Windows. Thus, I wouldn"t suggest wasting any even more time via that tool.