Microsoft KB Archive/217224

{|
 * width="100%"|

MSCS: How to Replace a Clustered Disk in Windows NT 4.0 Enterprise Edition

 * }

Q217224

-

The information in this article applies to:


 * Microsoft Windows NT Server, Enterprise Edition version 4.0

-

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SUMMARY
This article describes how to replace a clustered disk in Windows NT 4.0, Enterprise Edition.

NOTE: For information about disk replacement in Microsoft Windows 2000, refer to the following Microsoft Knowledge Base article:

"Q224075 Disk Replacement for Windows 2000 Server Cluster"

MORE INFORMATION
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

This procedure requires that Windows NT 4.0 Service Pack 4 or later be installed on the cluster server. This article is written with the assumption that you have knowledge of the following subjects or tools: disk signatures, Ftedit.exe, and Regedt32.exe. Please perform a full system backup before you attempt this procedure.

In this article, the two sample nodes are named NodeA and NodeB.

Note that this procedure is not valid for Microsoft Windows 2000 Advanced Server or Microsoft Windows 2000 Datacenter Server.


 * 1) Shut down and power off NodeB. Stop the Cluster service on NodeA.
 * 2) Start Regedt32.exe on NodeA. Open the cluster hive and locate the HKEY_LOCAL_MACHINE\Cluster\Groups key. Each group is listed by its Globally Unique Identifier (GUID). Click each GUID, and then set the PersistentState value to 0x0.
 * 3) Using the Devices tool in Control Panel, set ClusDisk to Manual. Using the Services tool in Control Panel, set the Cluster service to Manual.
 * 4) Restart the node. Use Disk Administrator to partition, format, and assign the same drive letters to the new disk.
 * 5) Use Ftedit.exe from the Windows NT Resource Kit to delete the old disk entries from the DISK key. Write down the new disk signatures for the new drive(s).
 * 6) Using Regedt32, remove the old disk signature keys from the HKEY_LOCAL_Machine\System\CurrentControlSet\Services\Clusdisk\parameters\Signatures key.
 * 7) Load the cluster hive and find each disk resource to be replaced. For each, delete the DiskInfo value. Enter the new signature value for the corresponding disk.
 * 8) Start ClusDisk by using the net start clusdisk command. Set the startup value back to System.
 * 9) Start the Cluster service with the -fixquorum switch and in Control Panel, use this parameter in the Services tool.
 * 10) Set the Startup value back to Automatic.
 * 11) Start Cluster Administrator and connect with "." Try to bring each disk resource online. It is acceptable for this not to work because this step may not succeed on some arrays until the next reboot.
 * 12) Restart the computer.
 * 13) In Cluster Administrator, bring each disk online.
 * 14) Using Regedt32.exe, set the PersistentState values from step 2 back to the original values (typically, 0x1).
 * 15) Start NodeB.
 * 16) Use Ftedit to remove old disk references (similar to step 5).
 * 17) Using Regedt32.exe, remove old disk signature keys from the HKEY_LOCAL_Machine\System\CurrentControlSet\Services\Clusdisk\parameters\Signatures key.
 * 18) Move the groups with disks, one at a time, to NodeB, testing bringing the disks online.

Windows NT Cluster relies on the disk signature to communicate properly with the drives. If the disk is replaced, that signature is lost and cannot be communicated with. If this happens, the following event is listed in Event Viewer:

Event ID: 1034

Source: ClusDisk

Description: The disk associated with cluster disk resource '%1' could not be found. The expected signature of the disk was %2.

Additional query words: mscs

Keywords : kbenv

Issue type : kbinfo

Technology : kbWinNTsearch kbWinNT400xsearch kbWinNTSsearch kbWinNTSEntSearch kbWinNTSEnt400 kbWinNTS400xsearch