VMware Communities
lionstone
Contributor
Contributor

Help! Expanding hard disk broke VM: The parent virtual disk has been modified since the child was created.

Hi, looks like I screwed up here and I'd really appreciate any help!

I have a VMWare XP install and I needed to increase the VM disk size so I went into my VM and removed the snapshots. VMWare crashed at this point, so I had to close it, then I restarted it. When I restarted it, I no longer had the optionsto remove any snapshots so I figured it was ok. (Big Mistake, I now realize)

Then I ran this command to expand the disk size: vmware-vdiskmanager -x 50Gb Windows\ XP\ Professional.vmdk

It spat back the following:

Using log file /tmp/vmware-blo/vdiskmanager.log

Grow: 100% done.

The old geometry C/H/S of the disk is: 16383/16/63

The new geometry C/H/S of the disk is: 16383/16/63

Disk expansion completed successfully.

Then I went to restart my VM and it returned the error:

Cannot open the disk '/var/lib/vmware/Virtual Machines/Windows XP Professional/Windows XP Professional-000001.vmdk' or one of the snapshot disks it depends on.

Reason: The parent virtual disk has been modified since the child was created.

I'm running Workstation on Ubuntu 8.04

To see if the issue was the CID, I ran the following:

grep --text -m2 CID= /var/lib/vmware/Virtual\ Machines/Windows\ XP\ Professional/Windows\ XP\ Professional.vmdk

which returned:

CID=4e4a6361

parentCID=ffffffff

Then I ran:

grep --text -m2 CID= /var/lib/vmware/Virtual\ Machines/Windows\ XP\ Professional/Windows\ XP\ Professional-000001.vmdk

which returned:

CID=1eb79052

parentCID=4e4a6361

so the CID's match correctly...

Please help if you can, I have no idea where to go from here. Many thanks!

Here is the full listing of files in the /var/lib/vmware/Virtual\ Machines/Windows\ XP\ Professional directory with ls -s:

total 71227976

4 archive

33012 core

12 nvram

24 vmware-0.log

24 vmware-1.log

24 vmware-2.log

244 vmware-core.gz

24 vmware.log

268 Windows XP Professional-0-000001-s001.vmdk

268 Windows XP Professional-0-000001-s002.vmdk

268 Windows XP Professional-0-000001-s003.vmdk

268 Windows XP Professional-0-000001-s004.vmdk

268 Windows XP Professional-0-000001-s005.vmdk

268 Windows XP Professional-0-000001-s006.vmdk

268 Windows XP Professional-0-000001-s007.vmdk

268 Windows XP Professional-0-000001-s008.vmdk

16 Windows XP Professional-0-000001-s009.vmdk

4 Windows XP Professional-0-000001.vmdk

158696 Windows XP Professional-000001-s001.vmdk

686700 Windows XP Professional-000001-s002.vmdk

627636 Windows XP Professional-000001-s003.vmdk

443456 Windows XP Professional-000001-s004.vmdk

16 Windows XP Professional-000001-s005.vmdk

4 Windows XP Professional-000001.vmdk

268 Windows XP Professional-0-s001.vmdk

268 Windows XP Professional-0-s002.vmdk

268 Windows XP Professional-0-s003.vmdk

268 Windows XP Professional-0-s004.vmdk

268 Windows XP Professional-0-s005.vmdk

268 Windows XP Professional-0-s006.vmdk

268 Windows XP Professional-0-s007.vmdk

268 Windows XP Professional-0-s008.vmdk

16 Windows XP Professional-0-s009.vmdk

4 Windows XP Professional-0.vmdk

2098948 Windows XP Professional-1-f001.vmdk

2098948 Windows XP Professional-1-f002.vmdk

2098948 Windows XP Professional-1-f003.vmdk

2098948 Windows XP Professional-1-f004.vmdk

2098948 Windows XP Professional-1-f005.vmdk

2098948 Windows XP Professional-1-f006.vmdk

2098948 Windows XP Professional-1-f007.vmdk

2098948 Windows XP Professional-1-f008.vmdk

2052 Windows XP Professional-1-f009.vmdk

4 Windows XP Professional-1.vmdk

2098948 Windows XP Professional-f001.vmdk

2098948 Windows XP Professional-f002.vmdk

2098948 Windows XP Professional-f003.vmdk

2098948 Windows XP Professional-f004.vmdk

1028 Windows XP Professional-f005.vmdk

2098948 Windows XP Professional-f006.vmdk

2098948 Windows XP Professional-f007.vmdk

2098948 Windows XP Professional-f008.vmdk

2098948 Windows XP Professional-f009.vmdk

2098948 Windows XP Professional-f010.vmdk

2098948 Windows XP Professional-f011.vmdk

2098948 Windows XP Professional-f012.vmdk

2098948 Windows XP Professional-f013.vmdk

2098948 Windows XP Professional-f014.vmdk

2098948 Windows XP Professional-f015.vmdk

2098948 Windows XP Professional-f016.vmdk

2098948 Windows XP Professional-f017.vmdk

2098948 Windows XP Professional-f018.vmdk

2098948 Windows XP Professional-f019.vmdk

2098948 Windows XP Professional-f020.vmdk

2098948 Windows XP Professional-f021.vmdk

2098948 Windows XP Professional-f022.vmdk

2098948 Windows XP Professional-f023.vmdk

2098948 Windows XP Professional-f024.vmdk

2098948 Windows XP Professional-f025.vmdk

2098948 Windows XP Professional-f026.vmdk

5388 Windows XP Professional-f027.vmdk

4 Windows XP Professional.vmdk

4 Windows XP Professional.vmsd

4 Windows XP Professional.vmx

4 Windows XP Professional.vmx~

0 Kudos
14 Replies
continuum
Immortal
Immortal

Good that you use preallocated split disks.

Man - do not ignore the vmware-vdiskmanager warning about snapshots again !!!!!!!!!

Back to work:

zip all your old vmware.logs ! - thats important

next post the small vmdks - those that have no s00* or f00* in the name.

DO NOT TRY TO START THE VM AGAIN BEFORE WE ARE FINISHED

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
lionstone
Contributor
Contributor

Whoa, great - thanks for the help. OK, attached are the small vmdks:

0 Kudos
lionstone
Contributor
Contributor

Also, I made an error: I'm running VMWare Server, not VMWare Workstation. Sorry for the confusion...

0 Kudos
continuum
Immortal
Immortal

Windows XP Professional-0-000001.vmdk

Windows XP Professional-000001.vmdk

are missing.

Hurry up - I go to bed in 15 minutes Smiley Wink

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
lionstone
Contributor
Contributor

Sorry, here they are:

0 Kudos
continuum
Immortal
Immortal

No need to aplogize - you provide useful data - better than average Smiley Wink

Hmm - I don't understand one thing : your VM seems to use two virtual disks - in your directory you have three

Windows XP Professional.vmdk

Windows XP Professional-0.vmdk

Windows XP Professional-1.vmdk - the last one has no snapshot.

Can you explain ?

If it is an unused disk which is just lying around you can ignore that one. If not - don't use the suggestion yet - we need to better understand it - tomorrow.

Basically I would now change Windows XP Professional.vmdk back to:

#Disk DescriptorFile

version=1

CID=4e4a6361

parentCID=ffffffff

createType="twoGbMaxExtentFlat"

#Extent description

RW 4193792 FLAT "Windows XP Professional-f001.vmdk" 0

RW 4193792 FLAT "Windows XP Professional-f002.vmdk" 0

RW 4193792 FLAT "Windows XP Professional-f003.vmdk" 0

RW 4193792 FLAT "Windows XP Professional-f004.vmdk" 0

RW 2048 FLAT "Windows XP Professional-f005.vmdk" 0

#The Disk Data Base

#DDB

ddb.toolsVersion = "6532"

ddb.adapterType = "ide"

ddb.geometry.sectors = "63"

ddb.geometry.heads = "16"

ddb.geometry.cylinders = "16383"

ddb.virtualHWVersion = "4"

As this IDE-disk is 8Gb or larger you do not need to rewrite the geometry.

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

lionstone
Contributor
Contributor

I was trying to avoid this whole resizing business in the first place, so I first tried to create a second disk for the VM...but I couldn't figure out how to access it from within the VM, so I gave up and foolishly decided to resize the VM instead. So I'm guessing Windows XP Professional-1.vmdk is the extra disk I made, which serves no purpose...

I'll back up the whole folder and then give your suggestion a try! Thanks so much! I will report back with how it goes...

0 Kudos
continuum
Immortal
Immortal

Good luck - if you still get the "parent was modified" - check the CID-chain for both disks again - sounds like you already know how to do that.

By the way - in emergency case - when you just need to get the data out of it - copy to windows host and use vdk.exe against

"Windows XP Professional-000001.vmdk"

This also gives good suggestions on what may still be wrong ...

Good night Smiley Wink

By the way - resizing is ok - when you have NO snapshot

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
lionstone
Contributor
Contributor

It worked!! Wow, thanks!!! You are seriously my hero!!! :smileygrin:

The only issue is that I'm back where I started- I still need to expand the virtual hard disk Smiley Sad

How can I do this without messing everything up again? Was I correct in using the following command?

vmware-vdiskmanager -x 50Gb Windows\ XP\ Professional.vmdk

I haven't touched anything since changing Windows XP Professional.vmdk to your recommeded setup...

Or how can I add that other 16gb disk I created to my virtual XP?

THANKS SOOOOOO MUCH! Seriously you saved my day, if you ever come to San Francisco, I buy your beers Smiley Happy

0 Kudos
admin
Immortal
Immortal

Try taking a snapshot and then deleting it. That should try to reconsolidate your existing delta disks.

If it crashes again, please post your log files.

If it succeeds, you should verify that your .vmx file references the base .vmdk file (and that you don't have any other leftover .vmdk files in your VM's directory).

0 Kudos
lionstone
Contributor
Contributor

OK, I took a snapshot, closed the VM, deleted the snapshot, then restarted the VM...But nothing changed.

I am not sure how I would know that the extra space is available- I'm assuming it would show up when I look for free space available on drive c within the virtual machine? Or am I missing a step?

My log files are attached- thanks for the help!

0 Kudos
admin
Immortal
Immortal

I thought you meant how to remove the snapshot disks.

First (after backing up your VM Smiley Wink ), you need to make absolutely sure you've consolidated all your snapshot disks before you do any resizing (this is what I was explaining how to do in my earlier post). This will not have any visible effect from within the VM.

After that, you can use vmware-vdiskmanager to grow the disk. This will increase the disk capacity, but your guest will not be able to use the extra space until you either add a new partition in the guest or use a partition resizing tool (e.g. gparted, Partition Magic, etc.) to resize the existing partition to fill the space.

0 Kudos
RDPetruska
Leadership
Leadership

Or how can I add that other 16gb disk I created to my virtual XP?

If you've added it to the vmx file and it appears in the VM's settings, then start the XP guest. And add it exactly the same way you would if it was a new physical disk: Run Disk Management (Start>Control Panel>Administrative Tools>Computer Management, select Storage>Disk Management in the treeview. You should see a new, blank hard disk. Create a partition on it, and then format it and give it a drive letter.

0 Kudos
lionstone
Contributor
Contributor

lionstone wrote:

Or how can I add that other 16gb disk I created to my virtual XP?

> If you've added it to the vmx file and it appears in the VM's settings,

> then start the XP guest. And add it exactly the same way you would if

> it was a new physical disk: Run Disk Management (Start-->Control

> Panel>Administrative Tools>Computer Management, select

> Storage-->Disk Management in the treeview. You should see a new,

> blank hard disk. Create a partition on it, and then format it and give

>it a drive letter.

Whoa, great! So simple and worked like a charm..Guess I need to learn how to use Windows, I've been on Linux too long. Thanks, this was exactly what I needed- I'm done messing around with the disk-manager now Smiley Happy

Greatly appreciate all the help, everyone!

0 Kudos