A new physical disk resource does not successfully move to another cluster node on a Windows Server 2003-based server cluster

When you try to move a physical disk resource from one cluster node to another cluster node on a Microsoft Windows Server 2003-based server cluster, the move operation is unsuccessful.

When this problem occurs, information that resembles the following is logged in the %WINDIR%\Cluster.log file:

This problem occurs if the hard disk's signature is missing from the Windows registry.

When you bring a physical disk online, the following behavior occurs:

1. Windows identifies the disk by using the disk's GUID number.
2. Because the disk is a physical disk, Windows obtains the disk signature from the following registry location:
   HKEY_LOCAL_MACHINE\Cluster\Resources\<GUID>\Parameters
   Note In the Cluster.log file that appears in the "Symptoms" section, the disk signature is E8AAEC81.
3. Windows obtains the DiskName value that corresponds to the signature of the physical disk. To do this, Windows examines the following registry location:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ClusDisk\Parameters\Signature\<E8AAEC81>
   The value of the DiskName registry entry indicates the device that is being brought online. For example, the DiskName registry entry may contain a value such as \Device\Harddisk5.
4. Windows submits a request to the host bus adapter (HBA) to reserve this disk signature together with the disk number.

The log file entries that appear in the "Symptoms" section indicate that a file was not found. In this scenario, because the E8AAEC81 registry subkey is missing, Windows cannot determine which disk number to reserve. Therefore, the move operation is unsuccessful.

Method 1: Install the KB919117 hotfix

Install the hotfix that is mentioned in the Microsoft Knowledge Base article KB919117. For more information about this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

Method 2: Modify the registry

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, create the registry subkey that corresponds to the disk signature of the physical disk resource with which you experience this problem. In the Cluster.log file that appears in the "Symptoms" section, this subkey is the E8AAEC81 subkey. Then, add the following registry entry to this subkey:After you perform these actions, you can fail over the physical disk resource successfully. You do not have to restart the computer after you perform these actions.

To configure this registry entry, follow these steps:

1. Examine the Cluster.log file to determine the disk signature with which you experience this problem.
2. Click Start, click Run, type regedit, and then click OK.
3. In Registry Editor, locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk\Parameters\Signatures
4. Right-click Signatures, point to New, and then click Key.
5. Type the disk signature with which you experience the problem, and then press ENTER. For example, type E8AAEC81.
6. Right-click the new registry subkey, point to New, and then click String Value.
7. Type DiskName, and then press ENTER.
8. Right-click DiskName, and then click Modify.
9. In the Value data box, type \Device\Harddisknumber, and then click OK.
   
   In this registry entry, replace number with the correct number for the hard disk that you want to fail over.
   
   Note You can obtain this disk number by using the Disk Management tool. To do this, follow these steps:
   1. On the computer that hosts the hard disk, click Start, click Run, type diskmgmt.msc, and then click OK.
   2. In the lower pane of the Disk Management window, note the disk number that corresponds to the letter of the drive with which you experience the problem.

If you specify an incorrect disk number when you follow the steps in the "Resolution" section, information that resembles the following is logged in the Cluster.log file:In this situation, you must modify the DiskName value with the correct disk number.