VM cannot power on - Cannot open disk

[godace89]

Power On virtual machine:Cannot open the disk '/vmfs/volumes/5088ea80-94ead5a4-d619-0026b9fc73e8/KLM1MES01S210/KLM1MES01S210-000001.vmdk' or one of the snapshot disks it depends on.

See the error stack for details on the cause of this problem.

Time: 10/6/2014 3:47:24 PM

Target: KLM1MES01S210

vCenter Server: klm1esx01s502.FS.LOCAL

Error Stack

An error was received from the ESX host while powering on VM KLM1MES01S210.

Cannot open the disk '/vmfs/volumes/5088ea80-94ead5a4-d619-0026b9fc73e8/KLM1MES01S210/KLM1MES01S210-000001.vmdk' or one of the snapshot disks it depends on.

0 (Invalid argument)

anyone experiencing this issue before? I did removed all snapshot files but it still unable to power on. Any ideas?

[Praveenmna]

Can you try to vMotion the VM to other hosts in the cluster and then power ON.

[vThinkBeyondVM]

It may resolve your issue::::Refer :http://ardamis.com/2009/11/20/vmware-cannot-open-the-disk-xxxxxx-vmdk-or-one-of-the-snapshot-disks-i...

[a_p_]

Please download the virtual machine's vmware.log from the datastore and attach it to a reply post.

In addition to the log file, post a schreenshot of the Datastore Browser which shows all the VM's files with their sizes and time stamps.

André

[godace89]

tried but still failed

[godace89]

Here you go.

[godace89]

Datastore files

[a_p_]

>>> I did removed all snapshot files ...

How exactly did you remove the snapshot files?

According to the log file the VM has a snapshot .vmdk file, which however - according to the screenshot - doesn't exist (anymore)!?

André

[godace89]

I'm creating a new snapshot from the vSphere GUI and choosing delete all option upon completed the creation process. But from the files that stated on the datastore, i couldn't locate the snapshot anymore...

[a_p_]

That's strange. Can you confirm that the vmware.log file has a current time stamp, i.e. a new vmware.log file is created when you try to start the VM?

What you might try to do is to manually edit the VM's .vmx file from the command line (replace "KLM1MES01S210-000001.vmdk" with "KLM1MES01S210.vmdk"), reload this single VM (see http://kb.vmware.com/kb/1026043), create a new temporary snapshot to be able to revert to the current state, and then power on the VM. If the VM contains all of your latest changes/data then you may delete the temporary snapshot again.

André

[Sreejesh_D]

if you are not bothered about the snapshot, I would recommend to edit the vmx file to point to parent vmdk instead of snapshot.

SSH to the host and go to the VM folder.

Open the vmx file in VI editor.

Search and replace the snapshot vmdk with the parent vmdk.  The outpu will look like following. Then try to power on.

scsi0:0.fileName = KLM1MES01S210.vmdk