Disks Are Not Detected Correctly When You Add a Disk As a Cluster Resource on a Cluster Node

This article was previously published under Q322945
This article has been archived. It is offered "as is" and will no longer be updated.
In certain situations, you may be unable to add a disk as a cluster resource to a node in a server cluster. When you try to do so, the disk is not detected correctly and it is not listed as Online in the Disk Management snap-in.
This problem may occur in situations where the physical drive number of the disk that you want to add is greater than the disk count, or if the disks are not numbered consecutively in Device Manager. The number of disks that are enumerated is based on the disk count of the node. The Clusdisk.exe program uses the IoGetConfigurationInformation routine to determine the disk count. Clusdisk.exe assumes that disks are numbered consecutively and it includes in the disk count any physical disks on the node that are currently disabled.

For example, this problem may occur in the following scenario:
  1. You have a two-node cluster (Node 1 and Node 2), where each node has two local drives that are detected in Disk Management as Disk 0 and Disk 1. All shared disks (Disk 2, Disk 3, and Disk 4) and cluster resources are located on Node 1.
  2. You disable a local physical disk on Node 2.
  3. Without restarting Node 2, you move the cluster group from Node 1 to Node 2.
In this example, the disk count is 4. Therefore, only physical drive numbers 0 to 3 are detected. Disk 4 is not added and is not listed as Online in Disk Management.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version        Size    File name   -------------------------------------------------------   25-Sep-2002  14:59  5.0.2195.6070  73,040  Clusdisk.sys

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product

Identyfikator artykułu: 322945 — ostatni przegląd: 10/24/2013 11:58:52 — zmiana: 1.7

Microsoft Windows 2000 Advanced Server

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbqfe kbbug kbfix kbwin2000presp4fix KB322945