Direkt zum Inhalt

[SOLVED] LINUX RECOVERY - UEFI Recovery environment will not boot if Diskdirector 12 is integrated

Thread needs solution

ATIH b6029

I was about to test if Acronis fixed the issue that Diskdirector was flagged as DEMO in the Linux recovery environment.

After creating a new and fresh Boot medium I am not longer able to boot up any of the listed applications (Diskdirector 12 b3234 / Acronis 2016 b6029)

The behaviour is permanent and reproducible on 2 computers.

This may concur with the reason for this sporadic problem aswell: http://forum.acronis.com/forum/97398

pardon, forgot the attachment.

 

After some seconds the booloader will terminate and startup Windows normally, so sorry for the blurry pic. I think you can still read the code.

 

I tried to use the media creator of DD12 aswell as the recovery creator integrated in ATIH 2016.

Anhang Größe
20151210_032554.jpg 1.57 MB
0 Users found this helpful

i was able to reproduce the computer with the USB stick on other computers. I thought the issue could be that it is a 64GB USB 3.0 that is using exFAT instead FAT32, so I made a classic medium using DVD-RW. Same problem. In this case I would like to say that this is an error in the software, possibly again (just) with several Asus Z77 boards, however it is reproducible for me. Currently I have no other mainboard / chipset combination at hand.

I think I can test the Linux Recovery behaviour on 2 completely different UEFI supported Laptops (HP and Dell) this weekend.

 

Hello Acronis,

I can reproduce the issue on 2 different Asus Z77 Chipset mainboards, on a HP Laptop and Dell Laptop the problems does not exist.

Shall I request a fix from Asus?

I have unloaded and reloaded the secure boot keys on both Mainboardboards but still the Z77 mainboard (I have 3) are causing issues. Not anymore permanent but often enough.

I have contacted the ASUS Support Germany. The answer was plain: They do not support any other OS than Windows. In case I have any issues with UEFI (which I clearly see in the implementation as the error is mostly reproducible on my Z77 Asus boards) they feel not responsible but point me to Acronis Support.

I have reset the Secure boot keys configuration and things got better. Not sure why this happened in the first place but I will mark this as solved as long it is not permanently reproducible anymore.