Chkdsk /f Does Not Run on the Shared Cluster Disk

Last reviewed: March 20, 1998
Article ID: Q176970
The information in this article applies to:
  • Microsoft Windows NT Server, Enterprise Edition version 4.0 - Microsoft Cluster server

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.

CAUSE

Under 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.

RESOLUTION

If file corruption is suspected, follow these steps to close all open handles to the shared disk and run chkdsk /f against the drive:

  1. Shut down any applications and stop all services that may be accessing the shared drive.

  2. Move the quorum log to a different shared disk.

  3. From the command prompt, change to a drive other than the one you are attempting to run chkdsk on.

    For example, assuming the shared drive is drive X and Windows NT is installed on drive C, you would type the following command from drive C:

          chkdsk /f /r X:
    

Chkdsk should complete as all open handles have been closed. If there is still an open handle, chkdsk will state that the drive cannot be locked. If there is not another shared disk to move the quorum log to, restarting the computer will be required.

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:

  1. Log on to Windows NT as an administrator.

  2. Run the chkdsk /f /r command for the shared disk.

  3. In the Devices tool in Control Panel, select Cluster Disk and then click Startup.

  4. Change the Startup type to Disabled.

  5. In Services in Control Panel, select the Cluster Server service and then click Startup.

  6. Change the startup type to Disabled.

  7. Exit Control Panel and then shut down and restart the computer. Chkdsk /f should be able to run without interference from Cluster Disk.

  8. After completing repairs, change the Startup type back to its original setting and restart the system again to enable MSCS.

MORE INFORMATION

For 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 Drive

additional query words: autochk MSCS
Keywords          : ntdriver ntsetup NTSrv kbhw kbsetup
Version           : WinNT: 4.0
Platform          : winnt
Issue type        : kbprb


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 20, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.