The Quorum Resource is on an Inaccessible or Nonfunctioning Disk
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
To understand this topic in context, see the flowchart in Troubleshooting Quorum Resource Problems.
If you can start the Cluster service with the /fixquorum option and can use Cluster Administrator to bring nonquorum disk resources online, but cannot bring the quorum resource online, the disk used for the quorum resource might be inaccessible or might have failed. Note that when the quorum resource cannot be brought online in this way, the Cluster service will stop again, even though it was started with the /fixquorum option.
A disk might be inaccessible because of incorrectly configured hardware or software, for example, multipath I/O (MPIO) software. There are multiple causes for failure of a hard disk.
For further diagnosis, you can study events in the system log for indications of hardware errors. Then, use Device Manager to review the condition of the disk that the quorum resource is on. If there is a disk signature problem but the quorum disk can function otherwise, correct the disk signature problem. If the disk will not function, use either Clusterrecovery or Cluster Administrator to use a different disk for the quorum resource.
To use Device Manager to review the condition of the disk that the quorum resource is on
On the node on which you have started the Cluster service with the /fixquorum option, click Start, click Programs or All Programs, click Administrative Tools, and then click Computer Management.
Click Device Manager.
In the Details pane, click Disk drives and then try to view the disk that the quorum resource is on.
If you cannot view the disk and want to further diagnose its condition, see diagnostic tools or information provided by the disk manufacturer, or contact the disk manufacturer for assistance.
If you can view the disk, look in the event log for an instance of Event ID 1034 related to the quorum resource, and record the disk signature expected by the Cluster service for the quorum resource. Then use one of the following procedures to correct problems with the disk.
To use Clusterrecovery to correct problems with the quorum being on a nonfunctioning disk
On the node on which you have started the Cluster service with the /fixquorum option, run Clusterrecovery.exe, which is described in Configuring a Computer for Troubleshooting the Quorum Resource in a Server Cluster. Use Clusterrecovery to substitute a new disk for the disk that has been having problems, referring to Clusterrecovery Help as needed.
Clusterrecovery makes it relatively easy to configure a new disk to replace the disk that has developed a problem.
To use a different disk for the quorum resource without using Clusterrecovery
After starting the Cluster service with the /fixquorum option, from the disks available on the cluster storage, choose the disk that you will use for the quorum resource. If the disk has two or more NTFS partitions, ensure that all partitions on the disk are assigned drive letters.
Using Cluster Administrator, create a Physical Disk resource or other storage-class resource for the new disk (unless one has already been created).
In the console tree, click the Resources folder.
In the details pane, click the resource that you will use for the quorum resource. If the resource is online, on the File menu, click Take Offline.
In the console tree, click the cluster name and then on the File menu, click Properties.
On the Quorum tab, click Quorum resource, and then select the disk or storage-class resource you want to use as the quorum resource for the cluster.
In Partition, if the disk has more than one partition, click the partition to be used for the quorum resource.
In Root path, type the path to the folder on the partition. For example:
In the console tree, click the Resources folder and then, in the details pane, click the new quorum resource.
On the File menu, click Bring Online to confirm that you can bring the new quorum resource online.
Stop the Cluster service by typing:
net stop clussvc
On the same node on which you performed the preceding steps, restart the Cluster service by typing:
net start clussvc
You must perform this step, which forms the cluster, from the node on which you performed the preceding steps. This is because the new information that you configured on this node does not exist yet on the other nodes. After the other nodes have joined the cluster, they will receive the new information about the location of the quorum resource and will be able to form the cluster as needed.