VMware Cloud Community
lucarobusto_arp
Enthusiast
Enthusiast
Jump to solution

VM UNACCESSIBLE but running and working

I suppose that following a Network issue, after a VMotion, 5 VM on 78 are now showing status: unaccessible.

The machine are correctly running (they are Active directory DHCP, DNS, IIS), also after host reboot, but I cannot login via VCenter remote console, since STATUS  is UNACCESSIBLE.

I cannot register them again, and I cannot delete lock files (resource busy).

I tested this from all hosts of the cluster.

Do you have any suggestion on how to access the machine from VCenter 6.7 again?

 

Thanks.

0 Kudos
1 Solution

Accepted Solutions
continuum
Immortal
Immortal
Jump to solution

Does plan A not work or do you look for a shortcut ?

- power off VMs via RDP or whatever you use instead
- unregister VM in vCenter
- use ESXi that the VMs were running on to clean up locks
- reregister VMs in vCenter

 

 


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

View solution in original post

0 Kudos
3 Replies
scott28tt
VMware Employee
VMware Employee
Jump to solution

@lucarobusto_arp 

Moderator: Moved to vSphere Discussions


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
0 Kudos
continuum
Immortal
Immortal
Jump to solution

Does plan A not work or do you look for a shortcut ?

- power off VMs via RDP or whatever you use instead
- unregister VM in vCenter
- use ESXi that the VMs were running on to clean up locks
- reregister VMs in vCenter

 

 


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
lucarobusto_arp
Enthusiast
Enthusiast
Jump to solution

It's solved.

I had to poweroff the VM.

The main issue was that the VM in the VCenter list was inaccessible, so I could not login using console, or power it off.

I could anyway login via RDP, after getting the IP on the DHCP lease.

Once powered off, I could delete from inventory, and delete the file from the file system, and restore the last night backup.

Thanks all for the support.

0 Kudos