Lost 130GB on Bootcamp drive when making a VM
I used Transporter to make a VM copy of my Bootcamp partition as a first step toward importing the Virtual Machine version of Bootcamp into Parallels. In doing so, the program compressed the data on the Bootcamp partition so as to only copy the data and not the empty space on the partition.
In preparing this data-only verion of the Bootcamp partition, the program seems to have marked the whole Bootcamp drive as only 30GB (the amt of data on the drive) instead of 160GB, which is the actual size of the partition.
Now, when I boot into Bootcamp, I can *only* access this 30GB of my 160GB drive.
Is this a known issue with Transporter and the process of "shrinking" the Bootcamp partition? Anyone encounter this, or heard of it before?
Thanks.
PS This could have happened in VMWare's "Converter" software, which I used previously for the same purpose. There is a point in the process where one is asked whether to convert the whole drive including the free space, or just the portion of the drive with data. If one answers "just the data" part, then the drive is apparently redefined (temporariliy, I assume, if things work properly) as the smaller drive for purposes of copying it as a VM.
Last edited: Jun 20, 2008
