[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1834
  • Last Modified:

$Mft error

I have a Windows 2003 SP1 server.  It is a single server domain controller for a small office.  A recent power outage has caused the following error to pop up.  C:\$Mft is corrupt and unreadable.  Please run the Chksdk utility.  I have researched this and found to try either a chkdsk /r from the recovery console or a complete reinstall of the OS.  
A reinstall will take hours.  Do you have any other suggestions that might help me get past this?  The server seems to be running fine with exception of Backup Exec and a printer not working.  Also, the swapfile is not located on the boot partition.  I am also getting the following error in the event log.

Event Type:      Error
Event Source:      Ntfs
Event Category:      Disk
Event ID:      55
Date:            5/1/2006
Time:            10:32:32 AM
User:            N/A
Computer:      MAIL
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume4.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 04 00 04 00 02 00 52 00   ......R.
0008: 02 00 00 00 37 00 04 c0   ....7..À
0010: 00 00 00 00 02 01 00 c0   .......À
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 81 01 22 00               .".    

I am planning on trying the chkdsk /r after 5 tonight.  Any help greatly appreciated.
  • 2
  • 2
2 Solutions
There are few other suggestions you might want to look at here:


You have to be very careful with this kind of error. It seems you might have a bad hard drive.

It seems you do not have RAID on the server either. If you have a RAID 1 or RAID 5 this kind of error can be early taking care of.

You shuld get a replacement hard drive, then using image utility to backup the entire hard drive image, then restore the image to the new hard drive.

You should also plan to mirgrate to RAID configuration later on.

Good luck
daxatviyuAuthor Commented:
One thing I forgot to add.  This problem occurred after a power outtage and discovering that the battery is bad in the UPS.  We are replacing the UPS, but I am not sure the HDD is bad, I think the un-graceful shutdown maybe the cause of this error.
check even view see if you have any kind bad sector. If you do then you need to replace the hard drive, if you don't have bad sector error, chkdsk should fix the problem

good luck
daxatviyuAuthor Commented:
The problem in this case actually turned out to be the Volume Shadow Service working with Veritas Backup Exec 10.  Once I stopped the Backup Exec services, the server stopped getting errors and ran great.  On restart it still ran a defrag, all was well, I uninstalled Veritas 10 and installed Veritas 10d.  Thanks for your quick response guys.

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now