EventID 55 - MFT (Master File Table) - NTFS

[Paul Doherty]

Hi,

I am experiencing repeated Event ID 55 messages in my Windows 2003
Server Event Log in relation to my OS drive (SCSI RAID 1 - mirror)

On two occasions, a scheduled reboot (so that chkdsk could fix errors)
resulted in the system failing to start (hung at starting windows 2003
screen). A manual run of chkdsk was required by booting the OS
installation CD and using the recovery console to run chkdsk.

Although chkdsk reports the errors as fixed, and the OS starts on next
reboot, the Event ID errors continue to persist.

My reading on the web leads me to believe that this is/may be due to
Master Table Corruption. I have a number of questions.

1. Is there a way to analyse the MFT to determine if this is the cause?

2. Is there a way to repair the MFT - (most solutions MS-KBs etc.
recommend reformatting the volume) - as I don't want to bring this
system down if at all possible.

3. Is there a list of root causes for this problem? (I'm suspecting
power failure in my case).

I've already performed memory/disk diagnostics and all is well.

I'm running Windows 2003 Server Standard Edition (Appliance Edition) on
a Dell PV 775N.

Best regards,

Paul

 

[Greg Hayes/Raxco Software]

Paul,

Sounds like possibly a hardware issue. Once you have "fixed" the drive by
running CHKDSK at boot, I'd suggest disabling write caching on the drive and
run for a while and see what happens.

- Greg/Raxco Software
Microsoft MVP - Windows File System

Want to email me? Delete ntloader.

 

[rsifre]

event id 55 win2k3 std. san spanned volume

I am having a similar issue, but I have not yet run the chkdsk. I have a spanned volume (3 luns - 2TB ea), the whole volume size is 6.0TB. I started getting this error about a week ago. The volume only contains data. I am trying to figure out what caused the problem and if I really need to run chkdsk. The volume currently has about 4.5TB of data.