2016-07-27T13:34:33.894+09:00| vmx| I125: [msg.disklib.CID_MISMATCH] The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child
2016-07-27T13:34:33.894+09:00| vmx| I125: [msg.disk.noBackEnd] Cannot open the disk 'F:\one\one-000003.vmdk' or one of the snapshot disks it depends on.
2016-07-27T13:34:33.894+09:00| vmx| I125: [msg.moduletable.powerOnFailed] Module 'Disk' power on failed.
2016-07-27T13:34:33.894+09:00| vmx| I125: [msg.vmx.poweron.failed] Failed to start the virtual machine.
|
In the virtual machine of the Vmware, the disk is stored on local host PC as a number of seperated files numbered sequentially.
like this..
F:\one>dir | findstr one
2016-07-27 01:34 7,929,856 one-000003.vmdk
2016-07-27 11:19 8,684 one.nvram
2016-07-27 11:19 30,642,339,840 one.vmdk
2016-07-27 11:04 0 one.vmsd
2016-07-27 11:19 5,045 one.vmx
2016-07-27 11:36 <DIR> one.vmx.lck
2016-07-08 03:29 258 one.vmxf
|
A vmdk , the file extention , which means virtual disk of the VM.
As you open the last file 'one-000003.vmdk' , you can see CID and parent CID.
※ parentCID=fffffff means it is a root disk file.
In this case, CID and parentCID has exactly same value.
So, you have to fill up the value of the parentCID correctly.
If the root vmdk file is so huge size that can not open file, try to type this.
F:\one>type one.vmdk | findstr CID
CID=3c0de770
ddb.longContentID = "84db3daa23d4babb81c98b613c0de770"
FINDSTR: 26row so long.
FINDSTR: 114326row so long.
FINDSTR: 114326row so long.
FINDSTR: 114326row so long.
|
After you got a CID of root disk file, Edit parentCID value of the 'one-000003.vmdk' with given CID. then , try to power on the vm.
if it does not work, and if you don't care a losing of data, rollback the disk file to root disk file.
Open vmx file of VM and edit it . then power on.
it might be powered on... but anyone knows how much of data losing.
scsi0:0.present = "TRUE"
scsi0:0.fileName = "one.vmdk"
sata0:1.present = "TRUE"
|
No comments:
Post a Comment