MFT corrupted

[Skye Flynn]

How do I fix this problem? I have access to my main drive C:\ but not my secondary drive D:\. The problem is making start ups very slow. I have run the usual scf, chkdsk, and SFCfix to no avail. Thanks for any advice you can provide. Below is from event viewer warning. Event ID 55.

Log Name: System
Source: Ntfs
Date: 3/26/2019 1:36:08 PM
Event ID: 55
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: Lenovo-PC
Description:
A corruption was discovered in the file system structure on volume D:.

The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x3000000000003. The name of the file is "<unable to determine file name>".

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Ntfs" Guid="{DD70BC80-EF44-421B-8AC3-CD31DA613A4E}" />
<EventID>55</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-03-26T20:36:08.886628100Z" />
<EventRecordID>489776</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="7576" />
<Channel>System</Channel>
<Computer>Lenovo-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriveName">D:</Data>
<Data Name="DeviceName">
</Data>
<Data Name="CorruptionState">0x0</Data>
<Data Name="HeaderFlags">0x922</Data>
<Data Name="Severity">Critical</Data>
<Data Name="Origin">File System Driver</Data>
<Data Name="Verb">Bad FRS</Data>
<Data Name="Description">The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x3000000000003. The name of the file is "&lt;unable to determine file name&gt;".
</Data>
<Data Name="Signature">0x6cc9467b</Data>
<Data Name="Outcome">Volume Not Available</Data>
<Data Name="SampleLength">0</Data>
<Data Name="SampleData">
</Data>
<Data Name="SourceFile">0x6</Data>
<Data Name="SourceLine">152</Data>
<Data Name="SourceTag">337</Data>
<Data Name="CallStack">Ntfs+0x15c140, Ntfs+0xcd62e, Ntfs+0xcd804, Ntfs+0xcd148, Ntfs+0x28918, Ntfs+0x177ae3, Ntfs+0x174c79, Ntfs+0x178437, Ntfs+0x176991, Ntfs+0x13cd4d, ntoskrnl+0x12f355, ntoskrnl+0x148ebd, ntoskrnl+0x831d6, ntoskrnl+0x12f2a9, Ntfs+0xfc76, ntoskrnl+0x148e3d, ntoskrnl+0x82a01, ntoskrnl+0x81faa, Ntfs+0x1234a, Ntfs+0x12de1d, Ntfs+0x81090, Ntfs+0xe62a, ntoskrnl+0x5bb8f, ntoskrnl+0xd3dc2, ntoskrnl+0x147d36</Data>
</EventData>
</Event>

 

[Digerati]

What switches did you run with chkdsk?

I recommend you open a command prompt running as administrator. Then enter chkdsk D: /r and press Enter and see if that helps. Note this could take many hours to complete and may appear to be locked up. Just let it finish. Otherwise, I would urge you to see if you can access and back up any data on that drive you don't want to lose, then replace the drive if chkdsk cannot resolve it.

If still under warranty, visit the drive makers website and run their diagnostic program. They cannot really refuse an RMA if the drive fails their own diagnostic program.

 

[Skye Flynn]

Thank you for your response. I tried everything but the kitchen sink to diagnose/repair/gain access to the drive, but nothing worked. So, I did a quick format of the drive, and that allowed me to gain access to the drive, albeit a drive with no data. Fortunately I back up my drives daily. Problem solved ungracefully!

If I knew how to correct a corrupted MFT file at a given address, I might have solved the problem. But if that required accessing the drive, then, alas, that also would have not worked.

This is a wonderful website. Thanks all.

 

[Digerati]

I am glad you got it sorted out and thanks for posting your followup. Note file table corruption is pretty rare, but it does happen. It could have been a one-time fluke or a sign of bad things to come. I would keep an eye on it, and for sure, keep up the daily backups.

 

[Skye Flynn]

Thanks, Bill. FYI. I don't really need this drive, so I disabled it and that resolved additional issues. No more raid warnings, etc., and startup is down to 1 minute from approx. 15 minutes. Oh, joy! It's amazing what small clues I discovered when reading the responses to my post. Thank you!

 

[Digerati]

and startup is down to 1 minute from approx. 15 minutes

Oh wow! That's big. Not sure I would have had the patience to wait out 15 minutes. When I had spinners (I've gone to all SSDs), my patience ran out after 5 minutes even though everything ran fine once fully booted.

And you are welcome though clearly you did all the heavy lifting!