Clone a Windows Installation to a 3TB Hard Drive; MBR to GPT

27
2013-10
  • DanBlakemore

    I have Windows 7 Professional 64-bit installed on my desktop. Unfortunately for me and my wallet my hard drive is failing. I have purchased a 3TB hard drive as a replacement for my current 2TB drive. I would like to avoid as much hassle as possible in moving to this new drive so I would like to copy my current partition to the new drive using Gparted. The problem is that I suspect that my current partition is MBR, and I need GPT on my new drive since it is 3TB.

    Can I simply copy the MBR partition onto the new disk and then convert it to GPT after the fact (can you even convert the type of a partition)?

    Or would I need to somehow copy the contents of the partition into a GPT partition on the new drive?

    How do I go about making this transistion?

    Also, are there any issues I should be wary of booting to a GPT partition? If it matters, my motherboard is 1 year old as of May, 2012.

    Edit: My motherboard is 1 day old. My old one does not have UEFI compatibility, so I decided to make an upgrade to Intel today given that I would need a UEFI motherboard to use my new HDD.

    How much can I use a dying hard drive (bad sectors according to Hitachi Drive Fitness Test)?
    I have assumed not at all, to be safe.

    Edit 2: After two cloning attempts, nothing worked (direct cloning or cloning to an image). I just installed Windows fresh and then and copied everything I could. Honestly, after several days of stress with the cloning software, I would recommend this to anyone who has this problem in the future.

  • Answers
  • Peter Maxwell

    Use clonezilla to make an image of your hdd then restore that image to your new drive and it would be as if nothing happened. http://clonezilla.org/
    You'll have to boot clonezilla from a USB or CD in order to do this.

    Alright given the new information I recommend you do the following:

    1. Partition your 3TB drive in half.
    2. Create the image using the software above while saving the image to the second half of the partition you just made. (Clonezilla will let you specify where you want to put the image)
    3. Restore the image to the first half.
    4. Once it seems everything is good, format the second partition then delete the second partition
    5. Extend the first partition to cover the entire drive.

    Note: If you don't have enough space then you might have to remove some of your games then just install them after the image goes down.

    I recommend just messing around with it till you get what you want, because as long as you have the original you'll be fine.

  • Matthew

    None of the answers so far gave me all the info I needed to solve this problem. I solved it and I'm successfully running my old Windows MBR install on UEFI and GPT now.

    1. Connect only your target drive and run Windows 7 Setup in UEFI mode. You can do this by enabling UEFI in the BIOS and by using the DVD. It is possible to make a USB stick that UEFI boots, but the Microsoft tool will not make them so. Watch out for this.
    2. Install Windows 7 clean to your target drive. You can confirm you're in UEFI mode as 3 partitions (EFI, MSR, and Main) will be created.
    3. Connect your source drive and boot up an Ubuntu (or other linux) live CD/DVD/USB and use NTFSCLONE (from terminal with super user priv: 'sudo ntfsclone', syntax is easy to use from the help page) to copy your NTFS partition from your source drive and overwrite the main windows partition on your target drive. Watch out for the syntax of NTFSCLONE, it can have the target and source on the command line the other way round.
    4. Disconnect source drive and enjoy your old install on the new drive.

    From what I can see, instead of running boot code in the disk start, EFI simply runs boot code on the EFI FAT32 partition in a predetermined location, this boot code then starts the Windows installation. As we overwrite one that was set up correctly, it starts our old one up instead.

    It has taken me literally days of fiddling to figure this all out and now hopefully others wont have to.

    (Other notes: on my Intel DP43TF I had to update the BIOS and set the BIOS to IDE instead of AHCI for the Windows setup. I switched it back to AHCI after putting my old install onto the GPT drive and all was well)

    Tested and working!

  • Robert

    First you have to make sure that your mainboard supports UEFI boot. It may have to enabled in the BIOS.

    The content of the partition itself is NTFS and has no difference between MBR and GPT. But the boot code needed for booting via UEFI in the partition may be different.

    Furthermore the biggest difference is the ~100MB boot partition which is usually located right before the system partition. UEFI needs an additional partition.

    You can try to create two 100MB partitions manually, then copy the system partition after it. Then boot the Win7 install CD and let it repair the boot process. This may work however I don't know (never tried it).

    But I think it would be easier to start a new Windows 7 installation and let it partition the disk automatically. While installation you can reset the computer and afterwards overwrite the incomplete installation with your old one.

    Recommended UEFI-Based Disk-Partition Configurations

  • DanBlakemore

    Another possibility is to use robocopy. Since UEFI is only needed to use the drive as a boot drive, you can mount it with any 64-bit Windows 7. This method copies the files from the old disk to the new after the new drive has been partitioned.

    1. Partition the 3TB disk with Windows
    2. Insert both the original and new drives into another computer running 64-bit Windows 7
    3. In an (elevated?) command prompt, run the command robocopy F: G: /mir /zb /copyall /dcopy:t /sl /xd "System Volume Information" /xf hiberfil.sys pagefile.sys /xj /r:0 /w:0 /mt:2 /log:robocopylog.txt where F: is the source drive and G: is the destination drive. Refer to the documentation of robocopy for the flag definitions.
    4. Done.

    I have not tested this yet, and I may end up going with Peter Maxwell's answer, but I don't want to be the forum post in 2 years that someone finds and is dissatisfied with the lack of answers.

    This answer is based on the SevenForums.com thread that I started.

  • Vincent Chan

    I upgraded from a 2T MBR drive to a 3T GPT one (each with a Win 7 OS partition & a data partition). The comments here gave me really great help in transferring the old Win 7 MBR partitions to the new GPT ones, especially the boot partition. Just to share here what I did so that it would take less time for others with the same need:

    I had both drives connected throughout, plus a USB thumb drive and a DVD drive

    1. Make the USB thumb drive bootable with Parted Magic (reference: http://www.makeuseof.com/tag/how-to-clone-your-hard-drive/)
    2. Take the Win 7 64-bit setup DVD (or burn one from iso image available on the net), set the PC's BIOS option (in my case, press F12 at start up) to boot the Win 7 setup DVD in UEFI mode
    3. Do a clean installation of Win 7 on to the new 3T disk (no need to worry about the settings as they'll be overwritten later) - Win 7 will create 3 partitions automatically under GPT
    4. Restart and set the BIOS option to boot the USB drive into Parted Magic (use x386_64 platform)
    5. Using Partition Editor, reduce the Win 7 partition to the size needed and create a new data partition with the vacated space
    6. Using Clonezilla, clone the old MBR Win 7 boot partition into the new GPT Win 7 boot partition
    7. Do the same with the data partition
    8. Disconnect the old 2T drive (optional: to avoid drive letter confusions), set the BIOS option to boot the new 3T drive in UEFI mode
    9. When Win 7 reports error with the drive, follow instructions on screen to go along with "System Recovery" > "Startup Repair" using the Win 7 DVD - the problems will be fixed automatically by Win 7
    10. Reboot and allow the system to go through chkdsk - the new drive is ready with exactly the same two partitions and everything transferred from the old drive

    Hope this helps - it worked for me!


  • Related Question

    partitioning - Can a hard drive using a GPT partition table be booted in an AMD computer?
  • Phenom

    I have a 64-bit AMD Phenom II and I'm installing a new hard drive on it. One of the options when formatting the drive is to use a GPT partition table instead of an MBR. I read somewhere that only Itaniums can boot disks formatted with GPT. What about AMDs?

    Also, are there any advantages of using GPT instead of MBR for a partition table? Is it more secure?


  • Related Answers
  • William Hilsum

    I read somewhere that only Itaniums can boot disks formatted with GPT. What about AMDs?

    AMD Opteron server CPUs certainly do support GUID Partition Tables.

    are there any advantages of using GPT instead of MBR for a partition table? Is it more secure?

    1. What is a GPT disk? The GUID Partition Table (GPT) was introduced as part of the Extensible Firmware Interface (EFI) initiative. GPT provides a more flexible mechanism for partitioning disks than the older Master Boot Record (MBR) partitioning scheme that has been common to PCs.

    A partition is a contiguous space of storage on a physical or logical disk that functions as though it were a physically separate disk. Partitions are visible to the system firmware and the installed operating systems. Access to a partition is controlled by the system firmware before the system boots the operating system, and then by the operating system after it starts.

    1. What is wrong with MBR partitioning? MBR disks support only four partition table entries. If more partitions are wanted, a secondary structure known as an extended partition is necessary. Extended partitions can then be subdivided into one or more logical disks. By convention, Windows creates MBR disk partitions and logical drives on cylinder boundaries based on the reported geometry, although this information no longer has any relationship to the physical characteristics of the hardware (disk driver or RAID controller)., For Windows Vista and Windows Server 2008, more logical boundaries will be selected when the hardware provides better hints at the true cache or physical alignment. Because this partition information is stored on the drive itself, the operating system is not dependent on the alignment. MBR partitioning rules are complex and poorly specified. For example, does cylinder alignment mean that each partition must be at least one cylinder in length? An MBR partition is identified by a two-byte field, and coordination is necessary to avoid collision. IBM originally provided that coordination; today there is no single authoritative list of partition identifiers.

    Another common practice is to use partitioned or "hidden" sectors to hold specific information. That practice is undocumented and results in severe system problems that are difficult to debug. Over the years, vendor-specific implementations and tools have been released to the public, making support difficult.

    1. Why do we need GPT? GPT disks can grow to a very large size. The number of partitions on a GPT disk is not constrained by temporary schemes such as container partitions as defined by the MBR Extended Boot Record (EBR).

    The GPT disk partition format is well defined and fully self-identifying. Data critical to platform operation is located in partitions and not in unpartitioned or "hidden" sectors. GPT disks use primary and backup partition tables for redundancy and CRC32 fields for improved partition data structure integrity. The GPT partition format uses version number and size fields for future expansion.

    Each GPT partition has a unique identification GUID and a partition content type, so no coordination is necessary to prevent partition identifier collision. Each GPT partition has a 36-character Unicode name, which means that any software can present a human-readable name for the partition without any additional understanding of the partition.

    1. Where can I find the specification for GPT disk partitioning? Chapter 16 of the Extensible Firmware Interface (EFI) specification defines the GPT format. This document is available at http://www.Intel.com/technology/efi/

    2. Is EFI required for a GPT disk? No. GPT disks are self-identifying. All the information needed to interpret the partitioning scheme of a GPT disk is completely contained in structures in specified locations on the physical media.

    3. How big can a GPT disk be? In theory, a GPT disk can be up to 2^64 logical blocks in length. Logical blocks are commonly 512 bytes in size.

    The maximum partition (and disk) size is a function of the operating system version. Windows XP and the original release of Windows Server 2003 have a limit of 2TB per physical disk, including all partitions. For Windows Server 2003 SP1 Windows XP x64 edition, and later versions, the maximum raw partition of 18 exabytes can be supported. (Windows file systems currently are limited to 256 terabytes each.)

    1. How many partitions can a GPT disk have? The specification allows an almost unlimited number of partitions, but the Windows implementation restricts this to 128 partitions. The number of partitions is limited by the amount of space reserved for partition entries in the GPT.

    2. Can a disk be both GPT and MBR? No. However, all GPT disks contain a Protective MBR.

    3. What is a Protective MBR? The Protective MBR, beginning in sector 0, precedes the GPT partition table on the disk. The MBR contains one type 0xEE partition that spans the disk.

    4. Why does the GPT have a Protective MBR? The Protective MBR protects GPT disks from previously released MBR disk tools such as Microsoft MS-DOS FDISK or Microsoft Windows NT Disk Administrator. These tools are not aware of GPT and do not know how to properly access a GPT disk. Legacy software that does not know about GPT interprets only the Protected MBR when it accesses a GPT disk. These tools will view a GPT disk as having a single encompassing (possibly unrecognized) partition by interpreting the Protected MBR, rather than mistaking the disk for one that is unpartitioned.

    5. Why would a GPT-partitioned disk appear to have an MBR on it? If this occurred, you must have used an MBR-only-aware disk tool to access the GPT disk. See answers #8 through #10, earlier.

    6. If the disk is larger than the maximum size an MBR can report, will the entire disk contents be protected? The EE partition in the Protective MBR is specified to be the maximum size allowable in an MBR.

    Source