VMware Cloud Community
bleuze
Enthusiast
Enthusiast

VMs unrecognized after reboot

we had to shutdown our esxi 6.7 server last night and start it up this morning. When it came up, 6 of our VMs were not recognized and did not boot. I had to go into datastore browser, find the vmx file for each failed VM and select "Register". Then the VMs were recognized and I could start them. But the old "Invalid" registrations still show (see attachment)  and I want to know how to get rid of them. This is viewed in a browser connection directly to the host. The vcenter server. As the vcenter server is a VM within this host. The VMs that were not recognized are all ones that were newly created since the last time this host has been rebooted.

Another symptom  is that when connect to the vcenter server and click on the affected host,in the summary tab it shows the correct amount of storage but there is no data whatsoever for CPU or Memory. And there is a status message saying "Quick stats on ccv-vmware-stone is not up-to-date Cannot synchronize host ccv-vmware-stone" Also it shows only 2 of the 16 VMs as powered up when in reality 10 of them are powered up.

Note that we have 2 hosts connected to this vcenter server, the other one shows correctly in the vcenter display, it is only the host ccv-vmware-stone that does not synchronize. Both hosts were shutdown last night and started up this morning. Only the one host has this problem, the other one started up normally with no unrecognized VMs. I could try to remove this host from inventory then re-connect it but am not sure if I should find out how to remove the references to unrecognized VMs first.

0 Kudos
7 Replies
bleuze
Enthusiast
Enthusiast

SOLVED

to remove the unrecognized vms: Delete invalid virtual machine entry in web client

then unregister and re-register the host

0 Kudos
bleuze
Enthusiast
Enthusiast

But I would still like to know how to avoid this happening in the future. I assume the reason it happened is somehow related to the fact that we normally manage our hosts and their VMs through the direct connect esxi management webpage, not the vCenter server.  I mostly just use the vcenter only to upgrade our esxi version and to remove orphaned VMs. So I am guessinng  something gets out of sync between the esxi host and the vcenter server.  But this has never happened before. I'm not sure why it happened this time. Anyone know how to shed some light on this?

0 Kudos
vijayrana968
Virtuoso
Virtuoso

What type of datastore in use, ISCI or FC ! Usually it happens when datastore hosting VMs is unavailable. Check event on datastore for connectivity.

0 Kudos
bleuze
Enthusiast
Enthusiast

The datasatore is direct attached. All VMs on the same datastore. Only 5 of the 16 VMs were unrecognized.

I'm searching the logs top look for evidence\clues

0 Kudos
vijayrana968
Virtuoso
Virtuoso

Can you confirm if those 5 VMs were on separate datastore and other 16 on separate !

0 Kudos
bleuze
Enthusiast
Enthusiast

all on the same datastore - direct attached

0 Kudos
vijayrana968
Virtuoso
Virtuoso

you need to take a look on logs /var/log/vmkernel.log on ESXi host to find out what happened. As you said you shut down host last night, I hope all VMs were shut down gracefully.

0 Kudos