Bug 15823 - drakboot crashed (grub2-install failed: Installing for x86_64-efi platform. error : cannot find EFI directory)
Summary: drakboot crashed (grub2-install failed: Installing for x86_64-efi platform. e...
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
: 15788 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-05-02 14:39 CEST by Roland Gillard
Modified: 2015-05-04 12:31 CEST (History)
3 users (show)

See Also:
Source RPM: drakxtools-16.86-1.mga5
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Roland Gillard 2015-05-02 14:39:01 CEST 
The "drakboot" program crashed. Drakbug-16.86 caught it.

configure the boot from mcc.
I installed grub2efi before (after desinstalling grub2)

grub2-install failed: Installing for x86_64-efi platform.
grub2-install : erreur : cannot find EFI directory.
	...propagated at /usr/lib/libDrakX/any.pm line 264.
	...propagated at /usr/libexec/drakboot line 64.
Perl's trace:
drakbug::bug_handler() called from /usr/libexec/drakboot:64

Theme name: oxygen-gtk
Kernel version = 3.19.4-desktop-2.mga5
Distribution=Mageia release 5 (Cauldron) for x86_64
CPU=AMD A6-5200 APU with Radeon(TM) HD Graphics
Comment 1 Thierry Vignaud 2015-05-02 18:12:10 CEST 
Why are you doing that?
If we selected grub2, it's because it's the bootloader tagergeting your machine.
Installing grub2-efi on a no UEFI machine won't work.

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => INVALID
Summary: drakboot crashed => drakboot crashed (grub2-install failed: Installing for x86_64-efi platform. error : cannot find EFI directory)

Comment 2 Roland Gillard 2015-05-03 09:45:13 CEST 
My hp15N is an EFI machine. mcc launched grub2 and drakboot crached: bug 15788.
As said in the comments there, I wished to test grub2-efi and thinking that it was the correct option. I add a complete summary in comment 10

IMPORTANT :  <<cannot find EFI directory>> is very surprising because 
 that  the /BOOT/EFI empty directory does exist (in order to mount
the sda2 partition where the EFI boot processes are pesent).


It is my intent (on monday) to do a third test with a CLEAN Mga5RC install 
and no longer UPDATE the legacy grub distribution Mga4.1

Status: RESOLVED => UNCONFIRMED
Resolution: INVALID => (none)
Ever confirmed: 1 => 0

Comment 3 Samuel Verschelde 2015-05-03 10:31:48 CEST 
Seems a valid bug report indeed. I'm not sure QA has tested this situation, Mageia 4.1 installed on EFI (I suppose you followed the wiki page about this, since the installer did not automated this?) upgraded to Mageia 5.

Status: UNCONFIRMED => NEW
CC: (none) => qa-bugs, tmb
Ever confirmed: 0 => 1

Comment 4 Thierry Vignaud 2015-05-03 10:42:19 CEST 
You changed what we installed and was working.

Switching from !UEFI to UEFI on upgrade is not supported.
If you manually shoot yourself in the foot, we cannot help you.

If you want a pure UEFI install, you must perform a new install.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Comment 5 Thierry Vignaud 2015-05-03 10:42:50 CEST 
You changed what we installed and was working.

Switching from !UEFI to UEFI on upgrade is not supported.
If you manually shoot yourself in the foot, we cannot help you.

If you want a pure UEFI install, you must perform a new install.
Comment 6 Thierry Vignaud 2015-05-03 10:42:56 CEST 
*** Bug 15788 has been marked as a duplicate of this bug. ***
Comment 7 Samuel Verschelde 2015-05-04 12:31:02 CEST 
*** Bug 15788 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.