Shulou(Shulou.com)05/31 Report--

This article shows you how to restore the cluster service on the server cluster, the content is concise and easy to understand, it will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

Problem description:

The physical disk resource may not come online, or the cluster service may not start. Generate the following message in the system event log:

Event ID: 1034

Source: ClusDisk

Description: the disk DriveLetter associated with the cluster disk resource cannot be found. Expected signature is the DiskSignature of the disk

To resolve this problem, follow these steps:

Make sure that the disk is interconnected through the actual public sharing and that the operating system is visible. To do this: if the count does not match, the disk is not accessible to the node. Resolve your storage solution to ensure that the disk is accessible and installable by the operating system. When running a normal storage solution, you can rescan the bus by right-clicking the device manager disk.

If the count does not automatically match, and the cluster service is up and running by moving all disk resources (groups of host resources) to a single node, if possible reduced complexity. If the Custer service is failing, shut down all nodes and restart one node.

Click start, click run, type CompMgmt.msc, and then click OK.

In system tools, device Manager, computer Management, look under the hard disk, you can view all the logical disks displayed by this node.

All nodes in the $cluster can see that the same number of disk drives are managed by the cluster. For example, if all 10 disks managed by the cluster are visible to all nodes in the cluster. If you know the disks of the target ID and LUN, you can verify them by clicking the properties of each disk.

If a disk signature occurs, the automatic change is written back to disk using the signature expected by Dumpcfg.exe.

The signature through the dumpcfg disk as an enumeration should match the list derived from the following registry subkeys:

HKLM/System/CurrentControlSet/Services/Clusdisk/Parameters

This information is used by Clusdisk to bind to disks managed by the cluster service.

If the signatures in the list do not match the list of registry subkeys, you must correctly identify the disk changes that have been signed by them, and they are reset to the expected signature. To do this:

Power off all but one node.

Document disk number: compares the information of the event ID 1034 messages displayed in the description section.

For example: the disk associated with the cluster disk resource disk Q:\. The disk label cannot be changed even if the signature. The disk label will help you correctly identify the disk of the problem. Once the disk has been correctly identified and its signature can be checked again to verify the mismatch.

Open computer Management, double-click Storage, and then click disk Management.

"in logical disk Manager, note the disk number and the label associated with the failed disk." This information is the partition information on the left. For example: disk 0.

If you prefer the DiskMgmt.msc disk will be set to manual, cluster service and cluster disk devices, and then restart (all other nodes should remain shut down) node. To do this, follow these steps.

Note: this step may not be required.

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 View menu.

View the section that is not a plug driver in the right pane, and double-click the Clusdisk driver.

On the driver tab, the startup type option changes from the system to disabled.

Double-click Services and applications in the left pane, and then click Services.

Double-click the cluster service in the right pane, and then click disable in the Startup Type box.

Restart the node and repeat step 2, if necessary.

The cluster service needs to write a signature to disk:

Obtain the required signature from the description section of the event ID 1034 error message. For example, the expected signature of the disk is 12345678.

Copy from the DumpCfg.exe of the Windows 2000 Resource Kit to the local node. Type dumpcfg.exe at the command prompt. The disk number and the signatures of all available disks are displayed under the disks section. Verification with the cluster service requires an actual disk signature.

Write to disk using the following command, where 12345678 is in hexadecimal, disk signature, and 0 is the expected signature of the disk number you replaced (this gets the previous step):

Dumpcfg.exe-s12345678 0

Type dumpcfg / for more information about using Dumpcfg.exe? At the command prompt.

Set the cluster service back to automatic and back to the cluster disk device of the system on the node. Start the cluster disk device, and then start the cluster service.

Turn on cluster management and bring the disk online.

Open all other nodes, once, and test the failover.

The above is how to restore the cluster service on the server cluster. Have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.