ESXi precheck fails with an error that reads "Directory /locker on host does not support the upgrade for resource, Please check"

Products

• VMware Cloud Foundation

Issue/Introduction

This article provides steps to validate the corresponding log entries to validate the issue and take necessary action in addressing the issue.

Log snippets in /var/log/vmware/vcf/lcm/lcm-debug.log reports an error similar to;

YYYY-MM-DDTHH:MIN:SEC ERROR [vcf_lcm,3e####,precheck_id=ab##-###-##bf,resourceType=ESX,resource_id=18##-###-##31] [c.v.e.s.l.p.impl.esx.EsxUtils,Precheck-97] ERROR occurred fetching the available disk space for the directory: /locker
java.lang.NumberFormatException: For input string: "Available.

By validating the available space using the command df /locker in ESXi host, the output shows following error:

# df /locker
Unable to statvfs(/locker): 5
Filesystem Bytes Used Available Use% Mounted on

Running 'df -h' command, indicates that an NFS volume of 0 bytes is present on the host

Environment

VMware Cloud Foundation 4.x

VMware Cloud Foundation 5.x

Cause

This issue can be caused by an inaccessible datastore on the host

Resolution

Please note that the inaccessible volume needs to be unmounted from all hosts (not just the host referenced in the initial error). Please follow the instructions mentioned in Broadcom article Detach a LUN device from ESXi hosts

• Once unmounted, re-run the df/locker command in ESXi host. The statsvfs error should be cleared and the command should return valid information as below:

# df /locker
Filesystem Bytes Used Available Use% Mounted on
vfat ## ## ## 69% /vmfs/volumes/5e##-###-##e4

• Re-run the precheck from SDDC and the locker-space precheck should now succeed.

Additional Information

If the issue persists, please additional articles referenced below;

How to update the SSH host keys on the SDDC Manager 

SDDC Manager Precheck fails with error - ESXi Temporary Directory Exist