Help! Expanded disk size and received error: The parent virtual disk has been modified since the child was created.

[Steve008]

Hey everyone..I need some help here...I ran the vdiskmanager command (below) to expand the size of my virtual disk. Before I ran the command, I deleted all my snapshots and I do not have any partitions. After running the command successfully, I tried to start the virtual disk and I received the error: The parent virtual disk has been modified since the child was created.

vmware-vdiskmanager -x 30GB "C:Users\Steve\Documents\Virtual Machines\Windows XP Professional - Work\Windows X Professional.vmdk"

I went online, read everyone's comments, and I did check the CIDs (see below). Everything matches. My .vmdk file is 6 GB, so I cannot even load the file to edit it - I did GREP the file, though, to get the CID values. I don't understand why the .vmdk file is so big!

************************ Windows XP Professional.vmdk ************************

CID=4805fc77

parentCID=ffffffff

************************Windows XP Professional-000001.vmdk ************************

CID=dab9e598

parentCID=4805fc77

What can I do to recover my virtual disk? I cannot get it to load without receiving the same error. I'm trying not to panic here but I really would like to get to this virtual disk! Any advice would be appreciated!!

[continuum]

First things first: zip all your old vmware.log files you have in that dir.

Attach last vmware.log from a successful start - before you used vdiskmanager.

Attach embedded descriptors for both the basedisk and the snapshot.

DO NOT START THE VM AGAIN

___________________________________

description of vmx-parameters:

VMware-liveCD:

[Steve008]

Here are the log files..I'm not sure how to obtain the descriptors?

[continuum]

read my site

http://sanbarrow.com/vmdk/procedures.html

special "extract with dsfo"

___________________________________

description of vmx-parameters:

VMware-liveCD:

[Steve008]

Here is the information from the DSFO utility:

version=1

CID=4805fc77

parentCID=ffffffff

createType="monolithicSparse"

1. Extent description

RW 62914560 SPARSE "Windows XP Professional.vmdk"

1. The Disk Data Base

#DDB

ddb.virtualHWVersion = "6"

ddb.toolsVersion = "7241"

ddb.geometry.cylinders = "16383"

ddb.geometry.heads = "16"

ddb.geometry.sectors = "63"

ddb.adapterType = "ide"

[continuum]

change

RW 62914560 SPARSE "Windows XP Professional.vmdk"

to

RW 16777216 SPARSE "Windows XP Professional.vmdk"

and inject descriptor again

cross your fingers and try a start

___________________________________

description of vmx-parameters:

VMware-liveCD:

[Steve008]

Ok...I'll try that....Waht do you mean by inject descriptor again? I plan on updating the .vmdk file with the new #....Is there something else I need to do?

[Steve008]

Bummer..Now I get an error "File not found: Windows XP Professional-000002.vmdk". It is telling me that this file is required to power on the virtual machine. Any idea on what I can to to fix this???

[Steve008]

Bummer..Now I get an error "File not found: Windows XP

Professional-000002.vmdk". It is telling me that this file is required

to power on the virtual machine. Any idea on what I can to to fix

this???

[continuum]

No idea - posting a file-listing may be useful - we also need the other embedded descriptors from the -00000.vmdks

___________________________________

description of vmx-parameters:

VMware-liveCD:

[Steve008]

Do I also used DSFO to get the other descriptors from the other files as well?

[continuum]

Yep - same procedure

___________________________________

description of vmx-parameters:

VMware-liveCD:

[Steve008]

Ok..I ran DSFO on the following files with the output:

Windows XP Professional.vmxf:

<?xml version="1.0"?>

<Foundry>

<VM>

<VMId type="string">52 e4 d2 51 f8 ec 47 d8-75 47 ba eb 74 46 20 48</VMId>

<ClientMetaData>

<clientMetaDataAttributes/>

<HistoryEventList/></ClientMetaData>

<vmxPathName type="string">Windows XP Professional.vmx</vmxPathName></VM></Foundry>

Windows XP Professional.vmx:

config.version = "8"

virtualHW.version = "6"

scsi0.present = "TRUE"

memsize = "1364"

ide0:0.present = "TRUE"

ide0:0.fileName = "Windows XP Professional_9_1_08_harddrive-000001.vmdk"

ide1:0.present = "FALSE"

ide1:0.fileName = "Windows XP Professional_9_1_08_harddrive-0000

I am almost at the point where I should just try to see if I can retrieve files from the VM file...Is there a way to do this? However, the best solution would to get just the VMWare image up and running..

[continuum]

Hi

you can use dsfo.exe to extract embedded descriptors from *vmdk files. After editing the descriptor you re-inject it with dsfi.exe.

What you have done with the vmx and vmxf files makes no sense and doesn't help.

As I already mentioned we need the embedded description for all vmdk files - no need to do it with other extensions

___________________________________

description of vmx-parameters:

VMware-liveCD:

[Steve008]

Sorry for the confusion....I only have one .vmdk file to run the DFSO against. The output is below:

version=1

CID=4805fc77

parentCID=ffffffff

createType="monolithicSparse"

1. Extent description

RW 16777216 SPARSE "Windows XP Professional.vmdk"

1. The Disk Data Base

#DDB

ddb.virtualHWVersion = "6"

ddb.toolsVersion = "7241"

ddb.geometry.cylinders = "16383"

ddb.geometry.heads = "16"

ddb.geometry.sectors = "63"

ddb.adapterType = "ide"

[continuum]

No - look again - you MUST have more than one *.vmdk file - otherwise you would have no problem anymore

___________________________________

description of vmx-parameters:

VMware-liveCD:

[Steve008]

Well, I do have one more .vmdk file but it is too big for the DFSO (I just assummed it was a "wrong" .vmdk file). I get the error that the file is too large..Is there a way around this?

[continuum]

I never seen that - here on my box dsfo.exe can handle files of saeveral hundreds of GB.

Post list of vmdks and I write a batch

___________________________________

description of vmx-parameters:

VMware-liveCD:

[continuum]

good night

___________________________________

description of vmx-parameters:

VMware-liveCD: