Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error message: The file or Dir c:\$Mft is corrupt or unreadable

196 views
Skip to first unread message

John

unread,
Feb 26, 2003, 11:18:48 AM2/26/03
to
To All;

This is the first problem(s) I've had with WINXP PRO.
First of all I'd like to point out that I have two HDDs on
this PC.
The first-BOOTABLE ONE has no problems. I've ran diags,etc.
Both HDDs are formatted as NTFS. I've installed SP1 with
all the updates as well.
This same drive I had running for a year without any
problems - is now giving me the 'The file or directory
c:\$Mft is corrupt and unreadable please run the chkdsk
utility.' after I reformatted it.-it was running NTFS
before the Format.
This comes and goes - I've ran the CHKDSK /f /r, it seems
to fix the problem for a while. It always returns.
The strange thing here is that it doesn't seem to fix my
Mft.
Both HDDs are on the same IDE channel. I've searched all
over MS forums /support/etc. The only documentation
available on this is pointing to CLUSTER disk access
problem-not my case here. Just a simple install of XP Pro.
I'm also getting 'Delayed Write Failed' messages. With
having this - I reaalize that it could be UDMA is using a
40-wire connection???? I have a newer INTEL MOBO without
force faster UDMA support. I'm guessing this problem is
due to my cable??
My BIG question to you ALL - Would this 40-wire cable also
be the cause of my 'The file or directory c:\$Mft is
corrupt and unreadable please run the chkdsk utility.'
ERROR????

Any advice you be NICE!!
Thanks and Kind Regards!


Greg Hayes/Raxco Software

unread,
Feb 26, 2003, 2:37:29 PM2/26/03
to
John,

I suspect that the $MFT corrupt issue is related to the delayed write
failure. If data is not being written to the drive, depending on what that
data is, it could leave files corrupted of even the file system metadata
corrupted.

- Greg/Raxco Software
Microsoft MVP - Windows Storage Management/File System

"John" <john....@hds.com> wrote in message
news:04a701c2ddb2$be5bf550$2f01...@phx.gbl...

john

unread,
Feb 26, 2003, 8:47:34 PM2/26/03
to
replaced the cable with a 80wire/40pin - problem has gone
away!
Thanks!!!!
>.
>
0 new messages