Article ID: 263590
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0 Enterprise Edition
This article was previously published under Q263590
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
This article discusses how to extend the disk space of a hardware-defined disk with Windows Clustering. If you add additional space to an existing cluster server disk at the hardware level, you must perform additional steps to ensure that the computer system recognizes this additional disk space.
For additional information about Windows 2000 Clustering, click the article number below to view the article in the Microsoft Knowledge Base:
304736 How to Extend the Partition of a Cluster Shared Disk
RESOLUTION
To add disk space to an existing cluster server disk at the hardware level, use either of the following methods.
Method 1: Create a New Partition on the Current Physical Disk
For additional information about how to create a new partition on the current physical disk, click the article number below to view the article in the Microsoft Knowledge Base:
175278 How to Install Additional Drives on the Shared SCSI Bus
Method 2: Delete the Current Partition and Create a New Partition
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
You can delete the existing partition and create a new partition that includes all available disk space. To do this, follow these steps:
- On node 2, change the startup value to Manual for the following items:
- Clusdisk (located in the Devices tool in Control Panel)
- Cluster Service (located in the Services tool in Control Panel)
- Restart node 2.
- When the OS Loader Boot menu is displayed, press SPACEBAR. This procedure prevents Microsoft Windows NT from loading.
NOTE: This procedure is necessary to maintain termination on the shared SCSI bus on some hardware configurations. - On node 1, change the startup value to Manual for the following items:
- Clusdisk (located in the Devices tool in Control Panel)
- Cluster Service (located in the Services tool in Control Panel)
NOTE: Do not attempt to stop the Clusdisk resource. If you do, you may receive the following error message:
- Restart node 1.IMPORTANT: By this step, you must have taken the necessary steps, as outlined by your hardware vendor, to extend the existing disk space at the hardware level.
- Back up all of the information on the shared disk that is to extended. You must verify that the backup is complete and accurate.
CAUTION: After you extend the volume, all data is destroyed and you need a complete backup to restore any data. - Delete all the partitions on the shared disk to be extended.
- Create a new partition that uses up all of the free space on the shared disk, format the disk with the NTFS file system, and then give the disk the same drive letter that the previous disk had.
- Restore all data to the shared disk.
- After you verify that the data is correctly restored, run the Regedt32.exe file.
- Locate HKey_Local_Machine. On the drop-down Registry menu, click load hive. On the Open dialog box, browse to \%System_root%\Cluster, and then click the Clusdb file. Open the file and when it prompts you for a name for the registry key, name it "cluster" (without the quotes).
- Expand the cluster hive, locate and expand the Resources key. A list of resources with global universal identification (GUID) is displayed. Click the first GUID. On the right-hand side of the screen is information about this GUID. Continue to click the GUIDs until you find the one for the disk that you just extended (the "type" shows the physical disk and the "name" tells you what disk you are looking at).
- When you locate the disk that you extended, expand the GUID key for that disk. A Parameters key is located under the GUID key. When you click the Parameters key, the right side of the screen has two values: a Diskinfo key and a Signature key. Click the Diskinfo key on the right side, and then delete it.
IMPORTANT: Do not delete the Signature key. - Go back to the root of the cluster hive and click the drop-down Registry menu, and then click unload hive. It may tell you that the key and all of its subkeys are to be removed. This message is normal behavior.
- Close the Regedt32.exe file.
Locate CLUSDB in the c:\winnt\cluster directory and copy to a floppy or other location available to both nodes (not the shared disks). - Start the Explorer.exe program and browse to your Quorum drive. Locate the MSCS folder on your quorum drive. There may be one or more files in the MSCS directory named Chk***.tmp. Rename all the .tmp files in the MSCS folder (you can delete them if you want to, but it is safer to rename them).
- Manually start the cluster disk device and reset its startup value back to "system".
- Manually start the Cluster Service and reset its startup value to "automatic".
- Open Cluster Administrator on your computer to verify that all of the resources are online.
- Shutdown Node 1.
- Boot Node 2.
- Verify in Disk Administrator the recreated partition has the correct drive letter based on Step #8 above.
- COPY CLUSDB into the c:\winnt\cluster directory from the floppy or other location used in step 15a above.
- Change Start values back to defaults, do not start:
a. Cluster disk device - reset its startup value back to "system".
b. Cluster Service - reset its startup value to "automatic".
- Shutdown Node 2, Reboot Node1. Everything should continue to work.
- If all of the resources are online, turn on node 2.
- Fail the resource group that contains the newly extended disk back and forth between the cluster nodes to verify that it comes online on either node.
STATUS
This behavior is by design.
MORE INFORMATION
IMPORTANT: This article assumes that the disk signature has not changed. If the "container" or physical disk has been deleted and recreated it will have a new disk signature. To handle new disk signatures, follow the procedure in:
243195 Event ID 1034 for MSCS Shared Disk After Disk Replacement
Some hardware-defined disks can have their allotted space increased without the loss or the restoration of any data that already exists on the disks. When this type of disk has its allotted space increased at the hardware level, your computer's operating system shows that additional free space now exists at the end of the disk. However, your computer's operating system does not show that the existing partition on the disk has actually been extended.
One method to extend a partition is to create a software volume set made up of the previous disk space and the newly added space which ensures that you can extend the current partition to include the newly added disk space. On a Windows Clustering server, however, the preceding method is not a valid option because Windows Clustering does not support software fault tolerant sets.
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
171052 Software FT Sets Are Not Supported in Microsoft Cluster
237853 Dynamic Disk Configuration Unavailable for Server Cluster Disks
Additional query words: mscs
Keywords: kbclustering kbprb KB263590
