• How to Run Chkdsk on a Server Cluster
  • Windows 2000 Chkdsk Management




    Download 191.2 Kb.
    bet8/10
    Sana21.03.2017
    Hajmi191.2 Kb.
    1   2   3   4   5   6   7   8   9   10

    Chkdsk and Server Clusters


    Running Chkdsk on a server cluster is the same as running Chkdsk on a stand-alone server, with the following exceptions:

    • On a server cluster, the filter driver ClusDisk.sys blocks all access to the shared disks until the Physical Disk resource has come online. This means that all Chkdsk functionality during the startup process (Autochk.exe) cannot see the disks and run.

    • When the Cluster service brings a disk online, it only checks to see whether the dirty bit is set on the physical disk.

    • You cannot run Chkdsk by using a registry setting (chkntfs /c or chkdsk /f) on a server cluster. You can only run Chkdsk by setting the dirty bit or by bringing down the whole cluster.

    • On a server cluster, you use FSUtil.exe to set the dirty bit, instead of running chkntfs /c to set the registry key.

    Note For more information about FSUtil.exe, see the “FSUtil.exe” section on page 31.

    • On a server cluster, before you run chkdsk /f against a volume, you must take offline all other resources in the group that the disk is in.

    The Cluster service also has some enhanced volume-corruption-checking options to give you more control over running Chkdsk.

    When you try to bring a Physical Disk resource online in Cluster Administrator, you may see one or more of the following symptoms:



    • The Physical Disk resource may fail, or it may come online.

    • The Physical Disk resource may appear to have stopped responding in an Online Pending state.

    • The chkdsk /f command may run on the drive.

    • The following event may be logged in the System event log:

    Event ID 1066

    Cluster resource Disk Y:: is corrupt. Running ChkDsk /f to repair problems.

    When the Cluster service brings a Physical Disk resource online, it checks the volume to see whether the dirty bit is set on the disk. By default, if the dirty bit is set, chkdsk /f is run on the disk before the Cluster service mounts the volume and makes it available to the system.

    As an additional check to detect a potential corruption problem, the Cluster service takes the following steps when it brings a Physical Disk resource online:


    1. It creates a temporary file (zClusterOnlineChk.tmp) in the root of the drive.

    2. It writes a test pattern and then saves the file.

    3. It reopens the file, reads the data, and then verifies the data.

    4. It deletes the file.

    If any part of this process fails, the Cluster service assumes that the disk is corrupted, and chkdsk /f is run.

    If the Cluster service can attach to the physical disk but has problems mounting the volume or file system, the Cluster service then tries to run chkdsk /f on the volume in case the volume is corrupted. This can sometimes be misleading when you are troubleshooting because the problem with the volume may not always be corruption; the problem may be another volume-mounting issue.

    The following is an example of a Cluster event log of the online process when Chkdsk is run:

    00000584.000005dc::YYYY/MM/DD-HH:MM:SS.SSS Physical Disk : DriveLetterIsAlive called for Online check

    00000584.00000430:: YYYY/MM/DD-HH:MM:SS.SSS Physical Disk: PnP Event GUID_IO_VOLUME_MOUNT for G (Partition1) received.

    000009d4.000009f4:: YYYY/MM/DD-HH:MM:SS.SSS [EVT] s_ApiEvPropEvents: Calling into EvpPropPendingEvents, size=648...

    000009d4.000009f4:: YYYY/MM/DD-HH:MM:SS.SSS [EVT] s_ApiEvPropEvents: Called EvpPropPendingEvents...

    00000584.000005dc:: YYYY/MM/DD-HH:MM:SS.SSS Physical Disk : DisksOpenChkdskLogFile: Chkdsk output is in file: E:\WINNT\CLUSTER\Chkdsk_Disk3_Sig3252EAA8.log

    00000584.00000430:: YYYY/MM/DD-HH:MM:SS.SSS Physical Disk: PnP Event GUID_IO_VOLUME_LOCK for 587488 received

    00000584.00000430:: YYYY/MM/DD-HH:MM:SS.SSS Physical Disk: PnP Event GUID_IO_VOLUME_DISMOUNT for 587488 received

    00000584.00000430:: YYYY/MM/DD-HH:MM:SS.SSS Physical Disk: PnP Event GUID_IO_VOLUME_UNLOCK for 587488 received

    00000584.000005dc:: YYYY/MM/DD-HH:MM:SS.SSS Physical Disk : FixCorruption: Chkdsk returned status of 2.

    00000584.000005dc:: YYYY/MM/DD-HH:MM:SS.SSS Physical Disk : DisksMountDrives: letter mask is 00000040.

    00000584.00000430:: YYYY/MM/DD-HH:MM:SS.SSS Physical Disk: PnP Event GUID_IO_VOLUME_MOUNT for G (Partition1) received.


    How to Run Chkdsk on a Server Cluster


    When you run Chkdsk on a server cluster, you use the same syntax and command-line switches that you use when you run Chkdsk on a stand-alone server; however, there are some considerations. When you try to run the chkdsk /f command or the chkdsk /f /r command on a cluster shared drive, Chkdsk may not run and may state that the drive could not be locked for exclusive use. If you schedule Chkdsk to run after the computer restarts, you may receive the following error message during the start-up process:

    Cannot determine file system on drive \??\drive letter.

    Under most circumstances, running Chkdsk with the /f or /r command-line switch requires that you restart the computer because of open handles on the drive from applications and user sessions. Typically, when the computer starts up, there are no services or drivers running that prevent Autochk from checking the drive. However, if you are using server clustering, the file system does not mount the shared drive until the Cluster service starts and brings the Physical Disk resources online. The ClusDisk.sys driver blocks all access to the drives until they are brought online. This causes Chkdsk to report that it cannot determine the file system on a cluster shared drive. Running Chkdsk in read-only mode may seem to work, but in this mode, Chkdsk does not fix any problems.

    FSUtil.exe is a utility in Windows XP and later that you can use on a Windows 2000 server cluster to set the dirty bit on the physical drive. Then, when the drive is failed over or brought online the next time, chkdsk /f is run against the drive. For more information about the FSUtil.exe tool, see the “FSUtil.exe” section in the Appendix on page 31 of this white paper.

    If you suspect that there is file corruption on the shared drive, close all open handles to the shared drive, and then run Chkdsk on the drive. To do so, follow these steps:


    1. Quit all programs, stop all cluster unaware applications, and then log on to the server with an account that has Administrative rights.

    2. Start Cluster Administrator, right-click the cluster name, and then click Properties.

    3. Click the Quorum tab, and then note which hard disk is the quorum disk. If the hard disk on which you want to run Chkdsk contains the quorum log, temporarily move the quorum disk to another shared drive.

    Note For more information, see the following Microsoft Knowledge Base article:

    280353 “How to Change Quorum Disk Designation”

    1. Find the group that contains the shared drive on which you want to run Chkdsk.

    2. Right-click the group name, and then click Take offline.

    This takes the whole group offline, including the shared drive, and closes all the handles to the physical drive.

    1. Right-click the Physical Disk resource that you want to run Chkdsk on, and then click Bring online.

    This brings the shared drive online.

    Note If the dirty bit was previously set, Chkdsk may automatically run, and the Physical Disk resource may stay in an Online Pending state and take awhile to come online. If this occurs, you will see a Command Prompt window with Chkdsk running, and Task Manager will show Chkdsk running as a process.

    1. At the command prompt, change to a drive other than the drive on which you are trying to run Chkdsk, and then type the following command, where drive is the shared drive:

    chkdsk drive: /f

    If you receive a “Disk cannot be locked” error message when you try to run Chkdsk, verify that all services and tools that have access to the drive are stopped, and then try to run Chkdsk again. Any service or program that is running and has an open handle to the drive can prevent Chkdsk from running. Windows 2000 can try to close the open handles to the shared drive by using the /x command-line switch. If you are prompted to close open handles, press Y.


    1   2   3   4   5   6   7   8   9   10


    Download 191.2 Kb.

    Bosh sahifa
    Aloqalar

        Bosh sahifa


    Windows 2000 Chkdsk Management

    Download 191.2 Kb.