Direkt zum Inhalt

ATI2017 not start the clone process in pre OS loader.

Thread needs solution

Hi,

I am a registered user from the ATI2012 version and now I have a little problem.

I was trying to clone my 750Gb HD to a new Crucial 525Gb SSD. The initial proces was ok, I had selected te origin and target disk and ATI2017 show me that it need to restart the system to execute the clone process.

After the restart, ATI2017 show a litle message in the screen to notice that is in pre OS loader, anfer that the screen go to black and that's it all. The clone process not start, it's like was waiting something, but I press all keys, move the mouse to check if the process start, but without any results.

I have had to use the AOMEI Partition software to do the same and without problems. The process of this software is very similar, you choose the origin and target disk, the system restart, but in this case, the clone process start.

I hope that Acronis solve this problem in a near future, becasue is frustating to pay for not working software.

I have the next environment:

ATI2017 - 5554

Windows 10 Professional on a i7 Inten CPU with 8Mb RAM.

Both disk connected directly with a SATA Cable, I mean, the new Crucial SSD was conected as a second HD.

Regards

0 Users found this helpful

Mario, thank you for bringing this topic to the ATIH 2017 Forum rather than the one for obsolete products.

Cloning with Acronis True Image should not be performed from within Windows for this precise reason - doing so causes Acronis to create a temporary Linux OS boot environment from which to lauch the clone operation.  Many modern systems do not support booting from Linux, especially if they have UEFI and Secure Boot and this can lead to an unbootable system if the UEFI bootloader configuration is changed and then not restored after the clone has been attempted.

The Acronis bootable Rescue Media should always be used for any Clone operations, and then you have a choice of two different versions for this Rescue Media - the default version uses the same Linux OS as when attempting to do the clone from within Windows, so may not work for you either - then you can also make the Windows PE version of the Rescue media which will work on all systems, including UEFI with Secure Boot - this uses the Windows 10 ADK for full compatibility with UEFI, Secure Boot and most modern hardware.

AOMEI also uses Windows PE media for performing clone operations, so you should try comparing like with like in this respect.

Another very important point - when doing a clone, you should remove the source drive and replace with the new target drive with this connected to the same port connector as the source was.  The source drive should be connected as a second drive and should always be removed before attempting to boot the cloned drive into Windows.  Both drives, when cloned are identical, including disk signatures - Windows may be corrupted by this if you boot with two identical drives / signatures.

Finally, last but should really be first.  Make a full disk backup of the source drive before attempting a clone.  Better to be safe than sorry when something goes wrong, with a backup you have an alternative way of recovering, plus you can use Backup and Restore as an alternative to using cloning, something that many of the MVP's strongly recommend doing instead of cloning.

Steve Smith wrote:

Finally, last but should really be first.  Make a full disk backup of the source drive before attempting a clone.  Better to be safe than sorry when something goes wrong, with a backup you have an alternative way of recovering, plus you can use Backup and Restore as an alternative to using cloning, something that many of the MVP's strongly recommend doing instead of cloning.

This is step is highly recommended. I always create a one-off backup before cloing, or doing a major udpate to Windows 10 (which have a propensity to go badly wrong).

Ian

Ditto, it's recommended in the documenation as well:

FAQ about backup, recovery and cloning

  • What is the best way to migrate the system to a new disk: cloning or backup and recovery? - The backup and recovery method provides more flexibility. In any case, we strongly recommend to make a backup of your old hard disk even if you decide to use cloning. It could be your data saver if something goes wrong with your original hard disk during cloning. For example, there were cases when users chose the wrong disk as the target and thus wiped their system disk. In addition, you can make more than one backup to create redundancy and increase security.