asked on

Vmware esxi 5 The parent virtual disk has been modified since the child was created.

Hi Guys,

I have an urgent problem I cant seem to fix.

I have 1 physical server with fibre SAN with mutiple VM's. VM's are located on the san but snapshots go to my NAS.

I found my NAS was disconnected from my vmware datastore and none of my VM's were running.

I had to recreate the NAS datastore which gave me a new UUID which i edited in each VM's .vmx workingdir line.

Now, some of my VM's run no problem but my Domain Controller has reverted to a old snapshot back in January so none of my other servers will authenticate, i get a trust relationship error.

When I try and change the .vmx file to use the most recent version, or use snapshot manager to go to the most recent, i get this error;

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.

Please help!!!

Timbobaloba

ASKER

dc1.vmx;

.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "8"
pciBridge0.present = "true"
pciBridge4.present = "true"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "true"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "true"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "true"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "true"
hpet0.present = "true"
nvram = "DC1.nvram"
virtualHW.productCompatibility = "hosted"
powerType.powerOff = "soft"
powerType.powerOn = "hard"
powerType.suspend = "hard"
powerType.reset = "soft"
displayName = "DC1"
extendedConfigFile = "DC1.vmxf"
floppy0.present = "true"
numvcpus = "2"
cpuid.coresPerSocket = "2"
scsi0.present = "true"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsisas1068"
memsize = "8192"
scsi0:0.present = "true"
scsi0:0.fileName = "DC1.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
ide1:0.present = "true"
ide1:0.fileName = ""
ide1:0.deviceType = "atapi-cdrom"
ide1:0.startConnected = "false"
floppy0.startConnected = "false"
floppy0.fileName = ""
floppy0.clientDevice = "true"
ethernet0.present = "true"
ethernet0.virtualDev = "vmxnet3"
ethernet0.networkName = "VLAN 1"
ethernet0.addressType = "generated"
chipset.onlineStandby = "false"
disk.EnableUUID = "true"
guestOS = "windows7srv-64"
uuid.location = "56 4d b4 46 75 dd ba 57-ae c9 16 c5 1a 63 b5 51"
uuid.bios = "56 4d 94 e2 a9 aa 4e 81-5a 00 99 3c 9f f4 53 b3"
vc.uuid = "52 d6 45 e1 fe 6f 81 8c-ce d9 88 bc 13 aa e8 00"
snapshot.action = "keep"
sched.cpu.min = "0"
sched.cpu.units = "mhz"
sched.cpu.shares = "normal"
sched.mem.min = "0"
sched.mem.shares = "normal"
ethernet0.generatedAddress = "00:0c:29:f4:53:b3"
svga.vramSize = "8388608"
vmci0.id = "-1611377741"
tools.syncTime = "false"
cleanShutdown = "TRUE"
replay.supported = "FALSE"
unity.wasCapable = "TRUE"
sched.swap.derivedName = "/vmfs/volumes/4e5cdcdb-ad00a89f-db0d-00215ade566c/VM/DC1/DC1-4f91b634.vswp"
replay.filename = ""
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "160"
ethernet0.pciSlotNumber = "192"
vmci0.pciSlotNumber = "32"
scsi0.sasWWID = "50 05 05 62 a9 aa 4e 80"
ethernet0.generatedAddressOffset = "0"
hostCPUID.0 = "0000000568747541444d416369746e65"
hostCPUID.1 = "00100f230004080000802009178bfbff"
hostCPUID.80000001 = "00100f230000036f000007ffefc3fbff"
guestCPUID.0 = "0000000568747541444d416369746e65"
guestCPUID.1 = "00100f230002080080802001178bfbff"
guestCPUID.80000001 = "00100f230000036f000003e9ebc3fbff"
userCPUID.0 = "0000000568747541444d416369746e65"
userCPUID.1 = "00100f230004080080802001178bfbff"
userCPUID.80000001 = "00100f230000036f000003e9ebc3fbff"
evcCompatibilityMode = "FALSE"
vmotion.checkpointFBSize = "8388608"
checkpoint.vmState.readOnly = "FALSE"
checkpoint.vmState = ""
ide1:0.clientDevice = "true"
snapshot.redoNotWithParent = "true"
workingDir = "/vmfs/volumes/4e5cdcdb-ad00a89f-db0d-00215ade566c/VM/DC1/"
fileSearchPath = "."
sched.swap.dir = "/vmfs/volumes/4e5cdcdb-ad00a89f-db0d-00215ade566c/VM/DC1/"
1.jpg

ASKER CERTIFIED SOLUTION

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Timbobaloba

ASKER

I am still getting the error after editting the .vmdk files. here is an export;
DC1.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=a887808a
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfs"

# Extent description
RW 125829120 VMFS "DC1-flat.vmdk"

head DC1-000001.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=688f8057
parentCID=a887808a
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000001-delta.vmdk"

DC1-000002.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=491de367
parentCID=688f8057
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1-000001.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000002-delta.vmdk"

head DC1-000003.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=0c271c7f
parentCID=491de367
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1-000002.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000003-delta.vmdk"

DC1-000004.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=2545ecff
parentCID=0c271c7f
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1-000003.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000004-delta.vmdk"

DC1-000005.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=b5e784bd
parentCID=2545ecff
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1-000004.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000005-delta.vmdk"

DC1-000006.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=d93267d2
parentCID=b5e784bd
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1-000005.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000006-delta.vmdk"

DC1-000007.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=eccffe8c
parentCID=d93267d2
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1-000006.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000007-delta.vmdk"

DC1-000008.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=c058d757
parentCID=eccffe8c
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1-000007.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000008-delta.vmdk"

DC1-000009.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=47a8bbe9
parentCID=c058d757
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1-000008.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000009-delta.vmdk"

DC1-000010.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=a6ad390a
parentCID=47a8bbe9
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="DC1-000009.vmdk"
# Extent description
RW 125829120 VMFSSPARSE "DC1-000010-delta.vmdk"

Timbobaloba

ASKER

I changed the dc1.vmx file to;

scsi0:0.fileName = "DC1-000010.vmdk"

But now I am getting;

Reason: The file specified is not a virtual disk.
Cannot open the disk '/vmfs/volumes/4e5cdcdb-ad00a89f-db0d-00215ade566c/VM/DC1/DC1-000010.vmdk' or one of the snapshot disks it depends on.

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

does this file exist?

Timbobaloba

ASKER

yep.

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

is it possible this file is damaged?

Timbobaloba

ASKER

it is happening on ALL .vmdx files now, even the base file which i could boot off.

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

do you have a full backup you can restore?

is it possible just to add these members servers to the domain again?

when you state happening ON all VMDKs, what do you mean?

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

the chain looks okay.

Timbobaloba

ASKER

I don't have a copy of the vmdk file no. but don't think this is the issue as most of them are untouched and were working before i started playing with the configs of them and the vmx file.

I could rejoin to the domain but have configured the domain controller a fair bit since Jan :-(

When i edit the vmx file to boot from one of the 10 vmdk files, i get the same error;

Reason: The file specified is not a virtual disk.
Cannot open the disk '/vmfs/volumes/4e5cdcdb-ad00a89f-db0d-00215ade566c/VM/DC1/DC1-000010.vmdk' or one of the snapshot disks it depends on

I can get the DC1 to boot again if i remove from inventory, then create a new VM from existing virtual disk.....

Timbobaloba

ASKER

oh no!

When I was editing my vmdk files, i've overwritten them istead of edited, so I have;

version=1
encoding="UTF-8"
CID=d13ab24a
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfs"

# Extent description
RW 306184192 VMFS "Server100-flat.vmdk"

When I should have;

version=1
encoding="UTF-8"
CID=d13ab24a
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfs"

# Extent description
RW 306184192 VMFS "Server100-flat.vmdk"

# The Disk Data Base
#DDB

ddb.virtualHWVersion = "8"
ddb.longContentID = "3eaddbf7982fd47f8ce1e8fbd13ab24a"
ddb.uuid = "60 00 C2 9d 71 6a fc 09-dd d1 27 05 23 c0 bd 3d"
ddb.geometry.cylinders = "19059"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"
ddb.toolsVersion = "8384"

I am missing all the DDB stuff. Is there a way to repair this?

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

do you have any backups or copies of the files before you started editting?

Timbobaloba

ASKER

only of the base "dc1.vmdk" version.

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

the quickest course of action now, would be STOP, and escalate to VMware Support, to see if they can force merge your snapshot chains and main parent, but the danger is the risk of corruption in AD.

Timbobaloba

ASKER

I've tried but only problem is I can't get VMware support on Sunday here in Australia. I have to wait for a 'callback' on Monday.

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

here is an article on how to build a vmdk from scratch

https://www.experts-exchange.com/Software/VMWare/A_1863-Rebuilding-a-VMware-VMDK-from-Scratch.html

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

but would strongly recommend making copies of what you have NOW, justbin case.

Timbobaloba

ASKER

haha. thanks. i learnt my lesson. doing now and will let you know how i go.

Timbobaloba

ASKER

My original dc1.vmdk file has the below ddb files which does work;

ddb.longContentID = "5ac165f5d48e3bda10b9e70c46a4859b"
ddb.toolsVersion = "8384"

I assume the contentID has to be unique?? can I just make one up for my others?