Cached FRS Data on an NTFS Volume Is Lost Under Stress

View products that this article applies to.

This article was previously published under Q310841

SYMPTOMS

Under stressful disk input/output (I/O) on a volume that uses the NTFS file system, disk inconsistency may occur. You may receive the following error message:

Event ID 41.
The file system structure on the disk is corrupt and unusable. Please run the Chkdsk utility on the volume "Name".

Even if you do not receive this error message, you may receive any of the following error messages when you run Chkdsk:

Correcting error in index $30 for file 100

-or-

Deleting corrupt attribute record (16, "") from file record segment xxx.

The event ID for Windows 2000 for a dirty volume is:

Event Type:Error
Event Source:Ntfs
Event Category:Disk
Event ID:55
Date:1/31/2002
Time:10:21:13 PM
User:N/A
Computer:HOMESERVER
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume L:.

For more information, see Help and Support Center at http://support.microsoft.com.
Data:
0000: 04 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..?
0010: 00 00 00 00 32 00 00 c0 ....2..?
0018: 18 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Back to the top

CAUSE

Under stressful I/O transactions, some of the cached data may not be written to the disk.

Back to the top

RESOLUTION

Windows 2000

NOTE: This fix is superceded in the following Microsoft Knowledge Base articles:

318533 (http://support.microsoft.com/kb/318533/EN-US/ ) Windows 2000 SP2 Active Directory Rollup Hotfix

326800 (http://support.microsoft.com/kb/326800/EN-US/ ) Some Windows 2000 Kernel Hotfixes May Cause a Conflict with SP3 for Windows 2000: 2 of 2

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 (http://support.microsoft.com/kb/260910/EN-US/ ) How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

   Date         Time   Version        Size       File name
   ----------------------------------------------------------
   19-Feb-2002  00:56  5.0.2195.4948  1,686,720  Ntkrnlmp.exe
   19-Feb-2002  00:57  5.0.2195.4948  1,686,400  Ntkrnlpa.exe
   19-Feb-2002  00:57  5.0.2195.4948  1,707,072  Ntkrpamp.exe
   19-Feb-2002  00:56  5.0.2195.4948  1,664,448  Ntoskrnl.exe

Back to the top

Windows NT 4.0

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

   Date         Time   Version        Size       File name     Platform
   --------------------------------------------------------------------
   15-Dec-2001  01:07  4.0.1381.7118  1,403,712  Ntkrnlmp.exe  Alpha
   15-Dec-2001  01:07  4.0.1381.7118  1,375,680  Ntoskrnl.exe  Alpha
   05-Feb-2002  19:55  4.0.1381.7129    957,184  Ntkrnlmp.exe  I386
   05-Feb-2002  19:55  4.0.1381.7129    936,896  Ntoskrnl.exe  I386

NOTE: Because of file dependencies, this hotfix requires Microsoft Windows NT 4.0 Service Pack 6a.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.

Back to the top