moberle
Contributor
Contributor

Locked VMDK file after VMotion stalled the VCenter

Jump to solution

I vmotioned a VM and it hung up the the VCenter Server Service. I had to restart the service.

When the service came back it showed the VM as running but using no resources and all of the controls greyed out

I removed the Host from the VCenter and added it back in to remove the orphaned VM in the VCenter.

I created a new VM with the same name and selected use an existing file and selected the the file from the old VM.

When I started the VM I got the following message "Unable to access a file since it is locked"

I had the same problem with this same VM 6 months ago, and I fixed it using vmkfstools -R or -L. (I did not write down what I had done.)

I have tried both the -L and -R params to no effect.

The -L lunreset appears to work but the file remains locked.

The -R responds with a message saying the Device or resource busy.

Can anyone help me with some precise intructions on how to unlock these files. (vmware.log, xxx.NVRAM, xxxx.flat.VMDK etc)

As usual points will be award to those that help

Thanks in advance for any help anyone can give me.

0 Kudos
1 Solution

Accepted Solutions
BryanMcC
Expert
Expert

It didnt find anything.. That is the PID of your grep command.

Try expanding your Service Console and runnign ps -ef|grep vmx

Look for anything with your VM inquestions name.... The PID is the first number in your posts case 6332.

If you dont find anything.... VMotion all other VMs and reboot.



Help me help you by scoring points.

Help me help you by scoring points.

View solution in original post

0 Kudos
4 Replies
Rajeev_S
Expert
Expert

try ps -ef | grep -i <vmname>

kill -9 <pid>

try powering on your vm after that.

Hope this helps

moberle
Contributor
Contributor

Ok which number is the pid or are both of them

# ps -ef | grep -i WEBDMZ-NRT-VNAV

root 6332 6290 0 14:22 pts/0 00:00:00 grep -i WEBDMZ-NRT-VNAV

#

Or didnt it find anything at all

0 Kudos
BryanMcC
Expert
Expert

It didnt find anything.. That is the PID of your grep command.

Try expanding your Service Console and runnign ps -ef|grep vmx

Look for anything with your VM inquestions name.... The PID is the first number in your posts case 6332.

If you dont find anything.... VMotion all other VMs and reboot.



Help me help you by scoring points.

Help me help you by scoring points.

View solution in original post

0 Kudos
moberle
Contributor
Contributor

That worked TY

0 Kudos