| Summary: | bootloader not installing on UEFI based system (this GPT partition label contains no BIOS Boot Partition; embedding won't be possible) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Wim Coulier <wim> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | marja11, thierry.vignaud, zen25000 |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
modprobe.conf
fstab menu.lst device.map |
||
Created attachment 6931 [details]
modprobe.conf
Created attachment 6932 [details]
fstab
Created attachment 6933 [details]
menu.lst
Created attachment 6934 [details]
device.map
Rémi Verschelde
2015-08-15 10:41:35 CEST
Summary:
bootloader not installing on EUFI based system =>
bootloader not installing on UEFI based system This looks to me as though the install media is not being booted in UEFI mode and is therefore trying to install in MBR mode. Installing using grub (legacy) would not be an option if the installer was running in UEFI mode, only grub2 would be offered. Please read https://wiki.mageia.org/en/Installing_on_systems_with_UEFI_firmware and check that you are really booting the install media in UEFI mode. CC:
(none) =>
zen25000
Thierry Vignaud
2015-08-18 16:20:34 CEST
CC:
(none) =>
thierry.vignaud (In reply to Barry Jackson from comment #5) > This looks to me as though the install media is not being booted in UEFI > mode and is therefore trying to install in MBR mode. > Installing using grub (legacy) would not be an option if the installer was > running in UEFI mode, only grub2 would be offered. > Please read > https://wiki.mageia.org/en/Installing_on_systems_with_UEFI_firmware and > check that you are really booting the install media in UEFI mode. (In reply to Barry Jackson from comment #6) > Also read: > https://wiki.mageia.org/en/Mageia_5_Errata#UEFI_or_BIOS.2Flegacy_mode This report saw no action since the above comments, almost 9 months ago. Assuming the install medium had indeed not booted in UEFI mode. Closing. Status:
NEW =>
RESOLVED |
Description of problem: grub / grub2 => Installer is not able to install bootloader; drakboot is not able to install bootloader Version-Release number of selected component (if applicable): Mageia 5 64 grub / grub2 installers How reproducible: install mageia on affected system or install bootloader with Remark: EFI partition is mounted on /boot/EFI (Mount point: /boot/EFI; Device: sda2; Volume label: SYSTEM_DRV; Type: EFI System Partition; Size: 260MB (0%); Mounted) When trying the bootloader installation during OS installation, the installer gives the following response: An error occured grub2-install failed: installing for i386-pc platform grub2-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible grub2-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However blocklists are UNRELIABLE and their use is discouraged.. grub2-install: error: will not proceed with blocklists. ...propagated Result: not able to get a working Mageia 5, not with grub and not with grub2. Via the installation of Linux Mint in multi-boot I can boot Mageia (the Linux Mint grub2 installer does not give any errors and is able to boot Linux Mint and Mageia correctly, but not Windows). When trying to reinstall the Mageia bootloader via drakboot with default settings (not changing anything, it crashes with the following error: The "drakboot" program has crashed with the following error: grub2-install failed: grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory. ...propagated at /usr/lib/libDrakX/any.pm line 268. ...propagated at /usr/libexec/drakboot line 64. Perl's trace: drakbug::bug_handler() called from /usr/libexec/drakboot:64 Used theme: oxygen-gtk To submit a bug report, click on the report button. This will open a web browser window on Bugzilla where you'll find a form to fill in. The information displayed above will be transferred to that server Things useful to attach to your report are the output of the following commands: 'lspcidrake -v', 'blkid'. You should also attach the following files: /etc/modprobe.conf, /etc/fstab, /boot/grub/menu.lst, /boot/grub/devices.map as well as /etc/lilo.conf. Reproducible: Steps to Reproduce: