A virtual machine (VM) fails to power on with an error indicating another task is in progress.
Symptoms:
/vmfs/volumes/<datastore_name>/<vm_folder>/vmware.log of the VM contains the following entries:DISKLIB-CTK : Could not open change tracking file "/vmfs/volumes/<datastore_name>/<vm_folder>/<vm_name>-ctk.vmdk": Change tracking invalid or disk in use.
DISKLIB-CTK : Error creating file ... 3 (The file already exists)
A snapshot remaining, but not being visible in the Snapshot Manager indicates that the request for snapshot removal was sent and received, but the snapshot consolidation did not complete successfully.
This often leaves the virtual machine in a state where it displays a "Consolidation is needed" alert.
>A lock on the VMDK files of that virtual machine can hinder the snapshot removal process. This lock is often caused by the VMDK still being attached using Virtual Appliance transport mode or the VMDKs being locked by the ESXi host.
To resolve this issue, take the following steps:
root account.# vmfsfilelockinfo -p /vmfs/volumes/<datastore_name>/<vm_folder>/<vm_name>-flat.vmdk
# cd /vmfs/volumes/<datastore_name>/<vm_folder>/
*.vmsd, *.ctk.vmdk and *.vmsn files into this temporary directory:# mkdir temp
# mv *-ctk.vmdk temp
# mv *vmsd temp
# mv *.vmsn temp
# cp vm-name.vmx vm-name.vmx.bak
<vm_name>.vmx file using the VI editor and set the following parameters to false:ctkEnabled = "false"
scsi#:#.ctkEnabled = "false"
# vim-cmd vmsvc/getallvms
# vim-cmd vmsvc/reload <vm_ID>