Quantcast
Channel: VMware Communities : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 180460

Unable to start VM

$
0
0

Hello

 

I have ran into a rather scary situation.  For some reasons my VM have become non responsive.  So I decided to restart it by issuing the "reset" command.  Unfortunately this resulted in the VM not being able to start up.  I tried rebooting the ESXi server and am still given the following message when attempting to start the VM.

Failed to start the virtual machine.
Module Disk power on failed. 
Cannot open the disk '/vmfs/volumes/557dc2e2-2c11eba8-1494-00259066ac58/<VM Name>/<VM Name>.vmdk' or one of the snapshot disks it depends on. 
22 (Invalid argument)

 

The screen shot looks like the image attached named "PowerOnError.jpg".

 

Even more puzzling is the ESXi shell isn't able to find the .vmx file.  Note I tried to list content of the directory it attempts to include the .vmx file but isn't able to.  In fact before the reboot it was included in the output of this command, in addition to showing something unable to stat file or something like that.  And if I tried to copy it it'd say Invalid Argument.  If I do something like 'strace cp <VM Name>.vmx <dest>' it'd show the error happened during the Linux system call 'open' operation with returned value EINVAL -1.

[root@esxi6prim:/vmfs/volumes/557dc2e2-2c11eba8-1494-00259066ac58/<VM Name>] ls -ltr
ls: ./<VM Name>.vmx: No such file or directory
total 52833280
-rw-r--r--    1 root     root             0 Oct  4  2015 <VM Name>.vmsd
-rw-r--r--    1 root     root        179092 Oct  9  2015 vmware-1.log
-rw-r--r--    1 root     root        177929 Oct 14  2015 vmware-2.log
-rw-r--r--    1 root     root     409599604 Nov 24 07:26 vmware-3.log
-rw-------    1 root     root           524 Nov 24 09:55 <VM Name>.vmdk
-rw-------    1 root     root     53687091200 Feb 17 12:52 <VM Name>-flat.vmdk
-rw-------    1 root     root          8684 Mar 28 04:42 <VM Name>.nvram
-rw-r--r--    1 root     root        270087 Mar 28 04:42 vmware.log

 

If I try to copy the directory to another location it'd say the following.  Note it says the <VM Name>-flat.vmdk can't be opened due to an Invalid argument despite it's shown as having a size of 53687091200 on the above 'ls' output? 53687091200

[root@esxi6prim:/vmfs/volumes/557dc2e2-2c11eba8-1494-00259066ac58] cp -rp '<VM Name>' '<VM Name>.orig.copi
ed.after.reboot'
cp: can't stat '<VM Name>/<VM Name>.vmx': No such file or directory
cp: can't open '<VM Name>/<VM Name>-flat.vmdk': Invalid argument

 

I'm seriously out of ideas here.  Any suggestions on how to fix this?

 

Thanks.


Viewing all articles
Browse latest Browse all 180460

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>