Failed to open 'virtual machine disk' with flags 0xe (The parent virtual disk has been modified since the child was created)
Failed to open (The parent virtual disk has been modified since the child was created)
Failed to open 'virtual machine disk': The parent virtual disk has been modified since the child was created (18).
DISKLIB-LINK : Attach: Content ID mismatch (7b7644b2 != 4f5a6761)
DISKLIB-LINK : Attach: the capacity of each link is different (83886080 != 46399652).
Cannot open the disk '/vmfs/volumes/4a365b5d-eceda1-19-439b-000cfc0086f3/examplevm/examplevm-000001.vmdk' or one of the snapshot disks it depends on.
Reason: The parent virtual disk has been modified since the child was created.
vmx| DISKLIB-LINK : Attach: Content ID mismatch (d0fdb25b != ef4854ee).
vmx| DISKLIB-CHAIN : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm.vmdk" : failed to open (The parent virtual disk has been modified since the child was created).
vmx| DISKLIB-VMFS : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002-delta.vmdk" : closed.
vmx| DISKLIB-VMFS : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000001-delta.vmdk" : closed.
vmx| DISKLIB-VMFS : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-flat.vmdk" : closed.
vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002.vmdk' with flags 0xa (The parent virtual disk has been modified since the child was created).
vmx| DISK: Cannot open disk "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002.vmdk": The parent virtual disk has been modified since the child was created (18).
vmx| Msg_Post: Error
vmx| [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002.vmdk' or one of the snapshot disks it depends on.
vmx| [msg.disk.configureDiskError] Reason: The parent virtual disk has been modified since the child was created.----------------------------------------
vmx| Module DiskEarly power on failed.
A general system error occurred: Internal error
.Content ID mismatch
The Content ID (CID) value of a virtual machine disk descriptor file aids in the goal of ensuring content in a parent virtual disk file, such as a flat or base disk, is retained in a consistent state.
The child delta disks that derive from that base disk's snapshot contain all further writes and changes. These changes depend on the source disk to remain intact.
A virtual machine disk descriptor file details the basic geometry, format, or otherwise identification and handling for a virtual disk or virtual disk delta file. A CID resides in each virtual machine's disk descriptor file for integrity or state tracking.
Example descriptor file for a base disk:
|
Example descriptor file for a delta disk
|
Note: examplevm-000001.vmdk
refers to, and in another sense depends on, examplevm.vmdk
.
When the virtual machine references a virtual disk, it cites either the base disk's descriptor file, or a snapshot delta's descriptor file. In this example, the virtual machine configuration file, or examplevm.vmx
, refers to the delta disk descriptor file:
scsi0:0.present = "true"
scsi0:0.fileName = "examplevm-000001.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
Any time a virtual machine is powered on, the referenced base or delta disk descriptor file's CID value is changed (see CID printed in blue, above):
examplevm-000001.vmdk before power-on: |
examplevm-000001.vmdk after power-on: |
All of this details a virtual machine in good running condition. A mismatch can be found here, which prevents tasks from succeeding for this virtual machine:
examplevm.vmdk: |
examplevm-000001.vmdk: |
In effect, a CID mismatch ensures that deviance from the original disk state results in all dependent child delta content being invalidated. This protects stored data from further potential corruption.
Content ID mismatch conditions are triggered by interruptions to major virtual machine migrations such as Storage vMotion or Migration, VMware software error, or user action.
These Content IDs are only used for virtual machine disks with snapshots. For more information about snapshots, see Understanding virtual machine snapshots in VMware ESXi and ESX (342618).
Some scenarios to avoid in particular include:
When there is a CID mismatch, the virtual machine name is provided in the error message, but you must identify:
There are several methods to log into an ESX host to review content of utilized datastores, depending on the version of ESX utilized.
Notes:
https://server-ip
, is used to browse VMFS datastores and distinguish between the virtual machine descriptor files and their corresponding associated binary files. You can copy the relevant file from the Datastore Browser for editing. The edited file can be uploaded to the datastore again via the vSphere Client.After locating the virtual machine's files and directory:
vmware.log
file contains information which identifies the specific disk chain affected. Review the logs and note the location and files affected.vmx| DISKLIB-LINK : Attach: Content ID mismatch (d0fdb25b != ef4854ee).
vmx| DISKLIB-CHAIN : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm.vmdk" : failed to open (The parent virtual disk has been modified since the child was created).
vmx| DISKLIB-VMFS : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002-delta.vmdk" : closed.
vmx| DISKLIB-VMFS : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000001-delta.vmdk" : closed.
vmx| DISKLIB-VMFS : "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-flat.vmdk" : closed.
vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002.vmdk' with flags 0xa (The parent virtual disk has been modified since the child was created).
vmx| DISK: Cannot open disk "/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002.vmdk": The parent virtual disk has been modified since the child was created (18).
vmx| Msg_Post: Error
vmx| [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/4a365b5d-eceda119-439b-000cfc0086f3/examplevm/examplevm-000002.vmdk' or one of the snapshot disks it depends on.
vmx| [msg.disk.configureDiskError] Reason: The parent virtual disk has been modified since the child was created.----------------------------------------
vmx| Module DiskEarly power on failed.
examplevm-000002.vmdk
references its parent (which in itself references another parent file), one of which has been modified some time after examplevm-000002.vmdk
was created. You must take corrective measures on any of these files: examplevm.vmdk
, examplevm-000001.vmdk
, and examplevm-000002.vmdk
.examplevm.vmdk
, examplevm-000001.vmdk
, and examplevm-000002.vmdk
are required.
|
|
|
examplevm-000002.vmdk
links to examplevm-000001.vmdk
without error. However, the base disk examplevm.vmdk
has been modified, causing the error.Note: The number sequences of the VMDK files are irrelevant. For example:
File CID PID
XXX.vmdk 1 ---------
XXX-000002.vmdk 2 1
XXX-000001.vmdk 3 2
The VMDK files forms a valid chain, though the XXX-000002.vmdk file precedes the XXX-000001.vmdk file within the chain.
At this point, the problem point has been identified, the virtual machine's files have backups, and corrections must be applied.
To correct the Content ID mismatch:
Warnings:
Example descriptor file for a base disk |
Example descriptor file for delta disk
|
Example descriptor file for child delta disk
|
examplevm-000002.vmdk
as a child of examplevm-000001.vmdk
, which in turn is a child of examplevm.vmdk
. These three disk files make up a singular virtual disk from the perspective of the virtual machine and guest operating system.examplevm.vmdk
, per this example, or the examplevm-000001.vmdk
disk file. In either circumstance, the parentCID
and CID
relationship must be valid.examplevm.vmdk
can have its CID changed to 7b7644b2
, making it match examplevm-000001.vmdk
's expected parentCID
value. Alternatively, examplevm-000001.vmdk
's parentCID
value can be changed to 12a9ffab
to match examplevm.vmdk
's base disk descriptor file's CID. You may also consider creating a CID value on your own.00000000
-ffffffff
) with no delimiter characters.The corrections made to the virtual machine files are usually not immediately acknowledged in the remainder of the product. As such, subsequent power-on attempts may not succeed as yet.
To verify the CID corrections:
examplevm.vmx
), and choose Add to Inventory.
You can also verify if the CID mismatch has been corrected by running this command against the highest level snapshot .vmdk :
Note:
At this point, the virtual machine should start successfully if the changes incurred were minimal. The guest operating system can exhibit varying symptoms, depending on what occurred in the snapshot.
However, if the virtual machine is not in an acceptable state, you may be required to restore from a backup copy. If one is not available, you can consider starting the virtual machine on older disks.
Example: The virtual disk referenced for the provided example is examplevm-000002.vmdk
. If necessary, the virtual machine's configuration file can be modified to boot from examplevm-000001.vmdk
, permanently invalidating examplevm-000002.vmdk
. This may allow the guest operating system to proceed as intended, but at the cost of losing all information contained in the examplevm-000002.vmdk
delta file.
You can log into a VMware ESX or VMware Command Line Interface to edit the virtual machine's configuration file, and you can copy the file from the datastore for editing on another system using a preferred text editor.
THE CONTENT OF THIS ARTICLE IS PROVIDED "AS-IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Failed to power on virtual machine
"An error occurred while consolidating disks:" deleting one or more snapshots or consolidate disks
Recreating a missing virtual machine disk descriptor file
Understanding VM snapshots in ESXi / ESX
A virtual machine cannot boot after resizing a base virtual machine disk (VMDK) that is part of a snapshot hierarchy
Creating and managing Broadcom support cases
Troubleshooting virtual machine snapshot descriptor problems