OSDATA volume configured on an SSD device was reported as a VFFS volume prior to esxi version 8.0.1,it reports error "GetVffsInVFlashResource: VFFS volume […] does not exist
search cancel

OSDATA volume configured on an SSD device was reported as a VFFS volume prior to esxi version 8.0.1,it reports error "GetVffsInVFlashResource: VFFS volume […] does not exist

book

Article ID: 312519

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

  • OSDATA volume if configured on SSD/NVME device reported as a VFFS volume. following messages noticed in hostd.log

(Log file: /var/run/log/hostd.log)

[YYYY-MM-DDTHH:MM:SS] Er(163) Hostd[2101862]: [Originator@6876 sub=Hostsvc.VFlashManager opID=WorkQueue-########-####-####-f318 sid=5268ed5c user=dcui:hcid] GetVffsInVFlashResource: VFFS volume [########-####-############] does not exist.

[YYYY-MM-DDTHH:MM:SS] Er(163) Hostd[2101872]: [Originator@6876 sub=Hostsvc.VFlashManager opID=b5eef32e] GetVffsInVFlashResource: VFFS volume [########-####-############] does not exist.

Environment


VMware vSphere ESXi 8.0

Cause

  • Above messages generate due to stale entry in configstore, it does not impact any functionality.

  • This issue has been fixed esxi version 8.0.1 onwards where it is reported as a VMFSOS volume. However this stale configstore entry for the VFFS volume will still remain post upgrade to any newer release >= 8.0.1 from < 8.0.1

Resolution

Please refer following workaround to clean configstore entry.


Workaround:

  • Upgrade ESXi version to 8.0.1 and above, please issue following command from ESXi host command line.

    # configstorecli config current get -c esx -g services -k hostd -p plugins/hostsvc/vflash/

Confirm that the vffs_uuid is as showed up in the hostd error message.

  • After this run the below command.

# configstorecli config current set -c esx -g services -k hostd -p plugins/hostsvc/vflash/vffs_uuid -v 0

Run first command again to verify if vffs_uuid is correctly set to 0. 

Note: -p flag introduced with esxi version 8.0.1

  • If hostd logging still reports this error, proceed to perform reboot of ESXi host.

 

Additional Information