Resolving “vSAN Disks Availability Validation Failed” During VCF 9.0 Installation
search cancel

Resolving “vSAN Disks Availability Validation Failed” During VCF 9.0 Installation

book

Article ID: 408233

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

During VMware Cloud Foundation 9.0 installation, the process may fail with the following validation error: vSAN Disk Availability (Hybrid) ! Failed

Error Seen in /var/log/vmware/vcf/domainmanager/domainmanager.log:
YYYY-MM-DDTHH:MM:SS ERROR [vcf_dm,########87f94f5e6e83############,8541] [c.v.e.s.c.c.v.esx.EsxCommandExecutor,dm-exec-35]  <esx_host_fqdn>: esxcli method vim.EsxCLI.storage.core.device.partition.list failed: Unable to find device with name vsan:<UUID>
YYYY-MM-DDTHH:MM:SS ERROR [vcf_dm,########87f94f5e6e83############,8541] [c.v.e.s.v.v.VsanDiskValidator,dm-exec-35]  Failed to validate vSAN disk availability
com.vmware.evo.sddc.common.client.vmware.esx.models.LocalizedMethodFault: Unable to find device with name vsan:<UUID>
        at jdk.internal.reflect.GeneratedConstructorAccessor493.newInstance(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
        at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
        at org.glassfish.jaxb.core.v2.ClassFactory.create0(ClassFactory.java:104)
        at org.glassfish.jaxb.runtime.v2.runtime.ClassBeanInfoImpl.createInstance(ClassBeanInfoImpl.java:255)
        at org.glassfish.jaxb.runtime.v2.runtime.unmarshaller.UnmarshallingContext.createInstance(UnmarshallingContext.java:655)
        at org.glassfish.jaxb.runtime.v2.runtime.unmarshaller.StructureLoader.startElement(StructureLoader.java:156)
        at org.glassfish.jaxb.runtime.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:530)
        at org.glassfish.jaxb.runtime.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:509)
        at org.glassfish.jaxb.runtime.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:137)
        at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:518)
        at java.xml/com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374)
        at java.xml/com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:613)
        at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:30
.
.
.
.
YYYY-MM-DDTHH:MM:SS DEBUG [vcf_dm,########87f94f5e6e83############,8541] [c.v.e.s.c.v.util.ResponseUtil,dm-exec-35]  Build validation response: {"errorCode":"VSAN_DISK_AVAILABILITY_VALIDATION.error","arguments":[],"context":{"severity":"ERROR","bundleName":"com.vmware.evo.sddc.common.validation.errors.messages","validation.taskId":"<task_id>"},"message":"vSAN Disks Availability Validation Failed"}

Environment

 

  • VMware Cloud Foundation 9.0

  • ESXi 9.0 hosts participating in the deployment

 

Cause

For the VCF installer to proceed, all disks used for vSAN must be valid and eligible. The error occurs in the following scenarios:

  • Stale vSAN partition exists on one or more disks.

  • The OS boot disk of the ESXi host is incorrectly marked as eligible for vSAN use.

  • One or more disks are flagged as ineligible for vSAN disk group creation.

SDDC Manager evaluates available disks and automatically selects those eligible for vSAN. If invalid partitions or incorrectly flagged disks are found, validation fails.

Resolution

Step 1: Verify Disk Eligibility

On each ESXi host, run: vdq -qH

This command lists disks and their vSAN eligibility status.

  • If the OS boot disk is marked as eligible, it must be marked as ineligible.

  • If other disks are flagged incorrectly, proceed with validation in Step 2.

Step 2: Check for Stale vSAN Partitions

  • If a disk is eligible but still failing validation, check for stale partitions:
    partedUtil getptbl /vmfs/devices/disks/<DeviceName>

  • If a stale vSAN partition exists, delete it using:
    partedUtil delete "/vmfs/devices/disks/<DeviceName>" <PartitionNumber>

    Caution:

    • Partition changes are destructive and cannot be undone.

    • Ensure no active I/O to the disk before modification.

    • Always take a backup before making changes.

    • If unsure which partitions to remove, contact Broadcom Technical Support for assistance.

Step 3: Retry VCF Installer

After correcting eligibility and removing stale partitions, rerun the installer. The validation should now succeed.

Additional Information

Powered by Wolken Software