VMware Cloud Community
continuum
Immortal
Immortal

A vmotion process died at 29 % - how to unlock the VM ?

A vmotion process died at 29 % - now I have one VM directory at location A and one at location B.
I can not start any of them as the vmdks are locked by owner 000...

How can I kill the process that locks the vmdks ?
The host that was running the VM still has a world-id for the VM but if I try to kill it - it says the process does not exist


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
4 Replies
NagangoudaPatil
Enthusiast
Enthusiast

Delete .lck files on VM and power ON.

Reply
0 Kudos
a_p_
Leadership
Leadership

So this was a vMotion with migrating host and storage!?

Restarting the Management Agents on the hosts should kill any processes which lock the files.

André

Reply
0 Kudos
admin
Immortal
Immortal

can you provide the hostd logs of source and destination ESXi host after recreating the issue

Reply
0 Kudos
continuum
Immortal
Immortal

I had to do it the hard way ...
I had to kill the management services but that was not enough.So we had to move all other VMs from that host elsewhere and reset the ESXi.
A gentle reboot was impossible


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos