Greetings all,
I started with a 2-node Windows 2012 failover cluster consisting of node1 and node2. To migrate to Windows Server 2012 R2 I created a node3 and installed it as a single node failover cluster. I used copy roles to migrate some VMs and their corresponding CSVs to the new cluster and things work great. Next I moved all remaining VMs to node1 on the original cluster and evicted node2 from the original cluster. So far so good. I then installed a clean copy of Server 2012 R2 onto node2 and attempted to add it to the new cluster and that's when I ran into trouble. It seems as though my shared storage on a Dell MD3000 (I know not supported) is not being seen correctly as the following is what I get when validating storage:
NODE2.adataconcepts.local
Row Disk Number Disk Signature VPD Page 83h Identifier VPD Serial Number Model Bus Type Stack Type SCSI Address Adapter Eligible for Validation Disk Characteristics
0 0 2b4cd3d6 19EBF3B700000000001517FFFF0AEB84 BOOT Intel Raid 1 Volume RAID Stor Port 1:0:1:0 Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller False Disk is a boot volume. Disk is a system volume. Disk is used for paging files. Disk
is used for memory dump files. Disk bus type does not support clustering. Disk is on the system bus. Disk partition style is MBR. Disk type is BASIC.
1 1 e4f31a08 60019B9000B68362000064BD5387F98E 71K002P DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:15:0 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath I/O (MPIO).
2 2 5be62253 60019B9000B683620000638651D2EB2D 71K002P DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:15:6 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath I/O (MPIO).
3 3 5be62245 60019B9000B6933F00000B9351D2E686 71K002P DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:15:7 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath I/O (MPIO).
4 4 c1100e74 60019B9000B6933F00000BE05363B77F 71K002P DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:15:11 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath I/O (MPIO).
5 5 6420dd00 60019B9000B68362000064395363C60A 71K002P DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:15:12 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath I/O (MPIO).
6 6 2cf2c0bc 60019B9000B6933F00000BFF536C698E 71K002P DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:15:13 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath I/O (MPIO).
NODE3.adataconcepts.local
Row Disk Number Disk Signature VPD Page 83h Identifier VPD Serial Number Model Bus Type Stack Type SCSI Address Adapter Eligible for Validation Disk Characteristics
0 0 eb58d775 759EAC7A01000000001517FFFF0AEB84 Boot Intel Raid 1 Volume RAID Stor Port 1:0:1:0 Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller False Disk is a boot volume. Disk is a system volume. Disk is used for paging files. Disk
is used for memory dump files. Disk bus type does not support clustering. Disk is on the system bus. Disk partition style is MBR. Disk type is BASIC.
1 1 e4f31a08 60019B9000B68362000064BD5387F98E 71K003O DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:2:0 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath
I/O (MPIO).
2 2 5be62253 60019B9000B683620000638651D2EB2D 71K003O DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:2:6 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath
I/O (MPIO).
3 3 5be62245 60019B9000B6933F00000B9351D2E686 71K003O DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:2:7 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath
I/O (MPIO).
4 4 c1100e74 60019B9000B6933F00000BE05363B77F 71K003O DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:2:11 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath
I/O (MPIO).
5 5 6420dd00 60019B9000B68362000064395363C60A 71K003O DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:2:12 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath
I/O (MPIO).
6 6 2cf2c0bc 60019B9000B6933F00000BFF536C698E 71K003O DELL MD3000 Multi-Path Disk Device SAS Stor Port 0:0:2:13 Microsoft Multi-Path Bus Driver True Disk is already clustered. Disk partition style is MBR. Disk type is BASIC. Disk uses Microsoft Multipath
I/O (MPIO).
List Disks To Be Validated
Description: List disks that will be validated for cluster compatibility.
Start: 5/30/2014 5:07:08 PM.
Physical disk e4f31a08 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE2.adataconcepts.local
Physical disk 2cf2c0bc is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE3.adataconcepts.local
Physical disk 6420dd00 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE3.adataconcepts.local
Physical disk c1100e74 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE3.adataconcepts.local
Physical disk 5be62245 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE3.adataconcepts.local
Physical disk 5be62253 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE3.adataconcepts.local
Physical disk e4f31a08 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE3.adataconcepts.local
Physical disk 2cf2c0bc is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE2.adataconcepts.local
Physical disk 6420dd00 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE2.adataconcepts.local
Physical disk c1100e74 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE2.adataconcepts.local
Physical disk 5be62245 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE2.adataconcepts.local
Physical disk 5be62253 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: NODE2.adataconcepts.local
No disks were found on which to perform cluster validation tests. To correct this, review the following possible causes:
* The disks are already clustered and currently Online in the cluster. When testing a working cluster, ensure that the disks that you want to test are Offline in the cluster.
* The disks are unsuitable for clustering. Boot volumes, system volumes, disks used for paging or dump files, etc., are examples of disks unsuitable for clustering.
* Review the "List Disks" test. Ensure that the disks you want to test are unmasked, that is, your masking or zoning does not prevent access to the disks. If the disks seem to be unmasked or zoned correctly but could not be tested, try restarting
the servers before running the validation tests again.
* The cluster does not use shared storage. A cluster must use a hardware solution based either on shared storage or on replication between nodes. If your solution is based on replication between nodes, you do not need to rerun Storage tests. Instead, work with
the provider of your replication solution to ensure that replicated copies of the cluster configuration database can be maintained across the nodes.
* The disks are Online in the cluster and are in maintenance mode.
No disks were found on which to perform cluster validation tests.
Can anyone shed some light on why even though the disk signatures are the same on both nodes the two nodes don't seem to acknowledge that they are in fact looking at the same disks? Any help greatly appreciated!
Regards,
scott
Scott