MFT Corruption

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi folks -

We have a Windows 2000, SP4 file server that has about 90 shares, both
Windows volumes and Mac volumes (I'm not responsible for that).

The Administrator of that server began to have problems when trying to
change permissions, rename folders, delete folders, etc., but only for
certain folders. There was also an intermittent problem creating new
folders. These problems only affected the data drive (hardware RAID 5). The
OS drive (hardware mirror) was fine. When these problems occurred, an error
message would pop up saying that the file system was corrupt or something
similar.

Every time that would happen we got corresponding NTFS entries in the System
Log:
"The file system structure on the disk is corrupt and unusable. Please run
the chkdsk utility on the volume D:."

After about a week or more of that, we began to randomly get popups saying
this:
"Application popup: Windows - Corrupt File : The file or directory D:\$Mft
is corrupt and unreadable. Please run the Chkdsk utility."
Eventually the Mac shares could not seen by clients, which undoubtably was
related. If we created a new one, that one could be seen.

Needless to say, chkdsk didn't solve the problem after running it maybe 5
times.

My solution was simply to back up the data, format the data drive, then
restore from backup. I made certain not to back up System Volume Information
or Recycle Bin and there were no visible files at the root of the drive, just
directories.

Since I have done that, all of the Event Log errors and popup error messages
have gone along with all the other above mentioned problems that affected
changes to files or folders.

Given what I have done as the solution and given the fact that the problems
appear to have ceased, is there any reason that I should think that I haven't
really solved the problem?

Thanks.
 
Charlie said:
Hi folks -

We have a Windows 2000, SP4 file server that has about 90 shares, both
Windows volumes and Mac volumes (I'm not responsible for that).

The Administrator of that server began to have problems when trying to
change permissions, rename folders, delete folders, etc., but only for
certain folders. There was also an intermittent problem creating new
folders. These problems only affected the data drive (hardware RAID 5). The
OS drive (hardware mirror) was fine. When these problems occurred, an error
message would pop up saying that the file system was corrupt or something
similar.

Every time that would happen we got corresponding NTFS entries in the System
Log:
"The file system structure on the disk is corrupt and unusable. Please run
the chkdsk utility on the volume D:."

After about a week or more of that, we began to randomly get popups saying
this:
"Application popup: Windows - Corrupt File : The file or directory D:\$Mft
is corrupt and unreadable. Please run the Chkdsk utility."
Eventually the Mac shares could not seen by clients, which undoubtably was
related. If we created a new one, that one could be seen.

Needless to say, chkdsk didn't solve the problem after running it maybe 5
times.

My solution was simply to back up the data, format the data drive, then
restore from backup. I made certain not to back up System Volume Information
or Recycle Bin and there were no visible files at the root of the drive, just
directories.

Since I have done that, all of the Event Log errors and popup error messages
have gone along with all the other above mentioned problems that affected
changes to files or folders.

Given what I have done as the solution and given the fact that the problems
appear to have ceased, is there any reason that I should think that I haven't
really solved the problem?

Thanks.

It is likely that you have solved the problem. However, I would
also run chkdsk /f /r to make sure that there are no bad clusters
on the disk.
 
Pegasus (MVP) said:
It is likely that you have solved the problem. However, I would
also run chkdsk /f /r to make sure that there are no bad clusters
on the disk.

Thanks, much.
Yes, I did run "chkdsk /r" last night and it reported no files in bad sectors.
 
Back
Top