Direkt zum Inhalt

Acronis 12.5.9010 recovery problem

Thread needs solution

Hi,

After a successful "Entire Machine" backup from a simple workstation (Lenovo M710Q with a Samsung 256GB NVME M.2 PCIe SSD) we're having trouble executing the recovery.

From the AMS we go to backups, select the backup and start the recovery process. The remote machine reboots (It is a W10 machine) and when the Acronis loader should be starting and also starting the recovery process from it what we get is:

ApplicationFrameHost_2018-02-20_12-05-32.png

Nothing happens after. If you reboot the machine it loads again the OS correctly.

This is what we get in the AMS from the activity itself:

Terminals_2018-02-20_12-12-32.png

What is going on here?

Thanks in advance for your feedback.

 

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi,

The problem is that due to specifis of particular hardware, the Linux kernel used in Acronis Bootable Media environment (that's where the machine reboots into in order to perform recovery) does not boot properly. To properly investigate the issue you should contact our support team for assistance.

The workaround would be to perform recovery of this machine via WinPE-based Acronis Backup bootable media and add Windows drivers for NVME controller into it when prompted. This media can be created via Acronis Media Builder installed on any machine - there is corresponding option in its GUI.

Thank you.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

In addition to my previous reply: the tainted kernel event may also happen of the ramdisk files (used by Linux to boot up) are corrupted while activating them in the boot loader, so the issue may be related not to Linux-based bootable media, but to specific "restore with reboot" scenario.

To confirm you can try creating standard Linux-based media (instead of WinPE one) and see if it boots properly on this machine. This would help to localize the problem.

In either case my previous recommendation to contact support would be still valid.

Thank you.

Thank you so much Vasily, we already sent the ticket to support.

It is weird because I've just created an image of other M710Q workstation with the same SO and repeated the same steps. Everything worked like a charm... started the recovery from the AMS, the workstation rebooted and the Acronis loader started correctly, it recovered and booted perfect... And super fast to be honest...

I will update the thread if I find what could cause the problem with the first workstation.

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

One more tip which may be useful for investigation: the ramdisk files used to activate the boot loader are located in C:\Program Files\Common Files\Acronis\BackupAndRecoveryAgent\ folder on the client machine side - the agent_ramdisk64.dat file in this folder is the main core one.

If you have another similar workstation which doesn't show the same symptoms, then it would be worthy to check the files in that folder in order to compare them with the files on problematic workstation. Probably there could be some inconsistent files.

Thank you.

Hi Vasily,

I've checked the folder you mention and in both machines are exactly the same:

- 39 files

- 257,341,165 bytes

I'm not sure if I should look something specific, but at first sight they both look the same. Just one difference, the issued workstation has W10 in english and the working workstation has W10 in spanish, but I suppose it is not relevant at all :)

Thanks Vasily.

Hi Vasily,

we've reinstalled the corporative windows 10 image to the issued machine. We reinstalled the agent and backed up again.

When tried to recover, the same problem appeared... Kernel panic and no acronis loader at all... This is just for your information, the support case is already opened and we're waiting for the answer :)

Thanks!