Microsoft KB Archive/891189

From BetaArchive Wiki

Article ID: 891189

Article Last Modified on 7/24/2007



APPLIES TO

  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition




SYMPTOMS

In a Microsoft Windows Server 2003 Microsoft Cluster Service (MSCS) environment, the MSCS service tries to recover the quorum disk when the MSCS folder in the quorum disk is inaccessible or does not exist. In this situation, the quorum disk may be damaged after MSCS tries to recover the quorum disk.

You can test whether the quorum disk is affected with this problem by running Chkdsk.exe in read-only mode. You can run Chkdsk.exe in read-only mode if you do not use the /f or /x options. For example, you can type chkdsk drive letter: at a command prompt, and then press ENTER. You can use the following switches:

  • /f Fixes errors on the disk.
  • /x Forces the volume to dismount if it is required.

If the quorum disk was affected with this problem and you run Chkdsk.exe in read-only mode, you may receive the following error message:

The type of the file system is NTFS.
The volume is in use by another process.
Chkdsk might report errors when no corruption is present.
Volume label is Volume.

WARNING! F parameter not specified. Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)... Deleting corrupt attribute record (112, "") from file record segment 3.
File verification completed. Errors found.

CHKDSK cannot continue in read-only mode.

Important If this problem occurs, do not run Chkdsk.exe with the /f or /x option on the quorum disk. If you run Chkdsk.exe with the /f or /x option on the quorum disk, the data on quorum disk may be corrupted.

CAUSE

This problem occurs when the MSCS service tries to recover the quorum disk from a corrupted state. In this case, incorrect volume information data may be written to the quorum volume.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003

   Date         Time   Version       Size       File name  Platform
   ----------------------------------------------------------------
   12-Jan-2005  18:07  5.2.3790.247    619,008  Ntfs.sys   x86
   12-Jan-2005  03:17  5.2.3790.247  1,695,232  Ntfs.sys   IA-64

WORKAROUND

To work around this problem, you can recover the quorum disk when you apply this hotfix on all the MSCS nodes and then format the quorum disk. This procedure is useful if the quorum disk is already affected with this problem.

To recover the quorum disk when you apply this hotfix on all the MSCS nodes and then format the quorum disk, follow these steps:

  1. Double-click the 217103_enu_x86 or IA-64 platform type_zip.exe file, and then extract the file contents to a location that can be accessed by all the nodes in the MSCS cluster.
  2. Log on to the Windows Server 2003-based computer by using an account that has administrative permissions.
  3. Double-click WindowsServer2003-KB891189-x86 or IA-64 platform type-enu.exe.
  4. Back up the quorum disk by using the Windows Server 2003 Backup and Recovery Wizard or a third-party backup utility.
  5. Format the quorum disk by using the Disk Management utility. For additional information about how to format a quorum disk , click the following article number to view the article in the Microsoft Knowledge Base:

    257937 How to format an existing partition on a shared cluster hard disk

  6. Restore the quorum disk using the Windows Server 2003 Backup and Recovery Wizard or a third-party backup utility.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For additional information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates



Additional query words: quorum disk ntfs file system chkdsk server cluster

Keywords: kbqfe kbhotfixserver kbbug kbfix kbwinserv2003presp1fix KB891189