Description of problem: Installing Fedora21-Workstation-Beta-RC1-x86_64 in my PC with EFI. I added gpt to the boot options to make the partitions with GPT. I choosed Btrfs partitions, everything else on defaults. When the installation process was configuring the boot loader, this error prompted. Version-Release number of selected component: efibootmgr-0.7.0-5.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: efibootmgr crash_function: vars_get_variable executable: /mnt/sysimage/usr/sbin/efibootmgr kernel: 3.17.1-302.fc21.x86_64 os_release_in_rootdir: Fedora release 21 (Twenty One) rootdir: /mnt/sysimage runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #0 vars_get_variable at vars.c:165 #1 efi_get_variable at lib.c:94 #2 read_vars at src/efibootmgr/efibootmgr.c:108
Created attachment 951566 [details] File: backtrace
Created attachment 951567 [details] File: cgroup
Created attachment 951568 [details] File: core_backtrace
Created attachment 951569 [details] File: environ
Created attachment 951570 [details] File: exploitable
Created attachment 951571 [details] File: limits
Created attachment 951572 [details] File: maps
Created attachment 951573 [details] File: open_fds
Created attachment 951574 [details] File: os_info_in_rootdir
Created attachment 951575 [details] File: proc_pid_status
Created attachment 951576 [details] File: var_log_messages
Another user experienced a similar problem: While installing Fedora 21 Beta 4 on an UEFI system the installation process paused after software installation and then prompted if to ignore this error. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: efibootmgr crash_function: vars_get_variable executable: /mnt/sysimage/usr/sbin/efibootmgr kernel: 3.17.1-302.fc21.x86_64 os_release_in_rootdir: Fedora release 21 (Twenty One) package: efibootmgr-0.7.0-5.fc21 reason: efibootmgr killed by SIGSEGV rootdir: /mnt/sysimage runlevel: N 5 type: CCpp uid: 0
Hi, in case it helps, I had the same issue (efi, btrfs), I think I found why: efivars are not mounted on sysimage. After install process, I mounted efivarfs on sysimage like that: $ sudo mount -t efivarfs none /mnt/sysimage/sys/firmware/efi/efivars Then I chroot with install mounted file system on /mnt/sysimage and installed grub-efi, grub-efi-modules, efivars: $ sudo chroot /mnt/sysimage /bin/bash $ yum install grub2-efi grub2-efi-modules efivars Finaly "yum update" installed the newest kernel which had automatically updated the boot and fix the matter.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.