Upgrading the ESXi host manually via the command line fails with the error "Cannot find filesystem with path /tmp/_osdata####/locker" but path exists
search cancel

Upgrading the ESXi host manually via the command line fails with the error "Cannot find filesystem with path /tmp/_osdata####/locker" but path exists

book

Article ID: 399725

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Symptoms:
    • Get below error/messages when trying to upgrade the ESXi via "Software Profile" method: Cannot find filesystem with path /tmp/_osdata####/locker" but path exists.
    • From the esxupdate the following below are observed:
      esxupdate log:
      YYYY-MM-DDTHH:MM:SSZ esxupdate: 2276222: root: WARNING: OSdata/scratch does not exist or is not backed by disk storage, reserved VIBs will not be cached.
      esximage.ImageManager.HostSeeding.NoVibCacheError: No VIB cache location is availableTransaction: ERROR: Unexpected error when storing reserved VIBVMware_locker_tools-light_xx.x.x.xxxxxxxx-xxxxxxxx: Cannot find filesystem with path /tmp/_osdata####/locker

Environment

vSphere vCenter server 8.X

VMware ESXi host 8.X

VMware ESXi host7.X

Resolution

OR

  • Configure the boot LUN with proper SAN zoning (host HBA to storage ports) and enforce correct LUN masking on the storage array so that only the intended ESXi host can access the boot device