How to investigate and clean Inaccessible VSAN objects.

Products

• VMware vSAN

Issue/Introduction

ESXi host is removed from the cluster and then added back, since then the Objects reporting inaccessible.

Resolution

• We can use the vCenter UI and under vSAN skyline health for data health, we can use the button "Purge inaccessible VM Swap Objects". This option would detect all the vswp objects and give you an option to purge them. These inaccessible VM Swap Objects can be removed without risk by clicking "Purge inaccessible VM Swap Objects.

 

• Use below article and purge inaccessible object from UI > vSAN Health Service - Data Health – vSAN Object Health

• If we still have Inaccessible objects proceed further.

 

• Connect to one of the hosts in the cluster via an SSH session and run "esxcli vsan debug object list --health=inaccessible > /tmp/inaccessible_objects.txt" to generate a list of all inaccessible objects. To create a friendly easy to read list for customer review run cat /tmp/inaccessible_objects.txt  | grep "Object UUID\|Health\|Path" | awk '{printf $0}' | sed -e s"/Object UUID/\nObject UUID/g" | grep inaccessible > /tmp/debugInacc.txt
  

  Example 1: This example gives us the path of the VMDK.

  Object UUID: ####-####-####-####-############
     Version: 14
     Health: inaccessible - Lost data availability.(APD)
     Owner: hostname.localhost
     Size: 0.00 GB 
     Used: 30.78 GB
     Policy:
     Configuration:

        RAID_6
           Component: ####-####-####-####-############
             Component State: ABSENT,  Address Space(B): 64424509440 (60.00GB),  Disk UUID: ####-####-####-####-############,  Disk Name: t10.NVMe____Dell_Express_Flash_NVMe_P4510_4TB_SFF___00012FD64AE4D25C:2
             Votes: 2,  Host Name: hostname.localhost
           Component: ####-####-####-####-############
             Component State: ABSENT,  Address Space(B): 64424509440 (60.00GB),  Disk UUID: ####-####-####-####-############,  Disk Name: t10.NVMe____Dell_Express_Flash_NVMe_P4510_4TB_SFF___00012FD61DE4D25C:2
             Votes: 1,  Host Name: hostname.localhost     
             Component State: ACTIVE,  Address Space(B): 64424509440 (60.00GB),  Disk UUID: ####-####-####-####-############,  Disk Name: t10.NVMe____Dell_Express_Flash_NVMe_P4510_4TB_SFF___00012FD5C7E4D25C:2
             Votes: 1,  Capacity Used(B): 16693329920 (15.55GB),  Physical Capacity Used(B): 16525557760 (15.39GB),  Host Name: hostname.localhost

     Type: vdisk
     Path: /vmfs/volumes/vsan:####-####-####-####-############/VirtualMachine.vmdk (Missing)
     Group UUID: ####-####-####-####-############
     Directory Name: N/A

 

• Go to the VM and verify if the "VirtualMachine.vmdk" is not in use.
  • vSAN datastore > files > search for the VM > verify if the above vmdk is in use or not.

 

• Assistance on cleanup and Recovery of inaccessible objects.

  For further assistance on either cleanup of inaccessible object or possibility of object recovery (if required), please contact Broadcom Support to investigate the issue.

Additional Information

Use below article and purge inaccessible object from UI. 

vSAN Health Service - Data Health – vSAN Object Health