Cluster failure? Wiz programs and nodes are the key

To address problems such as expanded capacity, redundancy, and load balancing, Windows Server 2003 supports adding multiple nodes to the existing Server cluster. This is indeed good news.
However, the bad message is that the program cannot proceed smoothly under complicated Storage Area Network SAN configuration. During the analysis phase, the installation wizard stops working and displays the error message: "The cluster service cannot locate the quorum disk ."
In fact, the reason why the cluster service cannot find the disk for arbitration may be an error in the installation wizard. As part of the installation, the wizard checks whether all nodes can identify disks with the same target ID and logical unit number.
In some complex SAN configurations, disks in the same group may be treated as different logical unit numbers or different target IDs, which is the problem. Even if there are no errors, the wizard identifies this as an error and stops the installation.
Note that this error occurs only when you add nodes to an existing cluster.
Based on Microsoft's opinion, you can use the wizard's advanced options and select the advanced minimal configuration to solve the problem. This will cancel the probe function, and the installation will be normal.
There are also other problems in this workspace: if there is a problem with the installation, the wizard will not be able to detect clearly, the problem may come from the online introduced disk.
To check whether the problem is related to the disk count, you can use the cluster Service Installation log, CICfgSrv. log, which records how nodes list disk information. Alternatively, you can use the Device Manager. Obtain related information from the Device Manager to Diskspropertiesgeneral and location, and you will see the logical unit number and target ID of the disk.