Skip to main content

Cloning in BIOS issue

Thread needs solution

I have a bit of a problem.

I'm cloning my 120gb SSD from intel to an Kingston HyperX 3k 240gb. I detatch all other HDD in order to get the cloning program working. However, once I'm done cloning and reattach the other HDD it still sends me into the Cloning in Bios. When I decline the cloning, my SSD ( Kingston ) gets corrupted. I've tried to fix it by deleting Acronis, but it still sends me into Cloning in bios, and corrupts my SSD! Help?!

0 Users found this helpful

Clone should be used only by advanced users who know what they are doing. It is riskier and can result in a loss of data and a failed system. Use a full disk backup and restore, as it's far safer.

My best advice: Do not Clone! Instead, do one extra step and create a full disk Backup to an external drive. If ever you need to return to that image state, you would do a full disk Restore/Recovery.

There is rarely a need to Clone. Really, Backup is safer and more flexible. Many users encounter problems Cloning which they would not have if they had instead used Backup.

1. Don't use Clone. Do a full disk mode Backup, selecting the entire disk, and a Restore. The end result will be the same as Clone, but with many advantages.

2. Check out the many user guides and tutorials in the left margin of this forum, particularly Getting Started and Grover's True Image Guides which are illustrated with step-by-step screenshots.
29618: Grover's new backup and restore guides http://forum.acronis.com/forum/29618

A full disk backup, selecting the disk checkbox rather than individual partitions, includes everything. It includes everything that a clone would include.

The difference is that while a clone immediately writes that information a single time to another drive, a backup is saved as a compressed .tib archive. As such, multiple .tib archives may be saved to a single backup drive, allowing for greater redundancy, security and flexibility.

Once a full disk image .tib archive is restored to a drive, the result is the same as if that drive had been the target of a clone done on the date and time that the backup archive was created.

Clone is riskier because we've seen situations where users mistakenly choose the wrong drive to clone from and to, thus wiping out their system drive.

For non-advanced users with UEFI/GPT I would like to recommend cloning - using TIH2013 bootable disk Build 6528
which I did - as noted here successfully
http://forum.acronis.com/forum/42588#comment-136786
It is best to have the new Drive in place where it is meant to be and the old drive in an external case.......