Salta al contenuto principale

Issues with Clone process

Thread needs solution

Hello,

I've attempted to clone my Windows OS drive 1TB ~150GB used to a brand new 500GB NVMe drive. Every time I always get an Insert Boot Disk and Press Any Key type error message. Is there something I need to do special for ATI to get a bootable disk?

0 Users found this helpful

Have you disconnected your old disk from that computer?  You must do that prior to booting after a clone.

Hello,

Yes I have tried not disconnecting and disconnecting it. Both result in the same thing. Although I'm not 100% sure why you would need to do thing anyhow. I've tried eveything I can think of and even used alternative software and they all result in the same thing.

The problem is your boot order in your bios is set to boot to the wrong device.

You will need to boot into your machine bios, go to the boot section, find the boot order - boot prioity, and make Windows Boot Manager first in boot order.  Save and exit, it should boot.

That is not the issue, I recloned the drive, shutdown disconnected my two HDD's, went into BIOS and ensured my Samsung 970 EVO was set to boot first though it shouldn't matter since it was the only one anyhow. Results are the same.

Well, now that we know what drive you are using that helps.

The 970 EVO is an NVMe PCIe M.2 based drive.  In order to boot that drive you must have the drive setup as UEFI/GPT device.  It will not boot otherwise.  Selecting the drive name in your boot order in the bios will not work as well.

You must select Windows Boot Manager in the boot order to get the drive to boot.  If you do not see Windows Boot Manager in your boot priority order list than it is likely that the drive is not setup for UEFI/GPT boot.

How did you do this clone.  Did you run the clone tool while booted into Windows using the True Image application or did you use bootable Recovery Media to create the clone?  I suspect you used the Windows application which is fine however, if you are trying to do this with Windows 7 then you have another problem as Win 7 natively will not boot using an NVMe drive.

Hello,

I used the built-in cloner tool of ATI -> Tools -> Clone Disk on Windows 10 Pro. The disk is GPT and I have UEFI. It the EVO never showed up with the Windows Boot Manager using ATI. I tried and failed with Clonezilla just now it doesn't like cloning to a smaller disk, but it did create a Windows Boot Manager, although it wouldn't boot because it failed to complete the clone.

The last thing I can think of is I suppose to reduce my source partition down below the size of my Evo, which I'm working on now.

I suggest that when using the Windows installed app after you perform the clone shutdown the computer, remove the old drive (the one you created the new clone from), now start the computer and enter the bios, go to the boot order, and make sure Windows Boot Manager is first in the order.

Using the Automatic method of the Clone tool should adjust your partition size properly as well without your intervention.

Thank you I've done this already. I now think it's the way Windows was installed ~1yr+ ago which is causing me issues. From my testing which is strange, is that windows (source) don't seem to want to boot without my Ubuntu drive attached as well. I originally installed Ubuntu, then bought another 1TB drive and Windows later. In the attached image disk 0 is Linux, disk 1 is my source Windows install, and disk 2 is the new M2 drive. I could only install on the M2 while the other two drives where disconnected.

Allegato Dimensione
484368-162303.jpg 213.2 KB

It appears that you are correct.  What I see is your EFI boot partition for your original setup is on your Linux disk 0.  When you installed Windows by default disk 0 was selected to host the boot partition.

The image you posted showing disk 2 is after you installed Windows on the M.2 drive and not after the clone process was run correct?

 

Yes, that is correct. It seems due to the way Windows is currently installed (disk 1), I can't clone, so I've done a fresh install (disk 2 M2), and almost have it setup software wise. After all this, I'll wipe the source Windows (disk 1) and use it additional storage for my M2. Consider this post resolve.