Salta al contenuto principale

Restoring to dissimilar hardware fails

Thread needs solution

Hello fellow Acronis users!

Here's my scenario:
Used a True Image 2014 backup to restore to different hardware (from an Optiplex 790 to an Optiplex 7010); selected the option to use universal restore, and then specified a folder where I had extracted all necessary drivers (extracted all .zip files and ran all .exe to get the raw files).

The restore completes without any error, so I start thinking things are good. The moment Windows goes to boot, however, it goes straight into Startup recovery. No BSOD is shown, and no error messages are provided. After a length period of time, Startup recovery returns that it is unable to repair Windows.

I've ran the tool multiple times and cannot seem to get past this.

Any suggestions?

Thanks,

Nicholas

0 Users found this helpful

Perhaps there is something here.

https://kb.acronis.com/content/34283

GroverH wrote:

Perhaps there is something here.

https://kb.acronis.com/content/34283

Apologies, but I probably should have mentioned in my original post that I had tried the restore again using the linked KB article. Unfortunately it had no impact on the restore.

This may also be worth noting, but once System Startup Recovery ran, I launched a command prompt to take a look at things...

Oddly, it showed Windows as being installed on a D partition with the recovery partition being on C. This definitely is not what I chose during the recovery process, so I'm not sure what the cause/solution is...

Nicholas

Just as an update, so far I still haven't found any solutions- for now, we've switched over to different hardware (we have a separate BD backup meant for that hardware, so there were no issues restoring that image).

I also experimented with GParted to ensure the partitions were properly destroyed prior to restoring the image. This did not seem to affect the outcome of the restore. Acronis still shows no error messages or warnings & Windows fails to start each time (even after letting Windows attempt to repair the issue). If I happen to discover solution, I'll be sure to post it here.

njnatale wrote:

Oddly, it showed Windows as being installed on a D partition with the recovery partition being on C. This definitely is not what I chose during the recovery process, so I'm not sure what the cause/solution is...

You should add a recognizable label to every disk, so you can uniquely identify it without the drive letter. When recovering a disk or partition image, it's recommended to do so from the ATI bootable Rescue Media. As the Rescue Media is based on Linux, disks will enumerate differently so that E: in Windows may not be E: in the Rescue Media. That's why you need to be able to identify each partition by name, not by letter.