All vSAN objects stuck in Reduced Availability with no rebuild
search cancel

All vSAN objects stuck in Reduced Availability with no rebuild

book

Article ID: 430112

calendar_today

Updated On:

Products

VMware vSAN VMware vCenter Server

Issue/Introduction

Running the following command shows all objects stuck in a "reduced-availability-with-no-rebuild" state.

esxcli vsan debug object health summary get

Health Status Number Of Objects
--------------------------------------------------------- -----------------
remoteAccessible 0
inaccessible 0
reduced-availability-with-no-rebuild ####     <----------------All Objects In This State
reduced-availability-with-no-rebuild-delay-timer 0
reducedavailabilitywithpolicypending 0
reducedavailabilitywithpolicypendingfailed 0
reduced-availability-with-active-rebuild 0
reducedavailabilitywithpausedrebuild 0
data-move 0
nonavailability-related-reconfig 0
nonavailabilityrelatedincompliancewithpolicypending 0
nonavailabilityrelatedincompliancewithpolicypendingfailed 0
nonavailability-related-incompliance 0
nonavailabilityrelatedincompliancewithpausedrebuild 0
healthy 0

Environment

ESXi 8.0 U3

vCenter 8.0 U3

Cause

This can occur when all virtual machines have the default storage policy and one host is in maintenance mode which causes the cluster to not have enough resources to keep the objects healthy and compliant.  

esxcli vsan cluster get

Cluster Information:
   Enabled: true
   Current Local Time: 2026-02-10T19:01:05Z
   Local Node UUID: ########-####-####-####-############
   Local Node Type: NORMAL
   Local Node State: BACKUP
   Local Node Health State: HEALTHY
   Sub-Cluster Master UUID: ########-####-####-####-############
   Sub-Cluster Backup UUID: ########-####-####-####-############
   Sub-Cluster UUID: ########-####-####-####-############
   Sub-Cluster Membership Entry Revision: 2
   Sub-Cluster Member Count: 3
   Sub-Cluster Member UUIDs: ########-####-####-####-############, ########-####-####-####-############, ########-####-####-####-############
   Sub-Cluster Member HostNames: HOSTNAME1, HOSTNAME2, HOSTNAME3
   Sub-Cluster Membership UUID: ########-####-####-####-############
   Unicast Mode Enabled: true
   Maintenance Mode State: ON         <----------MAINTENANCE MODE IS ON
   Config Generation: ########-####-####-####-############ 16 2026-02-10T17:49:09.78
   Mode: REGULAR
   vSAN ESA Enabled: false

Resolution

Put host into Maintenance Mode using "No data migration".  After the host is completely in Maintenance Mode, take it back out.