VMware {code} Community
kin0kin
Contributor
Contributor
Jump to solution

[HELP] VMs disappeared after host reboot - ESXI 5.5, Vcenter Server in same host

I rebooted the ESXI using classic Vsphere Client. Now all the Vms have disappeared. I tried connecting with both Vsphere Client and Workstation and the list is empty. I cannot access the Vcenter server since it is a Vm that resides in the host.

The datastore is a local disk. The datastore is still there and the amount of disk space used is correct. I cannot see any Vms in inventory. I re-installed ESXI 5.5, refreshed datastore and what not, there's nothing there. I'm freaking out and don't know what to do. :smileyshocked:

EDIT: I am able to browse to the datastore manually by creating new virtual machine and selecting existing virtual machine following this guide but I'm not sure what is the reason the files would be missing/corrupted

http://techhead.co/vmware-esx-how-to-easily-recreate-a-missing-or-corrupt-vmx-file/

1 Solution

Accepted Solutions
abhilashhb
VMware Employee
VMware Employee
Jump to solution

When you browse the datastore can you see the VM's and their folders?

If you see the VM's folders you can open the folder, Right-click on the .vmx file and select Add to inventory. that will get your VM back in the inventory.

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

View solution in original post

3 Replies
abhilashhb
VMware Employee
VMware Employee
Jump to solution

When you browse the datastore can you see the VM's and their folders?

If you see the VM's folders you can open the folder, Right-click on the .vmx file and select Add to inventory. that will get your VM back in the inventory.

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

kin0kin
Contributor
Contributor
Jump to solution

Yes I did that and I've gotten everything back but what seems to be the problem with them going missing from a reboot? I have 16 VMs in the host and it took a long time to get it back and running.    

0 Kudos
abhilashhb
VMware Employee
VMware Employee
Jump to solution

It happens when the host loses connection to storage. I have seen this happening during upgrades.

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

0 Kudos