vSAN File Services VM appears as Inaccessible Objects During Host Maintenance Mode Pre-Check

Products

• VMware vSAN

Issue/Introduction

Validation Steps:

• Placing an ESXi host with the File Service VM into maintenance mode triggers an inaccessible object alarm during the pre-check. However the host can enter the maintenance mode.
  
• FSVM is up and running and its files are accessible.
• All the vSAN objects shows healthy.
  
  
  
  

Environment

VMware vSAN 8.x

Cause

 The reported inaccessible objects during the vSAN maintenance mode precheck is expected behavior and are directly related to the vSAN File Service Node (FSVM) components.

1. The default vSAN storage policy for the File Service VMs (FSVMs) themselves is a specific, automatically created policy named FSVM_Profile_DO_NOT_MODIFY
2. The appliance is not protected across hosts, it is RAID-0.
3. The below output is from command /usr/lib/vmware/osfs/bin/objtool getAttr -u OBJUUID

Policy:((\"proportionalCapacity\" i0) (\"hostFailuresToTolerate\" i0) (\"affinity\" [ ########-33ab-dd64-cd83-###########]) (\"affinityMandatory\" i1) (\"spbmProfileId\" \"#######-15fa-4c0a-bb61-###########\") (\"spbmProfileGenerationNumber\" l+0) (\"migrateForDecom\" i1) (\"spbmProfileName\" \"FSVM_Profile_DO_NOT_MODIFY\") (\"locality\" \"HostLocal\"))

Resolution

As the objects are healthy according to their defined policy and the VMs are running without impact, no corrective action is necessary for the 8 reported objects
It is safe to proceed with maintenance mode, as the File Services are designed to handle this and will automatically recreate when the comes back post maintenance/reboot.