JSI Tip 10473. When a Windows Server 2003 cluster server starts, event ID 57, event ID 55, and event ID 50 are logged in the System event log?

Event ID 57, event ID 55, and event ID 50 are logged in the System event log when you start a Windows Server 2003 that is running Windows Clustering:

Event Type: Warning
Event Source: Ftdisk
Event ID: 57
Description: The system failed to flush data to the transaction log. Corruption may occur.

Event Type: Error
Event Source: NTFS
Event ID: 55
Description: The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume

Event Type: Warning
Event Source: Ntfs
Event ID: 50
Description: {Delayed Write Failed} Windows was unable to save all the data for the file. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

A conflict between the NTFS file system and Clusdisk, the cluster services driver component filter, causes this behavior to occur when the cluster node computer starts.

If you experience this behavior, it does not indicate a hard disk problem, and can be safely ignored.