The parent virtual disk has been modified since the child was created. - oh heck....

[dexdyne]

I needed to expand a vdisk.

I tried using the manager with the -x parammeter, and it complained that I had snapshots

I went into the snapshot manager and deleted the snapshots, leaving only the one created as the VM was closed down.

I ran the -x function to expand the vdisk, but it complained that the disk neded repair, so I ran the -R function, which said it worked OK.

I re-ran the -x function and it reported success.....

now when I try to open the VM it complains that the parent vdisk has been modified.

No I didn't take a back-up... I'm feeling pretty dumb.

====================================================================================

C:\VMWare\AVR32_Ubuntu2>"C:\Program Files\VMware\VMware Workstation\vmware-vdiskmanager" -x 40GB AVR32_Ubuntu_7.10.vmdk

Failed to open the disk 'AVR32_Ubuntu_7.10.vmdk' : The specified virtual disk needs repair (0xe00003e86).

Failed to open disk 'AVR32_Ubuntu_7.10.vmdk' : The specified virtual disk needs repair (0xe00003e86).

C:\VMWare\AVR32_Ubuntu2>"C:\Program Files\VMware\VMware Workstation\vmware-vdiskmanager" -R AVR32_Ubuntu_7.10.vmdk

The virtual disk, 'AVR32_Ubuntu_7.10.vmdk', was corrupted and has been successfully repaired.

C:\VMWare\AVR32_Ubuntu2>"C:\Program Files\VMware\VMware Workstation\vmware-vdiskmanager" -x 40GB AVR32_Ubuntu_7.10.vmdk

Disk expansion completed successfully.

==============================================================================

I still have LOADS of .vmdk files in the directory - do I have any chance of getting back anything???

Any help much appreciated

David

directory listing of .vm attached:

[dexdyne]

OK, bit more info....

when I deleted all the snapshots, my pc hung....

I had to abort vmware, and restart it - but having done do, the snapshot manager showed only thge one snapshot entry marked "made when closing down".....

So I thought I was safe to go ahead and resize....

but as you saw, it forced me to do a repair before it would resize.

Guess - the repair put back a link to the snapshots I thought I had deleted..... ???????

Now... the log file for the incomplete start up show it going back through all 27 snapshots... and finally coming to....

May 27 13:30:36.279: vmx| DISKLIB-DSCPTR: Opened : "AVR32_Ubuntu_7.10-s021.vmdk" (0x2e)

May 27 13:30:36.294: vmx| DISKLIB-DSCPTR: Opened : "AVR32_Ubuntu_7.10-s022.vmdk" (0x2e)

May 27 13:30:36.294: vmx| DISKLIB-LINK : Opened 'C:\VMWare\AVR32_Ubuntu2\AVR32_Ubuntu_7.10.vmdk' (0x2e): twoGbMaxExtentSparse, 83886080 sectors / 40 GB.

May 27 13:30:36.294: vmx| DISKLIB-LINK : Attach: the capacity of each link is different (83886080 != 41943040).

May 27 13:30:36.294: vmx| DISKLIB-CHAIN : "C:\VMWare\AVR32_Ubuntu2\AVR32_Ubuntu_7.10.vmdk" : failed to open (The parent virtual disk has been modified since the child was created).

May 27 13:30:38.669: vmx| DISKLIB-LIB : Failed to open 'C:\VMWare\AVR32_Ubuntu2\AVR32_Ubuntu_7.10-000027.vmdk' with flags 0x2a (The parent virtual disk has been modified since the child was created).

May 27 13:30:38.669: vmx| DISK: Cannot open disk "C:\VMWare\AVR32_Ubuntu2\AVR32_Ubuntu_7.10-000027.vmdk": The parent virtual disk has been modified since the child was created (18).

so I have a clash between the last snapshot in the chain, and the base disk, which quite rightly, now thinks it is 40gig.......

Could the fix for this be as simple as pointing the VM control file straight at the 40g image?

[dexdyne]

no, it wasn't as simple as that - pointing to that just got me a copy of ubuntu as it was installed, and a not very functional one either.

So I manually downsized the drive descriptor by halving the number of sectors, and commenting out the new 20G worth of image files... then I patched the CID in snapshot1 to match the edited base image.

And, lo, I have a computer again.

That was a horrible experience.

David