Recently, I've moved from a 1 TB to a 1.5 TB drive in my 2010 MacBook Pro (core i7) with 8 GB RAM. I've been trying everything to migrate an 80 GB Windows 7 partition from the old disk to a 120 GB partition on the new disk. I've tried Winclone, Paragon's Hard Disk Manager Pro 12, created boot camp parititions using Boot Camp Assistant, created NTFS paritions using Disk Utility and Paragon's NTFS driver, and nothing's worked. Finally, I used Parallels to PtoV my (now external) 80 GB Win7 partition to a virtual machine running off a disk image. Then I had a brilliant idea - use my virtual machine clone itself to an NTFS parition (or restore a virtual machine backup). So ... I partitioned my Mac HDD (now 1.5 TB) into a MacOS 10.8.2 partition and a 120 GB BOOTCAMP partition using Boot Camp Assistant. I then launched my Parallels Win7 virtual machine and noticed something quite wonky. MacOS in Disk Utility sees a 1.38 TB MacOS partition (which somehow suballocates the recoery partition within itself), and a 120.44 BOOTCAMP MS-DOS FAT parition. Windows 7 on other hand, sees a 200 MB GPT protective partition (which I assume contains the partition map), an 851.19 GB partition (containing MAC OS I assume), 128 MB unallocated (some kind of padd?), and a healthy 80 GB Windows partition with system, page file, active, crash dump, primary partition). Huh? It looks like what Windows is seeing is its last view of the 1 TB disk (which is no longer online), and isn't seeing the real disk installed in my MacBook Pro. Is this true? Once virtualized, Windows under Parallels no long sees any hardware disks? Has anyone anywhere had any luck migrating data from one disk to another, or rather from one Boot Camp to another?
