One vSAN object stuck in "Reduced availability with no rebuild" state after removing a host(s) from cluster
Article ID: 400420
Updated On:
Products
Issue/Introduction
Symptoms:
- You see one object in a "Reduced availability with no rebuild" state:
Environment
- VMware vSAN (all versions)
Cause
- The object has an invalid policy no longer supported by the current vSAN configuration. For example: if the object has a RAID 6 policy applied, but the vSAN cluster now has less than 6 hosts.
Verification:
- Login to one of the hosts in the cluster and confirm which policy the object has in the gui:
Cluster -> Monitor Tab -> vSAN -> Virtual Object -> Select the check box of the object and click View Placement Details
-OR-
From an ssh session to one of the ESXi hosts in the cluster:
# esxcli vsan debug object list --all -u <UUID>
Object UUID: ########-####-####-#############
... Policy:
... spbmProfileName: vSAN Default Storage Policy Configuration: RAID_6 Component: ######-####-####-############# Component State: ACTIVE, Address Space(B): 68451041280 (63.75GB), Disk UUID: ######-####-####-#############, Disk Name naa.##############:2 Votes: 2, Capacity Used(B): 176160768 (0.16GB), Physical Capacity Used(B): 171966464(0.16GB), Total 4K Blocks USed(B): 76054528 (0.07GB), Host Name: myvsanhost20.testlab.local Component: ######-####-####-############# Component State: ACTIVE, Address Space(B): 68451041280 (63.75GB), Disk UUID: ######-####-####-#############, Disk Name naa.##############:2 Votes: 2, Capacity Used(B): 146800640 (0.14GB), Physical Capacity Used(B): 142606336(0.13GB), Total 4K Blocks USed(B): 78524416 (0.07GB), Host Name: myvsanhost22.testlab.local Component: ######-####-####-############# Component State: ACTIVE, Address Space(B): 68451041280 (63.75GB), Disk UUID: ######-####-####-#############, Disk Name naa.##############:2 Votes: 2, Capacity Used(B): 159383552 (0.15GB), Physical Capacity Used(B): 155189248(0.14GB), Total 4K Blocks USed(B): 77770752 (0.07GB), Host Name: myvsanhost19.testlab.local Component: ######-####-####-############# Component State: ACTIVE, Address Space(B): 68451041280 (63.75GB), Disk UUID: ######-####-####-#############, Disk Name naa.##############:2 Votes: 2, Capacity Used(B): 1635777856 (0.15GB), Physical Capacity Used(B): 159383552(0.15GB), Total 4K Blocks USed(B): 80252928 (0.07GB), Host Name: myvsanhost17.testlab.local Component: ######-####-####-############# Component State: ACTIVE, Address Space(B): 68451041280 (63.75GB), Disk UUID: ######-####-####-#############, Disk Name naa.##############:2 Votes: 2, Capacity Used(B): 188743680 (0.18GB), Physical Capacity Used(B): 184549376(0.17GB), Total 4K Blocks USed(B): 80494592 (0.07GB), Host Name: myvsanhost23.testlab.local Component: ######-####-####-############# Component State: ABSENT, CSN: STALE (15795!=15855), Address Space(B): 68451041280 (63.75GB), Disk UUID: ######-####-####-#############, Disk Name naa.##############:2 Votes: 1, Host Name: None Type: vmnamespace Path: /vmfs/volumes/vsan:################-################/appvolumes (Exists) Group UUID: ########-####-####-####-################ Directory Names: appvolumes
Resolution
- If the object is an ordinary VM (or vmdk, vmnamespace or swap object related to an ordinary VM) and if the policy looks correct (e.g. the assigned policy is the vSAN Default Policy [left at the default RAID1]), try reapplying the policy: Reapply Virtual Machine Storage Policy
-OR-
Set a new policy, as needed: Change Storage Policy Assignment for Virtual Machine Files and Disks
- For assistance with non ordinary VM objects (e.g. non-local VM's, appvolumes directories, content libraries, .iso's, etc), please contact Broadcom support for assistance
Feedback
