Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

A virtual machine cannot boot after resizing a base virtual machine disk (VMDK) that is part of a snapshot hierarchy (1646892)

Details

  • A virtual machine fails to power on if you extend the base disk of a snapshot which is part of a redo hierarchy
  • You see errors in the VI client similar to:

    The parent virtual disk has been modified since the child was created
  • You see errors in the virtual machines vmware.log similar to:

    2013-02-17T17:41:58.304Z| vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/EXAMPLE-DATSTORE/EXAMPLE-VM/EXAMPLE-VM_4-000004.vmdk' with flags 0xa The capacity of the parent virtual disk and the capacity of the child disk are different (67).
    2013-02-17T17:41:58.304Z| vmx| DISK: Cannot open disk "/vmfs/volumes/EXAMPLE-DATSTORE/EXAMPLE-VM/EXAMPLE-VM_4-000004.vmdk": The capacity of the parent virtual disk and the capacity of the child disk are different (67).
    '/vmfs/volumes/EXAMPLE-DATSTORE/EXAMPLE-VM/EXAMPLE-VM_4-000004.vmdk' or one of the snapshot disks it depends on.
    2013-02-17T17:41:58.304Z| vmx| [msg.disk.configureDiskError] Reason: The capacity of the parent virtual disk and the capacity of the child disk are different.

Solution

This issue may occur if the size of the base disk does not match the logical size of the redo log.
 
To determine the original size of the base disk, look at the .vmdk file corresponding to the delta disk redo log. For example, an entry for a delta disk in the .vmdk file looks like:
RW 2048 VMFSSPARSE "foo-43489354-delta.vmdk"

Note: The disk size is expressed in number of sectors. In this example, the disk size is 2048, or 1MB.
 
The corresponding base disk descriptor file foo.vmdk looks like:
# Extent description
RW 2048 VMFS "foo-flat.vmdk"
If you extend the base disk to 2MB, the foo.vmdk file looks like:
# Extent description
RW 4096 VMFS "foo-flat.vmdk"


To reset the logical size of the base disk, replace 4096 with 2048 so that the foo.vmdk file looks like:
# Extent description
RW 2048 VMFS "foo-flat.vmdk"

Note: Additional datastore space is required to clone the disk

There are two options to fix this issue:
  1. Reset the base disk back to the original size in the disk descriptor file.
  2. Keep the new base disk size, and change ALL associated delta disk descriptor files to the new size.

    For information on how to modify a virtual machine disk descriptor file see: Editing configuration files in VMware ESXi and ESX (1017022).
Use this procedure to modify the virtual machine disk properties:
  1. Shutdown the virtual machine.
  2. Back-up each vmdk descriptor file in turn, and modify the RW value(s) as requires as detailed above. For example, base vmdk descriptor files, or all associated snapshot descriptor files.
  3. Clone the disk from the most recent snapshot to a new virtual disk.

    Note
    : Clone the disk, so that in the event of there being an issue, the original file(s) are available.

  4. Using Edit Settings, remove the existing disk from the virtual machine only (do not remove from disk), and add the new disk to virtual machine.
  5. Power on the virtual machine.
  6. When the size has been verified within the virtual machine, delete the original disk and associated snapshot files after confirming the virtual machine is running as expected.

See also:
Resolving the CID mismatch error: The parent virtual disk has been modified since the child was created (1007969)
Recreating a missing virtual machine disk (VMDK) descriptor file (1002511)

Tags

cannot-power-on power-on-fails power-on-vm vm-power-on-fails vm-snapshot

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 13 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 13 Ratings
Actions
KB: