• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 16678
  • Last Modified:

Remove snapshot stuck for more than 20 hours - ESXi 5.0

Yesterday tried to remove VM snapshots on ESXi 5.0, and the process is stuck for more than 20 hours.
Running  vim-cmd vimsvc/task_list of this host it shows:
(ManagedObjectReference) [
   'vim.Task:haTask-44-vim.VirtualMachine.removeAllSnapshots-12580485'

The VM is unresponsive, no shutdown, does not even allow to rename the VM, any task gets an error "another task is already in progress", no problems manipulating with any other VMs.

I have no problem to lose this particular VM, but the host is in production cluster.

Thanks
0
Vasilax50
Asked:
Vasilax50
  • 2
  • 2
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
this is how you should proceed:-

1. Restart Network Management Agents on the Host Server, hosting the VM.
2. Restart vCenter Server Server service on the vCenter Server.

It would appear that a Task has Hung which needs clearing.

The above functions are safe, and will not affect any of the VMs running in production.

then we can proceed with the snapshot issue, if you wish.

Please see my EE Article

HOW TO: VMware Snapshots :- Be Patient
0
 
RickEpnetCommented:
I would do this only as a last resort but you can try what is outlined here but read through it all.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014165
0
 
Vasilax50Author Commented:
Looks like your, hanccocka, solution works :)
Restarted Network Management Agents on host and VCenter Service and the process gone

But now in inventory I have inaccessible virtual machine named "Unknown 37" , if I try to remove from inventory, it created another, "Unknown 38" VM
Also, I cannot delete the the old VM folder from the Datastore

Thank you
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
was this the VM that had the snapshot issue.

its looking likely that there is a lock on the VM, which is no surprise

there are two ways to get rid of locks, the short way restart the host, the long way, login via console or ssh, find the lock, using lsof, kill the process.
0
 
Vasilax50Author Commented:
Thank you !
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now