Cluster is formed by using a local quorum resource after a cluster setup failure in Windows Server 2003


Symptoms


If you set up a new server cluster in Windows Server 2003, and the system boot disk, the pagefile disks, and the cluster disks are on the same storage area network (SAN) fabric, a setup failure may occur. In this scenario, the ClusSvc registry subkey may be re-created. Therefore, the ManageDisksOnSystemBuses registry entry is removed, and the server cluster is formed by using a local quorum resource.

In Windows Server 2003, you can use the ManageDisksOnSystemBuses DWORD registry entry to enable the system boot disk, the pagefile disks, and the cluster disks to be on the same bus.

Note After the cluster is installed and configured, an error message that resembles the following may be logged in the %Windir%\Cluster\Cluster.log file:




INFO Physical Disk <Disk Q:>: [DiskArb]- DisksArbitrate -.
INFO Physical Disk <Disk Q:>: [DiskArb] DisksOpenResourceFileHandle: Attaching to disk with signature eb14995a
INFO Physical Disk <Disk Q:>: [DiskArb] DisksOpenResourceFileHandle: Disk unique id present trying new attach
ERR Physical Disk <Disk Q:>: [DiskArb] Signature of disk has changed or failed to find disk with id, old signature 0xeb14995a new signature 0xeb14995a, status 2
ERR Physical Disk <Disk Q:>: SCSI: Attach, error attaching to signature eb14995a, error 2.
ERR Physical Disk <Disk Q:>: Arbitrate: Unable to attach to signature eb14995a. Error: 2.
INFO [MM] MmSetQuorumOwner(0,0), old owner 1.
ERR [FM] FmGetQuorumResource failed, error 2.
ERR [INIT] ClusterForm: Could not get quorum resource. No fixup attempted. Status = 5086
INFO [INIT] Cleaning up failed form attempt.
ERR [INIT] Failed to form cluster, status 5086.
ERR [CS] ClusterInitialize failed 5086
WARN [INIT] The cluster service is shutting down.
INFO [EVT] EvShutdown
WARN [FM] Shutdown: Failover Manager requested to shutdown groups.
INFO [FM] FmpCleanupGroups: Entry
INFO [FM] FmpCleanupGroups: Exit
INFO [Dm] DmShutdown
INFO [DM] DmpShutdownFlusher: Entry
INFO [DM] DmpShutdownFlusher: Setting event
INFO [DM] DmpRegistryFlusher: got 0
INFO [DM] DmpRegistryFlusher: exiting
WARN [MM] MMLeave is called when rgp=NULL.
ERR [CS] Service Stopped. exit code = 5086 Where error 5086 = The quorum disk could not be located by the cluster service.
The errors are logged when disks are enumerated after a group is moved or a node is restarted. If the Quorum disk is on the same bus as the system disk, this problem may cause the Cluster Service to stop.

Note The disk signature that is logged as a problem is not changed. There is no problem with the disk signature.

Resolution


Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows


To resolve this problem, install the updated Microsoft Storport storage driver, version 5.2.3790.217, and then modify the registry to add and to enable the ManageDisksOnSystemBuses registry entry in the ClusSvc registry subkey. To do this, follow these steps.

Note These steps must be performed on each node after the node is added to the cluster.
  1. Install version 5.2.3790.217 of the Storport storage driver. This driver is described in the following article:
    883646 The updated Storport storage driver, version 5.2.3790.217, fixes a range of Storport-related problems in Windows Server 2003

  2. Click Start, click Run, type regedit, and then click OK.
  3. Locate and then click the following subkey in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusSvc\Parameters
    Note If you have Service Pack 1 or a later service pack installed, locate and then click the following subkey in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Clusdisk\Parameters ManageDisksOnSystemBuses
  4. On the Edit menu, point to New, and then click DWORD Value.
  5. Type ManageDisksOnSystemBuses for the name of the DWORD, and then press ENTER.
  6. Right-click ManageDisksOnSystemBuses, and then click Modify.
  7. In the Value data box, enter a hexadecimal value of 1, and then click OK.
  8. Exit Registry Editor.
After you install the updated Storport storage driver and modify the registry, follow these steps to complete the procedure:
  1. After the first node is running the Cluster service, create new disk resources in Cluster Administrator, and then bring them online.
  2. After all the disks are online, use the procedure in the following article to move the quorum resource from a local disk to a disk resource that appears in the Cluster Administrator tool:

    280353 How to change the quorum disk designation

  3. Add the remaining nodes to the cluster, and then install the updated Storport storage driver. Add and enable the ManageDisksOnSystemBuses registry entry in the ClusSvc registry subkey for each node after it is added.
  4. Fail over all the resource groups to each cluster node.

Status


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

More Information


For more information about how to change the quorum on a server cluster, click the following article numbers to view the articles in the Microsoft Knowledge Base:

259267 Microsoft Cluster Service installation resources

280353 How to change the quorum disk designation

For more information about how to configure the quorum disk by using the cluster configuration wizard, click the following article number to view the article in the Microsoft Knowledge Base:

886569 How to add a registry value to a Windows Server 2003-based computer that you start from a SAN so that the startup disk, the pagefile disks, and the cluster disks are all on the same SAN fabric

For more information about how to configure a server cluster, see Windows Server 2003 Help.