The file or directory $ MFT is corrupt and unreadable. Run the chkdsk utility. [chkdsk utility] [volume c]

Q: Server 2003. So far, everything still works, I get this error message when you connect remotely with Remote Desktop.
What exactly does this mean?

Edit:
Upon checking the logs I found a couple of entries shows an error 55 .
“The file structure on disk is corrupt and unusable. Run the on the :”


Best Answer: If you are using Windows, then insert original disk in CD drive, when it opens up, see the options and select repair. click OK.
This will reload the windows and repair all your currupted files without disturbing your data. Once it is done, reboot your PC.
Hope this will solve your problem.

Re:http://support.microsoft.com/kb/176646

RESOLUTION
WARNING: When Chkdsk detects problems with the file system and attempts to repair the damage, data loss can occur. Microsoft does not recommend running Chkdsk with the /f command-line switch unless you have a full backup of your hard disk.

Attempt to repair the damaged file, folder or file system index using Chkdsk. To do so, follow these steps:
1. Click Start, and then click Run.
2. In the Open box, type chkdsk /f <drive>:, where <drive> is the letter of the drive on which the damaged file, folder or file system index exists.
3. Click OK.
NOTE: If the hard disk is large, Chkdsk may take several minutes to several hours to complete.


Re:I've had the error before on a 2k3 machine at work. use chkdsk /r

Re:/R: Locates bad sectors and recovers readable information (implies /F).

From chkdsk /?


Re:Fixing disk errors

Chkdsk corrects disk errors only if you specify the /f command-line option.

/r : Locates bad sectors and recovers readable information.
/f : Fixes errors on the disk.

http://www.microsoft.com/resou…docs/en-us/chkdsk.mspx (http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx)


Re:chkdsk /r is more comprehensive than /f and includes /f.

Re:Regular backups have been made of this system to an external drive. I've also been told to try the /f switch with chkdsk. Someone also said to check chipset drives and BIOS IDE settings? I'm sort of discounting that since this system has been A-OK up until now (over a year).

Re:Have you tried running chkdsk /r yet?

Regardless, you should make sure you have a current backup of all data on that system NOW. You could very well have a failing drive.


Related posts

Leave a comment

0 Comments.

Leave a Reply


click to changeSecurity Code

[ Ctrl + Enter ]