- A disk has become unavailable or inaccessible, and therefore, the Cluster service cannot find it.
- The signature on the disk has been changed.
- Make sure that the disk is actually exposed through the shared interconnects and is visible to the operating system. To do this:
Start, click Run, type
CompMgmt.msc, and then click OK.
- In Computer Management under System Tools, Device Manager, look under Disk Drives, and you can view all the logical disks that are being presented to the node.
All nodes in a cluster can see the same number of disk drives for disks that are managed by the cluster. For example, if there are 10 disks that are managed by the cluster, all 10 are visible to all nodes in the cluster. If you know the Target ID and LUN of the disk, you can validate them by clicking
Properties for each disk.
If the count does match, and if the Cluster service is up and running, reduce the complexity, if possible, by moving the all the disk resources (groups that host the resources) to a single node. If the Custer service has failed, shut down all nodes and restart one node.
- If the disk signatures have changed, use Dumpcfg.exe to write the expected signature back to the disk.
The signatures of the disks as enumerated by dumpcfg should match the list that is derived from the following registry subkey:HKLM/System/CurrentControlSet/Services/Clusdisk/ParametersClusdisk uses this information to bind to disks that are managed by the Cluster service.
- If the signatures in the list do not match the registry subkey list, you must correctly identify the disks that have had their signatures changed and reset them to the expected signatures. To do this:
- Power down all but one node.
- Document the disk number:
- Open Computer Management, double-click Storage, and then click Disk Management.
- In Logical Disk Manager, note the disk number and label that is associated with the failing disk. This information is to the left of the partition information. For example: Disk 0.
For example: "The disk associated with cluster disk resource 'Disk Q:\'". The disk label should not change even if the signature has. The disk label will help you correctly identify the problem disk. Once the disk has been correctly identified its signature can be checked again to validate the mismatch.
- If you cannot see the disks in DiskMgmt.msc, set the Cluster service and Cluster Disk device to Manual, and then restart the node (all other nodes should remain shut down). To do this, follow these steps.
NOTE: This step may not be necessary.
- Click Start, point to
Programs, point to Administrative Tools, and then click Computer Management.
- Click Device Manager in the left pane, and then click Show Hidden Devices on the
- In the right pane, view the non-Plug and Play drives section, and then double-click the Clusdisk driver.
- On the Driver tab, change the
Startup type option from System to
- In the left pane, double-click "Services and Applications", and then click "Services".
- In the right pane, double-click the
Cluster service, and then click Disabled in the Startup type box.
- Restart the node, and then repeat step 2 if necessary.
- Click Start, point to
- Write the signature that the Cluster service expects to the disk:
- Obtain the expected signature from the "Description" section of the Event ID 1034 error message. For example: "The expected signature of the disk was 12345678."
- Copy DumpCfg.exe from the Windows 2000 Resource Kit to the local node. At the command prompt, type
dumpcfg.exe. Under the [DISKS] section, the disk number and signature for all available disks is displayed. Validate the actual disk signature with what the Cluster service expects.
- Write the expected signature to the disk by using by using the following command, where 12345678 is the disk signature in hexadecimal, and 0 is the disk number that you replaced (which was obtained from the previous step):
dumpcfg.exe -s 12345678 0For more information about using Dumpcfg.exe, type
dumpcfg /? at the command prompt.
- Set the Cluster service back to Automatic, and set the Cluster Disk device back to System on the node. Start the Cluster Disk device, and then start the Cluster service.
- Open Cluster Administrator, and then bring the disk online.
- Turn on all other nodes, one at a time, and then test failover.
Malfunctioning multi-path software is a common cause for disk signatures to change. For more information about malfunctioning multi-path software in Windows 2000 clusters, please contact Microsoft support to obtain the hotfix that is described in the following Microsoft Knowledge Base article:
Article ID: 280425 - Last Review: Jan 7, 2008 - Revision: 1