If the hard disk on which you want to run Chkdsk contains the quorum log, temporarily move the quorum to another shared disk. On the Quorum tab, note which hard disk is the quorum hard disk. Start the Cluster Administrator tool, right-click the cluster name, and then click Properties. Quit all programs and stop all non-cluster-aware services. If you suspect that there is file corruption on the shared disk, use the following steps to close all open handles to the shared disk and run Chkdsk on the drive: Running Chkdsk in Read-Only mode may seem to work, but Chkdsk does not fix any problems. This causes Chkdsk to report that it cannot determine the file system on a shared cluster disk.
However, if you are using Windows Clustering, the file system does not mount the shared disk until the Cluster service starts because the owner of the shared disk is unknown. Typically, there are no services or drivers running that prevent autochk (a derivative of Chkdsk) from checking the disk when the computer restarts. Under most circumstances, running Chkdsk with the /F or /R switch requires the computer to be restarted because of open handles on the shared disk.
If you schedule Chkdsk to run after the computer restarts, Chkdsk may generate the following error message during the startup process:Ĭannot determine file system on drive ?\ drive letter. When you try to run the chkdsk /f or chkdsk /f /r command on a shared cluster drive, Chkdsk may not run and may state that the drive could not be locked for exclusive use. This article describes how to run the chkdsk /f command on a shared cluster disk.Īpplies to: Windows 10 - all editions, Windows Server 2012 R2 Original KB number: 176970 Summary
0 kommentar(er)
