VMs showing up as unknown (invalid)

[wstclair41]

I have an ESXi 5 update one environment I had issues with my storage which is NetApp using NFS datastores. I resolved my storage issues got the datastores backon online and added back to my ESXi host. Now some of my VMs particuraly my vCenter server and SQL server are showing up as Unknown (invalid). I tried removing them from inventory then browsing the data store and adding them back to inventory and they still show up as Unknown.

I also tried creating a new Custom VM then browsing to the vmdk file to add to the new VM but when I browse the datastore the vmdk's do not show up (althougth I can browse the datastore from the Configuration tab and see the vmdk).

Does anyone have any idea on what the issue may be and maybe point me in the right direction to solve this?

Thanks

[sparrowangelste]

have you tried to restart the management agents on your esxi host?

[aravinds3107]

Did you already check KB1003742

[wstclair41]

I did reboot the management agents.

[wstclair41]

In my case my SQL and vCenter Server were both virtual. So when we lost storage we lost everything.

[hmus]

I think the vmdk files are locked by the host. check out the below one

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051

[Sawkat]

Here is what I did once:

i opened the folder in the datastore, deleted all files (.log, .nvram, etc ect) I kept only the .vmdk, .vmx,

edit the .vmx file and remove all references pointing towards deleted files..

you may also, download all the .vmx and .vmdk files. clear the folder completely from the datastore and reupload them or use vmware converter to shoot them back again on the host...

remember that sometimes direct solutions do not exist, you need to have a get around... think out of the box always

[continuum]

Tips that include the advice "delete all logs" should be strictly forbidden here.

Never even think of doing that before you have not downloaded them or otherwise backed them up.