Knowledge Base

Location of the Chkdsk Results for Windows Clustering Resources

Article ID: 272244

Article Last Modified on 3/1/2007

APPLIES TO

Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server
Microsoft Windows NT Server 4.0 Enterprise Edition

This article was previously published under Q272244

SUMMARY

When you bring a cluster server online and it has the dirty bit set, you can run the chkdsk command to verify the integrity of the cluster server. The version of the Windows operating system that your computer is running determines the degree of chkdsk logging that is available:

Windows NT 4.0: A status code is logged in the Cluster log.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

265533 Explanation of Chkdsk Status Codes in Cluster Log
Windows 2000: Results are logged in the Application and Cluster log.
Windows 2000 Service Pack 1 (SP1) and Windows Datacenter Server: Results are logged in the Application and Cluster log. In addition, the Cluster log references a log file in which detailed chkdsk output is recorded.

MORE INFORMATION

Windows NT 4.0

To capture detailed information by using chkdsk, stop the cluster server. To schedule chkdsk to run the next time that you restart the cluster, and have the results logged in the Application log as part of the autochk process:

Shut down all but one node in the cluster.
On the remaining node, use the following settings:

Cluster Disk - Manual
Cluster Service - Manual
Run chkdsk by typing the following line, and then click Yes to schedule it for the next time that you restart the cluster server:

chkdsk drive: /f

Note: If no open handles are present on the disk and chkdsk runs immediately, the chkdsk results appear on the screen instead of being logged in the Application log. To ensure that chkdsk is scheduled to run the next time that you restart the cluster server, change the directory to the chosen drive before you run chkdsk.
Restart the cluster server to run the autochk command .The autochk results are logged in the Application log with the source "AUTOCHK."
Reset Cluster Disk and Cluster Server back to the original settings:

Cluster Disk - System
Cluster Service - Automatic
Restart the computer. Verify that the cluster server starts, and then bring the other nodes online.

Make sure that no programs or services have handles open on the drive, which may require that you stop any cluster server that is using the drive. Start chkdsk manually, and then redirect the output to a text file. For example:

chkdsk x: /f >output.txt 2>error.txt

Windows 2000

Here are some examples of chkdsk output for a cluster server that is running a version of Windows 2000 earlier than SP1:

Cluster log

Physical Disk <Disk S:>: FixCorruption: chkdsk returned status of 1

For additional information about the status code, click the article number below to view the article in the Microsoft Knowledge Base:

265533 Explanation of Chkdsk Status Codes in Cluster Log
System log

Event Source: ClusSvc
Event ID: 1066
Description: Cluster disk resource <Disk S>: is corrupt. Running ChkDsk /F to repair problems.
Application log

Event Source: Chkdsk
Event ID: 26180
Description:
Checking file system on S:
The type of the file system is NTFS.
Volume label is S_Drive.
The MFT mirror is different from the MFT.
Correcting errors in the Master File Table (MFT) mirror.
Windows has made corrections to the file system.

528367 KB total disk space.
15547 KB in 26 files.
20 KB in 24 indexes.
0 KB in bad sectors.
4643 KB in use by the system.
4096 KB occupied by the log file.
508157 KB available on disk.

1024 bytes in each allocation unit.
528367 total allocation units on disk.
508157 allocation units available on disk.

Windows 2000 Advanced Server SP1 and Datacenter

In Windows 2000 Advanced Server SP1 and Datacenter, an additional entry is placed in the Cluster log that references an additional log file. The additional log file has a name in the following format:

ChkDsk_Disk#_SigXXXXXXXX.log

NOTE: This chkdsk log file represents the last chkdsk results for that specific hard disk. For example, if Disk 2 has two partitions, and you ran chkdsk against both of them, only the results of the last partition will be recorded in the log file.

NOTE: This functionality is only provided by the Physical Disk Resource type provided by Microsoft. Other disk resource types provided by 3rd party vendors may not support this feature.

Cluster log

Physical Disk <Disk S:>: DisksOpenChkdskLogFile: ChkDsk output is in file: C:\WINNT\cluster\ChkDsk_Disk2_SigCF06E06F.log
Physical Disk <Disk S:>: FixCorruption: chkdsk returned status of 1.
Example ChkDsk_Disk#_SigXXXXXXXX.log

Note: The type of the file system is the NTFS file system and the volume label is S_Drive.

chkdsk is verifying files (stage 1 of 3)...
0 percent completed.
1 percent completed.
.........
98 percent completed.
100 percent completed.
File verification completed.
chkdsk is verifying indexes (stage 2 of 3)...
0 percent completed.
1 percent completed.
.........
90 percent completed.
100 percent completed.
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
0 percent completed.
1 percent completed.
.........
98 percent completed.
100 percent completed.
Security descriptor verification completed.
Correcting errors in the Master File Table (MFT) mirror.
Windows has made corrections to the file system.

528367 KB total disk space.
15547 KB in 26 files.
20 KB in 24 indexes.
0 KB in bad sectors.
4643 KB in use by the system.
4096 KB occupied by the log file.
508157 KB available on disk.

1024 bytes in each allocation unit.
528367 total allocation units on disk.
508157 allocation units available on disk.

Additional query words: autochk mscs w2000mscs checkdisk check disk physical scandisk

Keywords: kbhowto KB272244

Microsoft KB Archive/272244

Contents