Salta al contenuto principale

Clone missing unallocated space

Thread solved

Hi,

 

Could someone explain what's going on here?

Disk1 is a small 250GB SSD

Why is unallocated after so small? Using 'As is' method 

 

image 295

- I also tried manual as the move method which seemed to limit the part to 2TB and doesn't show any unallocated space.

image 296

I'm kinda scared to proceed that I might have my drive shrunk??

0 Users found this helpful

Colin, what size of drives are you cloning from and to here?

Your source drive in the image is showing GPT partitions which are not limited in size but your target drive is being converted from GPT to MBR where the latter cannot address any partitions larger than 2TB.

This is confirmed by the message shown below the Before and After graphic!

The core issue here is that you are doing the clone on a Legacy / MBR boot system and thus the clone will result in a MBR drive.

To resolve this, you need to either use the Acronis Active Clone feature from within a Windows OS running ATI 2021 on a UEFI BIOS boot PC, or else boot your PC from the Acronis Rescue Media booted in UEFI BIOS boot mode.

KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

KB 61665: Acronis True Image 2019, 2020 and 2021: Active Cloning in Windows

KB 65508: Acronis True Image 2021: how to create bootable media

Please see KB 56634: Acronis True Image: how to clone a disk - and review the step by step guide given there.

Note: the first section of the above KB document directs laptop users to KB 2931: How to clone a laptop hard drive - and has the following paragraph:

It is recommended to put the new drive in the laptop first, and connect the old drive via USB. Otherwise you will may not be able to boot from the new cloned drive, as Acronis True Image will apply a bootability fix to the new disk and adjust the boot settings of the target drive to boot from USB. If the new disk is inside the laptop, the boot settings will be automatically adjusted to boot from internal disk. As such, hard disk bays cannot be used for target disks. For example, if you have a target hard disk (i.e. the new disk to which you clone, and from which you intend to boot the machine) in a bay, and not physically inside the laptop, the target hard disk will be unbootable after the cloning.

Ah I see! Thanks!

 

Interesting and very helpful.

 

As per your question disk 1 is 250gb. Disk 2 7tb. I'll just do a clean install the above seems like fath and band aids.

Colin, if you are intending to boot this PC from the new 7TB drive, then you definitely need to booting the PC in UEFI mode with the drive using GPT partition scheme format or else you will not be able to use more than 2TB of the new drive.

Yes that's right, it's already gpt so a fresh install direct to the drive should leave it setup 'proper' rather than cloning.

Incidentally I'm curious about the quoted text at the bottom...is that instruction just to save people having to mess with the boot order in bios, why would it be unbootable?

This has mostly come about as my win 7 won't upgrade because there is no sys reserve partition - I assume because it was cloned from another disk when I bought the ssd using the samsung clone tool. So I was going to clone my os(D1) to the 7tb(D2) and not have it as the primary boot drive (just as a backup OS incase I have driver issues I could hop back into 7 by swapping the boot order to maintain functionality until win10 issues are resolved.) So I would do a upgrade on D1. But.... the clone is a lot of messing due to the mrt/gpt situation. So instead I'll install to D2 from scratch as gpt, and once all is good clone that to d1.

Colin, dealing with your questions in order as far as possible.

The information about the clone resulting in a MBR drive should also be accompanied by another warning to say that the MBR disk would not be bootable.  This is because migrating from GPT to MBR is rarely successful.  The opposite migration of MBR to GPT is fine though!

One reason why your Win 7 upgrade not having a System Reserved (or MSR) partition is because that partition may be found on a second internal drive (if that second drive is shown as being Disk 0 in the hierarchy of drives).

When doing a clean install to the 7TB drive, I would recommend removing or disconnecting any other internal drives so that the EFI System Partition (equivalent to the MSR on MBR drives) is created correctly on that GPT drive (or ensure the 7TB drive is shown as Disk 0 by moving it or the connection to it).

If your smaller 250GB drive has a working copy of Windows 7 installed, then you could try putting this back as a secondary drive and see if this will still boot correctly if set as the boot drive in the BIOS to use as a fallback if needed in future.  You could test this by having only that drive installed initially.  Windows Disk Management should show if the MSR is on another drive.