- part5.tar.bz2
- part5.vmdk and part5-pt.vmdk
- (1.45 KiB) Downloaded 5 times
My laptop HD uses GPT with protective MBR.
Anyways, I've just found out something that could help fix the situation. I started my Win 7 vbox machine (with the VMDK still attached) and the resized partition showed up just fine, with the new (smaller) size, as if nothing wrong had happened.
From this, I believe the smaller partition size information was written not to the host GPT partition table, but to one of the 2 VMDK files I had created. Can anyone versed in VMDK internals confirm that this is what usually happens?
So now I just need to get the start and end addresses of the resized partition from the VMDK files. How can I do this?
I've attached the VMDK files. Below you can find the text part of them:
part5.vmdk:
Code: Select all
# Disk DescriptorFile
version=1
CID=b3f4268b
parentCID=ffffffff
createType="partitionedDevice"
# Extent description
RW 63 FLAT "part5-pt.vmdk" 0
RW 1985 ZERO
RW 2048000 ZERO
RW 532480 ZERO
RW 2048000 ZERO
RW 262144 ZERO
RW 148731028 FLAT "/dev/sda5" 0
RW 876 ZERO
RW 921600 ZERO
RW 5568512 ZERO
RW 1101004800 ZERO
RW 614400000 ZERO
RW 52428800 ZERO
RW 25575424 ZERO
RW 1423 ZERO
RW 33 FLAT "part5-pt.vmdk" 63
# The disk Data Base
#DDB
ddb.virtualHWVersion = "4"
ddb.adapterType="ide"
ddb.geometry.cylinders="16383"
ddb.geometry.heads="16"
ddb.geometry.sectors="63"
ddb.uuid.image="4f4f1f24-a8d8-4a86-9e0e-16d53a96ee7a"
ddb.uuid.parent="00000000-0000-0000-0000-000000000000"
ddb.uuid.modification="12e7a9d0-e556-4e02-ae4f-58c6ed8e6990"
ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000"
ddb.geometry.biosCylinders="1024"
ddb.geometry.biosHeads="255"
ddb.geometry.biosSectors="63"
strings part5-pt.vmdk
Code: Select all
EFI PART
StateApp
ppAetatS
StateApp
ppAetatS
EFI PART