OPERATIONAL DEFECT DATABASE
...
...
Virtual machine (VM) fails to startVM files fail to delete on datastoreVirtual desktop infrastructure (VDI) Machine BSODIn the vmkernel.log, you see entries similar to: 2017-01-30T08:13:18.238Z cpu11:1319986)FSS: 5760: Conflict between buffered and unbuffered open (file 'ctf1461-checkpoint-sesparse.vmdk'):flags 0x4008, requested flags 0x1 In the vmware.log, you see similar to: 2017-02-15T06:03:49.168Z| vmx| I125+ Power on failure messages: File system specific implementation of LookupAndOpen[file] failed 2017-02-15T06:03:49.168Z| vmx| I125+ File system specific implementation of OpenFile[file] failed 2017-02-15T06:03:49.168Z| vmx| I125+ File system specific implementation of LookupAndOpen[file] failed 2017-02-15T06:03:49.168Z| vmx| I125+ Failed to lock the file 2017-02-15T06:03:49.168Z| vmx| I125+ Cannot open the disk '/vmfs/volumes/5677c9eb-2b7c3b68-a4c2-645106ee4220/lwepc5438/lwepc5438-checkpoint.vmdk' or one of the snapshot disks it depends on. 2017-02-15T06:03:49.168Z| vmx| I125+ Module 'Disk' power on failed.
Data corruption during reclaim disk space of linked clone with sesparse vmdk.
If the problem is happening for cloned VMs, see Failed to power on cloned VM. Error: File system specific implementation of LookupAndOpen[file] failedThere is a problem related to s sesparse file corruption bug for VDI VMs in ESXi 6.0. This has been resolved for ESXi 6.0 U3a. Fore more information see release notes and you can download the ESXi image here. For more information on the sesparse corruption bug affecting some versions of the ESXi OS, see Virtual Machines running on an SEsparse snapshot may report guest data inconsistencies
To workaround this issue for VDI VMs in ESXi 6.0, use any of the below workaroundsWorkaround 1Check and attempt to repair the disk. SSH to the ESXi host where the VM residesCheck the file location: vmkfstools -x check /vmfs/volumes/<datastorepath>/<vm name>/<vm name main base disk>.vmdk Repair the file path: vmkfstools -x repair /vmfs/volumes/<datastorepath>/<vm name>/<vm name main base disk>.vmdk Workaround 2Disable ATS heartbeat for all hosts.Refer the article for Disabling ATS heartbeat, ESXi host loses connectivity to a VMFS3 and VMFS5 datastore (2113956)Workaround 3Reclaim Disk Space in Horizon
Most other issues with the LookupandOpen[file] can be resolved by following Powering on a virtual machine fails with the error: File system specific implementation of Ioctl[file] failedVM fails to power on with Error: "File system specific implementation of LookupAndOpen [file] failed" For more information about troubleshooting VMs which won't power on:Failed to power on virtual machine
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
