To resolve this issue, delete the
.lck-xxxx file located in the virtual machine folder.
Caution: Ensure the vmdk files are not in use by another virtual machine before performing these steps. Removing a valid .lck can cause instability.
To delete the .lck-xxxx file:
- Ensure the virtual machine is powered off.
- Connect to the ESXi/ESX host using Secure Shell (SSH). For more information, see Connecting to an ESX host using a SSH client (1019852).
- Go to the virtual machine folder, run the command:
cd /vmfs/volumes/datastore_name/virtual_machine_folder
- List all files including the hidden files, run the command:
ls -la
- Remove the lock file, run the command:
rm .lck-xxxx
Where xxxx is a sequence of numbers. For example, lck-001455721.
Note: Ensure the virtual machine is not running.
- Power on the virtual machine.
Note: When the virtual machine is powered on, you see a new .lck-xxxx file generated in the virtual machine folder. This is expected behavior.
If this issue persists or no lock files are present to apply this resolution to, file a Support Request with VMware Support and note this KB article ID (2037507) in the problem description. For more information, see Filing a Support Request in Customer Connect (2006985).