Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

Cannot add Hyper-V node to cluster because of VMware lun

$
0
0

I might be wrong about this, but bear with me and see if you have any different thoughts that might shed some light on this.

I've reached capacity with my current Hyper-V hosts (ram/cpu) and need to add more Hosts.  However when I try to add a host (either in failover manager or VMM) the Failover Cluster Validation fails with the following error:

"Failed to find or allocate arbitration sectors for physical disk {e4d33605-a63a-4848-Disk ID...} from node HVH-1.htb.org.uk. These sectors are used to test reads and writes to the disk. On a GPT disk, these sectors are located within the Cluster Metadata Partition, and this partition may need to be created from the Microsoft Reserved Partition so that the storage will validate. Please ensure that all GPT disks have a Microsoft Reserved Partition (MSR) present. Error: 0x80070022."

After looking into the report and identifying the disk in Disk Management it is a LUN on my iSCSI storage that is for VWMare.  Since iSCSI doesn't seem to do the same security (zoning) as FibreChannel all my LUNs are presented to the hosts.  VMware is smart enough to recognize what LUNs it has the ability to use, MS not so much...

Disk Management shows it as an Offline disk with a Healthy (Primary Partition) with no filesystem.  Hyper-V is not using it, but if I try to "Add Disk" from inside Failover Cluster Manager, it does give me the option of adding it.  Is there a way to hide this drive from Hyper-V or even the OS to test if this is my problem?  Since Microsoft hasn't figured out how to omit disks that are not part of the Hyper-V cluster in its Cluster Validation test, this seems like my only option.


Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>