| Summary: | Unable to install Grub2 when installing Mageia 8 EFI | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Ange Karu <dieux> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | High | CC: | davidwhodgins, lewyssmith, ouaurelien |
| Version: | 8 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://www.mageia.org/fr/downloads/ | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Ange Karu
2021-04-21 02:23:33 CEST
Ange Karu
2021-04-21 02:25:48 CEST
Priority:
Normal =>
High Two most likely causes: - Secure boot has not been disabled, preventing the installer from updating the boot entries in nvram. - The install iso was booted in legacy bios mode. When booting from an iso the efi boot menu will usually display two entries. One for booting in legacy bios mode, and one booting in uefi mode. The wording and presence of both menu entries varies between manufacturers. CC:
(none) =>
davidwhodgins Also check that the vfat partition mounted at /boot/EFI is not full. @Dave: thanks for your comments. @Ange : Sorry for your problem. Please say which ISO you are using. And if you have any other access to the system, the output of: # gdisk -l (if GPT disc) or # fdisk -l (if MBR disc) plus $ inxi -MSDop To get you going, if your machine has 64-bit EFI firmware (normal, but it can be 32-bit) - go for rEFInd rather than Grub2; unless you have a good reason for wanting the latter. CC:
(none) =>
lewyssmith
Aurelien Oudelet
2021-04-22 22:08:43 CEST
CC:
(none) =>
ouaurelien @reporter, can you answer Comment 3, please? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you. (I also wonder if this not a duplicate of Bug 28835... Here is beginning of 28835 report: > grub2-install failed: Installing for x86_64-efi platform. > grub2-install: error: cannot find EFI directory. > ...propagated at /usr/lib/libDrakX/any.pm line 278. > ...propagated at /usr/libexec/drakboot line 49. > Perl's trace: > drakbug::bug_handler() called from /usr/libexec/drakboot:49 See same error, same line number... Reporter in Bug 28835 has 'noauto' in its ESP line of /etc/fstab... ) Keywords:
(none) =>
NEEDINFO I do not think that this bug is a duplicate of 28835. The Grub error messages are not the same: here: grub2-install failed: Installation pour la plate-forme x86_64-efi. Could not prepare Boot variable: Function not implemented grub2-install : erreur : efibootmgr n'a pas réussi à enregistrer l'entrée de démarrage: Erreur d'entrée/sortie. which indicates a failure to write to NVRAM. there: grub2-install failed: Installing for x86_64-efi platform. grub2-install: error: cannot find EFI directory. which is quite different. This failure to write to NVRAM rings a bell, and would effect the use of rEFInd as well. It might be related to 'difficult' EFI firmware, or, as Dave suggested, not unsetting 'secure boot'. We really do need some information about the system. If it was possible to get the journal from the installation session, that would help. (In reply to Lewis Smith from comment #5) > I do not think that this bug is a duplicate of 28835. The Grub error > messages are not the same: > here: > grub2-install failed: Installation pour la plate-forme x86_64-efi. > Could not prepare Boot variable: Function not implemented > grub2-install : erreur : efibootmgr n'a pas réussi à enregistrer l'entrée > de démarrage: Erreur d'entrée/sortie. > which indicates a failure to write to NVRAM. > > there: > grub2-install failed: Installing for x86_64-efi platform. > grub2-install: error: cannot find EFI directory. > which is quite different. > > This failure to write to NVRAM rings a bell, and would effect the use of > rEFInd as well. It might be related to 'difficult' EFI firmware, or, as Dave > suggested, not unsetting 'secure boot'. We really do need some information > about the system. If it was possible to get the journal from the > installation session, that would help. Right. Seems a bogus UEFI which refuses to accept new OS loader. @ reporter, can you install Mageia 8 with an UEFI system or a previous version? Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you. Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Resolution:
(none) =>
OLD |