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

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

book

Article ID: 421612

calendar_today

Updated On:

Products

VMware vSAN VMware vSphere ESX 8.x VMware vSphere ESXi

Issue/Introduction

Placing an ESXi host with a vSAN File Service VM (FSVM) into maintenance mode triggers an "inaccessible object" alarm during the pre-check

Symptoms

  • The host successfully enters maintenance mode despite the alarm.

  • The warning specifically targets FSVM components residing on the host being evacuated.

  • Skyline Health report shows all production vSAN objects as healthy.

Warning message noticed while placing the host on maintenance mode:

  • Running esxcli vsan debug health summary get shows all vSAN objects as healthy and no inaccessible objects




Environment

VMware vSAN 8.x

VMware vSphere ESXi 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. This appliance is not protected across multiple hosts; it is configured as RAID-0 (HostLocal).

  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

It is safe to ignore this specific warning and proceed with maintenance mode. Follow these steps to ensure a safe transition:

  1. Verify that all production virtual machines (excluding FSVMs) are compliant and healthy in the vSAN Skyline Health check.

  2. Proceed with placing the host into maintenance mode despite the "inaccessible object" warning.

  3. The FSVM should be removed automatically from the inventory once the host enters maintenance mode.

  4. If the FSVM persists in the inventory after the host successfully enters maintenance mode, manually remove the stale FSVM.

  5. File Services will automatically recreate the node on a healthy host or when the original host returns from maintenance.

For further assistance, Contact Broadcom support team

Additional Information

vSAN Health Service - File Service - Infrastructure health