Consider the following scenario:
- You have a Microsoft Windows Server 2003-based server cluster that uses shared storage. The shared storage is based on a storage area network (SAN) or on a storage server to which you connect by using iSCSI.
- You have more than one cluster node configured.
- You create a new logical unit number (LUN) on the SAN and then make that LUN available to a cluster node.
In this scenario, the LUN appears in the Disk Management tool on the particular cluster node as expected. However, after you create a partition, format the partition, and then assign a drive letter to that volume, you experience the following behavior:
- When you start Registry Editor on the cluster node, the disk signature of the new disk is displayed under the following registry subkey as expected:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk\Parameters\Signatures
- When you start the Cluster Administrator tool on the cluster node, and then you try to add a new Physical Disk Resource object, the disk does not appear in the Disk list.