Proxmox/Hyper-V/VMware

How to solve VMware workstation .lck error

One error you are bound to meet within your career as a Linux Administrator is a ”frozen” screen and it can be quite frustrating if you do not know what to do or where to look for the error logs. This Image below could be like this for a long time, not going further than this and not allowing any interaction on the machine. Lock files are created when a virtual machine is powered on. Their purpose is to prevent multiple VMware processes from accessing the same virtual machine at the same time. The existence of a lock file indicates to VMware that the associated virtual machine is powered on.

There are some circumstances in which one or more lock files exist in a virtual machine's directory even though the virtual machine is powered off. When this occurs, the only way that the virtual machine can be powered on is to manually remove the lock files.

Some of the major causes could be Acute Shortage of Space, System resource exhaustion. Other times, the virtual machine creates lock files to prevent consistency problems on the virtual disk.

One of the things you need to look for first is the iso image mirror. It is usually stored on the /Document/Virtual Machines folder if you are working with a Virtual Machine. It is always located in the same directory as the .vmdk files.

Open the folder and locate the files and folder that have .lck extensions and delete them. However, be sure these are not production processes locking the system down while they execute.

After deleting them, you will have to restart the machine. If it is hosted on a Virtual Machine, you may need to restart both the Virtual Machine and the host machine. After this, your system should start normally.

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Subscribe
Notify of
guest
1 Comment
Inline Feedbacks
View all comments
lucky
lucky
8 days ago

thanks a lot

1
0
Would love your thoughts, please comment.x
()
x