Version-Release number of selected component: anaconda-22.20.13-1 The following was filed automatically by anaconda: anaconda 22.20.13-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1610, in install raise BootLoaderError("boot loader install failed") File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1625, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2372, in writeBootLoaderFinal storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2450, in writeBootLoader writeBootLoaderFinal(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 266, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 244, in run threading.Thread.run(self, *args, **kwargs) BootLoaderError: boot loader install failed Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22-x86_64 rd.live.check quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 22
Created attachment 1034873 [details] File: anaconda-tb
Created attachment 1034874 [details] File: anaconda.log
Created attachment 1034875 [details] File: dnf.log
Created attachment 1034876 [details] File: dnf.rpm.log
Created attachment 1034877 [details] File: environ
Created attachment 1034878 [details] File: lsblk_output
Created attachment 1034879 [details] File: nmcli_dev_list
Created attachment 1034880 [details] File: os_info
Created attachment 1034881 [details] File: storage.log
Created attachment 1034882 [details] File: syslog
Created attachment 1034883 [details] File: ifcfg.log
Created attachment 1034884 [details] File: packaging.log
Created attachment 1034885 [details] File: program.log
Do you still have this install attempt available? If so, I'd like to see the output from 'parted -s /dev/sda u s p free' It looks like grub2 didn't recognize the biosboot partition: 21:38:22,062 INFO program: Running... grub2-install --no-floppy /dev/sda 21:38:30,233 INFO program: Installing for i386-pc platform. 21:38:30,234 INFO program: grub2-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. 21:38:30,234 INFO 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.. 21:38:30,234 INFO program: grub2-install: error: will not proceed with blocklists. 21:38:30,235 DEBUG program: Return code: 1 And yet, it looks like it was created: 21:32:58,389 INFO blivet: executing action: [313] create format biosboot on partition sda1 (id 6) 21:32:58,391 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 1 ; 21:32:58,392 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 2 ; 21:32:58,393 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 3 ; 21:32:58,395 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 4 ; 21:32:58,396 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 5 ; 21:32:58,397 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 6 ; 21:32:58,398 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 8 ; 21:32:58,400 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 9 ; 21:32:58,401 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 10 ; 21:32:58,402 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 11 ; 21:32:58,403 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 13 ; 21:32:58,404 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 14 ; 21:32:58,406 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 15 ; 21:32:58,407 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 16 ; 21:32:58,408 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 17 ; 21:32:58,409 DEBUG blivet: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 18 ; 21:32:58,411 DEBUG blivet: PartitionDevice.setFlag: path: /dev/sda1 ; flag: 12 ; 21:32:58,413 DEBUG blivet: DiskLabel.commitToDisk: device: /dev/sda ; numparts: 3 ; 21:32:58,601 DEBUG blivet: PartitionDevice.setup: sda1 ; status: True ; controllable: True ; orig: False ; 21:32:58,603 DEBUG blivet: BIOSBoot.create: device: /dev/sda1 ; status: False ; type: biosboot ; 21:32:58,632 DEBUG blivet: PartitionDevice.updateSysfsPath: sda1 ; status: True ; 21:32:58,633 DEBUG blivet: sda1 sysfsPath set to /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
Another user experienced a similar problem: Clean installation on Lenovo Thinpad x230i HDD - Smartbuy Ignition 2 (Physon chip). Anaconda throws error "boot loader install failed". BIOS - tried both UEFI, Legacy. Tried Fedora 22 netinstall, Live XFCE. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Xfce-x86_64-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: python-libs-2.7.9-6.fc22.x86_64 package: anaconda-core-22.20.13-1.fc22.x86_64 product: Fedora reason: BootLoaderError: boot loader install failed release: Fedora release 22 (Twenty Two) version: 22
I got the "boot loader install failed" error installing Fedora 22 onto a GPT partitioned Intel RAID-1 volume. Manually installing the boot loader via grub2-install also failed and led me to discover that Anaconda had not set the bios_grub flag on the bios_boot partition. After setting that with parted, grub2-install completed successfully and the system was able to boot.
Another user experienced a similar problem: Trying to install Fedora LXDE 22 in a Virtualbox VM, replacing an existing Gentoo VM. Told installer to delete existing partitions on /dev/sda Installer failed when attempting to install bootloader. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-LXDE-x86_64-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: python-libs-2.7.9-6.fc22.x86_64 package: anaconda-core-22.20.13-1.fc22.x86_64 product: Fedora reason: BootLoaderError: boot loader install failed release: Fedora release 22 (Twenty Two) version: 22
Another user experienced a similar problem: Attempting to install using a usb boot disk created with the network install iso. I couldn't find the pxe boot file to just do it with a network boot... that would be nice... but that is not really pertinent to this issue. This is simply an installation attempt... the second attempt. I used dd to copy the iso image to the usb disk... it booted and ran through the installation fine both times. Only issue is installing the boot loader. I have alt-tab'd to another terminal and attempted manual installation of grub2... no joy whatsoever... sigh... Fedora 22 Server Netboot addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22-x86_64 quiet hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 package: anaconda-22.20.13-1 product: Fedora reason: BootLoaderError: boot loader install failed release: Cannot get release name. version: 22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.