Description of problem: Received error about not being able to install the boot loader. Version-Release number of selected component: anaconda-28.22.10 The following was filed automatically by anaconda: anaconda 28.22.10 exception report Traceback (most recent call first): File "/usr/lib64/python3.6/site-packages/pyanaconda/bootloader.py", line 1611, in install raise BootLoaderError("boot loader install failed") File "/usr/lib64/python3.6/site-packages/pyanaconda/bootloader.py", line 1626, in write self.install() File "/usr/lib64/python3.6/site-packages/pyanaconda/bootloader.py", line 2473, in writeBootLoaderFinal storage.bootloader.write() File "/usr/lib64/python3.6/site-packages/pyanaconda/bootloader.py", line 2552, in writeBootLoader writeBootLoaderFinal(storage, payload, instClass, ksdata) File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 438, in run_task self._task(*self._task_args, **self._task_kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 472, in start self.run_task() File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 304, in start item.start() File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 304, in start item.start() File "/usr/lib64/python3.6/site-packages/pyanaconda/installation.py", line 361, in doInstall installation_queue.start() File "/usr/lib64/python3.6/threading.py", line 864, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 291, in run threading.Thread.run(self) pyanaconda.bootloader.BootLoaderError: boot loader install failed Additional info: addons: com_redhat_kdump, com_redhat_docker blivet-gui-utils.log: cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 rd.live.check quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.16.3-301.fc28.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 28 Potential duplicate: bug 1512205
Created attachment 1453278 [details] File: anaconda-tb
Created attachment 1453279 [details] File: anaconda.log
Created attachment 1453280 [details] File: dbus.log
Created attachment 1453281 [details] File: dnf.librepo.log
Created attachment 1453282 [details] File: environ
Created attachment 1453283 [details] File: hawkey.log
Created attachment 1453284 [details] File: lorax-packages.log
Created attachment 1453285 [details] File: lsblk_output
Created attachment 1453286 [details] File: nmcli_dev_list
Created attachment 1453287 [details] File: os_info
Created attachment 1453288 [details] File: program.log
Created attachment 1453289 [details] File: storage.log
Created attachment 1453290 [details] File: syslog
Created attachment 1453291 [details] File: ifcfg.log
Created attachment 1453292 [details] File: packaging.log
From program.log: 15:35:14,672 INF program: Running in chroot '/mnt/sysimage'... grub2-install --no-floppy /dev/vda 15:35:21,717 INF program: Installing for i386-pc platform. 15:35:21,719 INF program: grub2-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. 15:35:21,719 INF program: 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.. 15:35:21,720 INF program: grub2-install: error: will not proceed with blocklists. 15:35:21,720 DBG program: Return code: 1 Anaconda should catch this error earlier probably with the verify_gpt_biosboot check and show the following warning. I'm not sure why it fails to do that. "Your BIOS-based system needs a special partition to boot from a GPT disk label. To continue, please create a 1MiB 'biosboot' type partition."
*** Bug 1594514 has been marked as a duplicate of this bug. ***
*** Bug 1603592 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was trying to install on my ThinkPad X201 when I encountered this issue. addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img root=live:UUID=d75ce7f5-06a7-4efe-af95-fde6d7aec453 rd.live.image rw rd.live.overlay=UUID=d75ce7f5-06a7-4efe-af95-fde6d7aec453 rd.live.check quiet hashmarkername: anaconda kernel: 4.16.3-301.fc28.x86_64 other involved packages: python3-libs-3.6.5-1.fc28.x86_64 package: anaconda-core-28.22.10-1.fc28.x86_64 product: Fedora reason: pyanaconda.bootloader.BootLoaderError: boot loader install failed release: Fedora release 28 (Twenty Eight) version: 28
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/1619
*** Bug 1642785 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.