Skip to main content

recovery program crashing

Thread needs solution

I have tried 3 forms of the 2019 linux recovery disk. Vanilla writing to a usb stick. Writing to an iso and burning a cd. And finally... writing to an iso and then creating a usb with rufus. For this I specify uefi, and it seems to boot up in uefi although the pc says its a mbr drive. So I'm not sure exactly what's happening there.

 

Anyway, they all boot up fine. It all works until I try to restore a volume. I am able to select the archive file I wish to restore, then it lets me choose which volumes I want to restore. It should then ask me where I want to restore it to, but I never get that far. The window stays up, but it is blank, and hitting any key or pressing the mouse just makes the pc beep and there is no response.

 

I just have to hit reset on the pc at this point.

It does this with all 3 versions of my restore disk.

 

I am able to restore 2015 image backups with the 2015 recovery disk fine. No problems there. I haven't tried restoring a 2019 image with the 2015 recovery disk. If that works I can keep on using 2019 to create backups. Is 2019 backward compatible with the 2015 recovery disk?

 

The 2015 restore usb shows up as mbr, and my hard disk shows up as gpt partitioned.

 

Anyway I would like to get 2019 working. I guess there's something odd about my pc since surely you have it working in house.

Thanks.

0 Users found this helpful

So I tried out making a win pe disk.

First I made a usb drive and booted that.

I actually got to the next screen "specify recover settings of partition C", but when I clicked on "new location" the program hung. No beeping this time, but I had to reboot.

 

So for my next trick I thought I would try writing an iso image and then creating a bootable uefi usb with rufus. It shows up in partition aster as a uefi disk, and it booted fine.

Unfortunately same result. Hung in the same place.

 

I guess there is something about my partitions that it doesn't like. I posted a link of what is displayed in easus partition master. You can see it here...

https://drive.google.com/file/d/1th25jWdOJVUYrR1ILFhrwDWRz3LAUSTj/view?…

 

I suppose I could repartition my drive 0 and hope for the best but it shouldn't be necessary. As I said, recovery disk from ATI 2015 works perfectly, so there is clearly some issue with the 2019 version.

I guess in the meantime I'll just go back to 2015. Not happy.

 

Richard, welcome to these public User Forums.

Sorry to hear of the issues you have found in trying to recover your drive with ATI 2019.

Your image of your partitions show that you have a UEFI / GPT drive with an EFI System partition therefore any rescue media needs to be booted in UEFI mode if you want to have a bootable OS after doing a recovery.

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media - for more information on boot modes.

The recommended method of creating the ATI 2019 rescue media is by using the Simple method for the rescue media builder tool which creates WinPE media based on your computer Windows Recovery Environment, which in turn should have support for all your devices that are installed.

See KB 61632: Acronis True Image 2019: how to create bootable media

Note: you should not need to use third party tools like Rufus to create bootable USB media, the built in tool is more than capable of doing this directly without any need to create ISO files etc.
The key point with USB media is that it should be 32GB or less in size, and has to be FAT32 format.

Your ATI 2015 rescue media may work fine with your ATI 2019 backup image but this is not guaranteed as Acronis only publish backwards compatibility information, not forward compatibility.
It is very possible for Acronis to introduce changes in newer versions of the application that would not be compatible with rescue media from an older version, but where the new rescue media can handle files from older versions just fine.

When doing the recovery from the rescue media, it is recommended that you disconnect all other drives that are not required for the recovery, and if not recovering from a network drive or cloud, it can also help to disconnect from the network.  This is because the media has a habit of scanning any connected drives and also across network connections looking for any other .tib files, which can cause delays in the process that may look like the application is hanging.

How long have you waited after clicking on the option to select the new location for the recovery to write to?

What version of Windows OS is being recovered here?

That worked. (but read on please)

 

I guess it was my fault for not waiting long enough for it to respond.

Though perhaps I can be forgiven since it took 8 minutes staring at a blank window.

Perhaps you need to display some activity indicator when it is searching through the partitions before you choose where to restore to. Or at the very least say "busy, this could take a while".

the 2015 recovery media comes back straight away, so perhaps something is not quite right.

 

Haven't actually tried a restore yet, but it is past the part where it was "hanging" so I'll assume it is working and test it on a restore later.

 

thanks for your help.

Perhaps you need to display some activity indicator when it is searching through the partitions before you choose where to restore to. Or at the very least say "busy, this could take a while".

Richard, you should submit Feedback using the tool provided in the ATI GUI to make your concerns known directly to Acronis.  We are just users here in the forums, even the MVP's