Skip to main content

Unable to take snapshot & consolidate the VM



Recently I got an issue where customer was not able to take snapshot also unable to consolidate the snapshot.

While verifying the snapshot status of VM in snapshot manager its shows no snapshot available. However, while accessing the datastore I found 30 snapshot on both the hdd attached to the VM.

I tried to consolidate the VM from snapshot manager & from ESXi cli using below command where VIMID is the VM ID which you can get from vim-cmd vmsvc/getallvms(To get vm id) command
vim-cmd vmsvc/snapshot.removeall VMID ( To consolidate the snapshot) but it again failed by giving failed status.

Next, I tried to find CID and PID status of both the HDD connected to virtual machine.  You can use below command followed the path of virtual machine. (i.e /vmfs/volumes/vmname)
for i in `ls -l *.vmdk  | grep -v delta | grep -v ctk | grep -v flat | awk '{print $
$i; done

As mentioned, there are 30 delta files exist on both the HDD and one first HDD I find CID and PID mismatch where delta disk 25-30 where having 0000 CID and PID and all later HDD was having consistent details.

You can verify the disk consistency by using below command.
Vmkfstools –D /vmfs/volumes/datastore/vmname/disk.vmdk

While verifying the disk consistency I found disk to be inconsistent. Now whats next ??

Now, I decided to check the vmdk consistency all from 30 to 1. Later I got I found disk consistency on vmdk 24. I decided to map the vmdk24 to the VM which is the first HDD and try to poweron, but unable to poweron.

So, Finally I decided to clone vmdk24 of first hdd of VM where i foud the disk consistent so that all the metadata get saturated and consolidated to base disk.

You can clone the disk by using command vmkfstools –I (source disk) (destination disk)
Now, I after cloing the disk tried to add the clone HDD to the VM and try to poweron. Fortunatly it works. I’m able to poweron the VM also able to take the snapshot & consolidate.

Happy Sharing… J


Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl