Troubleshooting Insufficient Disk Space During VCSA Deployment or Upgrade
search cancel

Troubleshooting Insufficient Disk Space During VCSA Deployment or Upgrade

book

Article ID: 369947

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

Deployment or upgrade of the VMware vCenter Server Appliance (VCSA) fails at Stage 1 with the error: "Insufficient disk space on datastore" or "Error creating disk Out of resources".

Symptoms

  • The installer displays: "Insufficient disk space. Minimum required: 25GB".
  • VCSA installer log files (located at C:\Users\username\AppData\Local\Temp\vcsaUiInstaller) contain entries similar to:

    warn: checkDiskspace:[xlarge-xlstorage]: required diskSpace > providedDiskspace: 5818 : 4643
    Error creating disk Out of resources

Environment

  • VMware vCenter Server Appliance 7.0, 8.0
  • VMware vSphere ESXi 7.0, 8.0
  • Local VMFS Datastores
  • vSAN Datastores

Cause

The target datastore lacks sufficient free physical space to accommodate the selected deployment size. This commonly occurs if the VMFS datastore was created with incorrect partition sizing, or if the provisioned space (including vSAN FTT components) exceeds the available datastore capacity.

Resolution

  1. Verify datastore capacity:
    • Check the target datastore capacity in the host client to ensure it meets the minimum 25GB requirement.
    • Verify that the VMFS partition size matches the physical disk capacity.
  2. Adjust deployment configuration:
    • If the datastore is full, delete unused files or increase the datastore capacity.
    • If the current datastore is insufficient, select a different target datastore with adequate free space.
    • For upgrade scenarios, choose a "Small" or "Medium" deployment size if appropriate to the source environment, matching the source configuration.
  3. Verify resources:
    • If the issue persists, ensure the ESXi host has sufficient resources to support the deployment.

For assistance with downloading specific releases, see .

If the issue remains unresolved, contact Broadcom Support: