Chkdsk /f Does Not Run on the Shared Cluster DiskLast reviewed: March 20, 1998Article ID: Q176970 |
The information in this article applies to:
SYMPTOMS When you use a chkdsk /f or chkdsk /f /r command on a Microsoft Cluster Server (MSCS) shared drive, chkdsk may not run after the system restarts or it may generate an error message stating that the volume is corrupt.
CAUSEUnder most circumstances, running chkdsk with either the /f or /r switch will require restarting because of open handles on the shared drive. Normally, when the computer restarts, there are no services or drivers running that prevent autochk from checking the disk. When using MSCS, the file system does not mount the shared disk until the Cluster service starts because the owner of the shared disk is unknown. This causes the drive type to show up as unknown. Running chkdsk in read-only mode may work properly, but does not fix any problems.
RESOLUTIONIf file corruption is suspected, follow these steps to close all open handles to the shared disk and run chkdsk /f against the drive:
To run chkdsk /f, you need to disable the clustering drivers so that, when restarting, the file system can mount. The second node in the cluster needs to be shut down so that it does not gain control of the shared disk when the primary node shuts down. To temporarily disable clustering, use the following instructions:
MORE INFORMATIONFor additional information on Microsoft Cluster Server, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q172944 TITLE : How to Change Quorum Disk Designation ARTICLE-ID: Q174797 TITLE : How to Run CHKDSK on a Shared Driveadditional query words: autochk MSCS Keywords : ntdriver ntsetup NTSrv kbhw kbsetup Version : WinNT: 4.0 Platform : winnt Issue type : kbprb |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |