Aller au contenu principal

[CRASH] LINUX RECOVERY - Linux UEFI bootloader still causes exception

Thread needs solution

ATIH 2016 b5518

As reported during the beta (http://forum.acronis.com/forum/95580) the problem that the Linux UEFI bootloader will terminate still happens (quite often).

Fichier attaché Taille
20150824_124950.jpg 641.89 Ko
0 Users found this helpful

ATIH 2016 b5634

I can now reproduce the issue:

Prerequisites:
CSM disabled
Secure Boot enabled
so full UEFI support is forced and no non UEFI compliant devices can be booted.

0. Create an ATIH Linux recovery on an USB stick
1. insert ATIH medium into USB
2. restart computer
3. enter Asus UEFI
4. in the boot tab select the USB stick that contains the Acronis Linux recovery in the section "boot override"
5. After the Linux bootloader has loaded, select "c. contiunue boot" to return to the Asus UEFI setup.
repeated steps 4-5 until this exception came up (It will come up also without these steps on a normal boot but not so reproducible)

Fichier attaché Taille
303288-123061.jpg 3.12 Mo
303288-123064.jpg 3.61 Mo

was able to reproduce the issue on a different computer (Lenovo G500S) but this one has some other issues with UEFI compatibility.
In addition to the error message he reports that the UEFI signature is not valid or something similar. Unfortunately I haven't taken a photo.

I was able to reproduce this with B6027 but so far I can see the bootloader has the same compilation (version number) so I cannot expect a change.

Affected mainboards:

Asus P8Z77-V, latest BIOS

Asus P8Z77-I Deluxe WD, latest BIOS

 

Hello Acronis Support Team,

I am still able to repro this issue on my Asus Z77 boards (have 3). Thankfully there is a 40% chance to get this error, and 60% to still pass and launch ATIH, otherwise I wouldn't be able to use ATIH Linux recovery anymore.

As today I am generally testing things in the linux recovery env. I had this issue quite often. Just a feeling it happens more often after a warm  reboot/ reset and less likely on a cold boot - if this helps.

However it does not make a difference if external drives are connected like USB sticks or HDDs. It will also happen often enough when just the Linux boot medium (USB 3.0, UEFI) is connected to load ATIH.

I have also discovered a small difference in the output depending the Linux Recovery medium was created using the lastest DD 12 build or the latest ATIH 2016 build. The one build with ATIH 2016 displays more information regarding it is 64 bit and the version number of the bootloader.

Fichier attaché Taille
330293-125800.jpg 641.89 Ko
330293-125803.jpg 1.52 Mo

Hello Karl,

Thank you for detailed reports and screenshots. Although the problem could be reproducing only on certain computer models, there is also a chance of incorrectly installed/updated Acronis True Image 2016 and Acronis Disk Director 12 which can result in different/incompatible versions of boot files in bootable media. To exclude that factor I suggest you to download pre-made ISO images of both programs from your account at https://www.acronis.com/my/products/ and burn them separately as two CD/DVD discs. If the problem with booting will be reproducing, could you please send us system report(s) from affected media(s) through a support ticket at http://www.acronis.com/support/?

Regards,

Slava

Hello Slava, I haven't tried the pre-made ISOs yet due to time constraints, but I recently I had a same problem on a different computer again.

It was a Zotac ZBOX ID-80 (plus) based on an older Intel Chipset and Atom Processor. The UEFI integration was not really good I would say so, as I was not able to boot / install Windows 10 using UEFI and the installation with secure boot (GPT) wasn't possible at the end. This mainboard also caused an exception when loading ATIH from a CD. The non UEFI version worked fine. I guess except my report this will not contribute to find the issue as I haven't made any screens or system reports because I was in hurry to get this system running.

I am looking into the pre made ISOs next time. (not soon I think, as I am unfortnately very busy these days)