VMware Cloud Community
WesTopping
Enthusiast
Enthusiast

the parent virtual disk has been modified since the child was created (Help!!)

I resized the parent disk without realizing that the VM had a snapshot. Now I am getting this error when I try to power on the VM. The parent virtual disk has been modified since the child was created. This is on ESX 3.0.2 any ideas on how I could recover from this?

Wes

Reply
0 Kudos
3 Replies
esiebert7625
Immortal
Immortal

Check out these threads...

http://communities.vmware.com/message/694228#694228

http://communities.vmware.com/message/475084#475084

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Thanks, Eric

Visit my website:

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Reply
0 Kudos
jinweijie
Contributor
Contributor

hi,

i encounted the same problem and i solved it this way:

use text editor to open the .vmdk file, for example Windows Server 2003 Standard Edition.vmdk

remove the disks added recently, for example,:

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s001.vmdk"

RW 2099200 SPARSE "Windows Server 2003 Standard Edition-s002.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s003.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s004.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s005.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s006.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s007.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s008.vmdk"

RW 12288 SPARSE "Windows Server 2003 Standard Edition-s009.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s010.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s011.vmdk"

RW 2101248 SPARSE "Windows Server 2003 Standard Edition-s012.vmdk"

remove

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s010.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s011.vmdk"

RW 2101248 SPARSE "Windows Server 2003 Standard Edition-s012.vmdk"

and start you vm again Smiley Happy hope it helps

Reply
0 Kudos
continuum
Immortal
Immortal

and start you vm again Smiley Happy hope it helps

NO - that does NOT help - on the contrary - your tip will surely mess up the complete VM and it does not apply to ESX at all.

At anybody reading the last post: ignore it

___________________________________

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 ...

Reply
0 Kudos