vCenter In-Place Update Precheck Fails to Warn About Low /storage/log Capacity.

Products

• VMware vCenter Server 8.0

Issue/Introduction

During an in-place upgrade of vCenter Server, the precheck process fails to display a warning message even if the /storage/log partition has insufficient space (less than 50 GB).
This can lead to update failures or performance issues during the migration process because the installer does not prompt the user to expand the disk before proceeding.

Environment

vCenter 8.x

Cause

The precheck validation logic lacks the specific requirement to verify if the /storage/log partition meets the minimum 50 GB threshold necessary for a successful in-place update.
As a result, the system proceeds without triggering an "insufficient disk space" notification, even when the partition size is inadequate.

Resolution

This issue is resolved in VMware vCenter 8.0 Update 3h.

Workaround:

1. Check Disk Space: Log into the vCenter Server Appliance (VCSA) via SSH or the VM console.

2. Verify Capacity: Run the command df -h to check the size and usage of the /storage/log partition.

3. Expand if Necessary: If the partition is below 50 GB, increase the size of the corresponding VMDK in the vSphere Client, then use the vcssupport or autogrow utilities within the appliance shell to extend the logical volume.

Additional Information

 

• Pre-deployment Check: Always perform a file-based backup and take a powered-off snapshot of the vCenter Server Appliance before modifying disk partitions or initiating an upgrade.

• Minimum Requirements: Ensure that other critical partitions, such as /storage/core and /storage/db, also have sufficient overhead as per the VMware Hardware Requirements guide.