Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1804862 - pyanaconda.bootloader.base.BootLoaderError: Failed to set new efi boot target. This is most likely a kernel or firmware bug.
Summary: pyanaconda.bootloader.base.BootLoaderError: Failed to set new efi boot target...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: efibootmgr
Version: 32
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3c3b1f9b7853fed41db6eb285d0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-19 18:51 UTC by browseria
Modified: 2021-05-25 17:18 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:18:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (2.24 MB, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: anaconda.log (48.16 KB, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: dbus.log (3.10 KB, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: environ (658 bytes, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: journalctl (1.19 MB, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: lsblk_output (3.17 KB, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: lvm.log (375.80 KB, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: nmcli_dev_list (1.62 KB, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: os_info (762 bytes, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: program.log (147.78 KB, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: storage.log (341.24 KB, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details
File: packaging.log (276 bytes, text/plain)
2020-02-19 18:51 UTC, browseria
no flags Details

Description browseria 2020-02-19 18:51:33 UTC
Description of problem:
Accepting all the defaults when installing to a blank (never formatted/never partitioned) hard drive results in the following error:
```
The following error occurred while installing the boot loader. The system will not be bootable. Would you like to ignore this and continue with installation?

Failed to set new efi boot target. This is most likely a kernel or firmware bug.
```

Version-Release number of selected component:
anaconda-core-32.22-1.fc32.x86_64

The following was filed automatically by anaconda:
anaconda 32.22 exception report
Traceback (most recent call first):
  File "/usr/lib64/python3.8/site-packages/pyanaconda/bootloader/efi.py", line 75, in _add_single_efi_boot_target
    raise BootLoaderError("Failed to set new efi boot target. This is most "
  File "/usr/lib64/python3.8/site-packages/pyanaconda/bootloader/efi.py", line 80, in add_efi_boot_target
    self._add_single_efi_boot_target(self.stage1_device)  # pylint: disable=no-member
  File "/usr/lib64/python3.8/site-packages/pyanaconda/bootloader/efi.py", line 123, in install
    self.add_efi_boot_target()
  File "/usr/lib64/python3.8/site-packages/pyanaconda/bootloader/efi.py", line 113, in write
    self.install()
  File "/usr/lib64/python3.8/site-packages/pyanaconda/bootloader/installation.py", line 188, in install_boot_loader
    storage.bootloader.write()
  File "/usr/lib64/python3.8/site-packages/pyanaconda/bootloader/installation.py", line 53, in write_boot_loader
    install_boot_loader(storage)
  File "/usr/lib64/python3.8/site-packages/pyanaconda/installation_tasks.py", line 451, in run_task
    self._task(*self._task_args, **self._task_kwargs)
  File "/usr/lib64/python3.8/site-packages/pyanaconda/installation_tasks.py", line 485, in start
    self.run_task()
  File "/usr/lib64/python3.8/site-packages/pyanaconda/installation_tasks.py", line 306, in start
    item.start()
  File "/usr/lib64/python3.8/site-packages/pyanaconda/installation_tasks.py", line 306, in start
    item.start()
  File "/usr/lib64/python3.8/site-packages/pyanaconda/installation_tasks.py", line 306, in start
    item.start()
  File "/usr/lib64/python3.8/site-packages/pyanaconda/installation.py", line 403, in run_installation
    queue.start()
  File "/usr/lib64/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.8/site-packages/pyanaconda/threading.py", line 280, in run
    threading.Thread.run(self)
pyanaconda.bootloader.base.BootLoaderError: Failed to set new efi boot target. This is most likely a kernel or firmware bug.

Additional info:
addons:         com_redhat_kdump
blivet-gui-utils.log: 
cmdline:        /usr/bin/python3  /sbin/anaconda --liveinst --method=livecd:/dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-32-20200218-n-0 rd.live.image quiet
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         5.6.0-0.rc2.git0.1.fc32.x86_64
other involved packages: python3-libs-3.8.2~rc1-1.fc32.x86_64
product:        Fedora
release:        Fedora release 32 (Thirty Two)
release_type:   pre-release
type:           anaconda
version:        32

Potential duplicate: bug 1779716

Comment 1 browseria 2020-02-19 18:51:38 UTC
Created attachment 1664126 [details]
File: anaconda-tb

Comment 2 browseria 2020-02-19 18:51:39 UTC
Created attachment 1664127 [details]
File: anaconda.log

Comment 3 browseria 2020-02-19 18:51:40 UTC
Created attachment 1664128 [details]
File: dbus.log

Comment 4 browseria 2020-02-19 18:51:41 UTC
Created attachment 1664129 [details]
File: environ

Comment 5 browseria 2020-02-19 18:51:44 UTC
Created attachment 1664130 [details]
File: journalctl

Comment 6 browseria 2020-02-19 18:51:45 UTC
Created attachment 1664131 [details]
File: lsblk_output

Comment 7 browseria 2020-02-19 18:51:47 UTC
Created attachment 1664132 [details]
File: lvm.log

Comment 8 browseria 2020-02-19 18:51:48 UTC
Created attachment 1664133 [details]
File: nmcli_dev_list

Comment 9 browseria 2020-02-19 18:51:49 UTC
Created attachment 1664134 [details]
File: os_info

Comment 10 browseria 2020-02-19 18:51:50 UTC
Created attachment 1664135 [details]
File: program.log

Comment 11 browseria 2020-02-19 18:51:52 UTC
Created attachment 1664136 [details]
File: storage.log

Comment 12 browseria 2020-02-19 18:51:53 UTC
Created attachment 1664137 [details]
File: packaging.log

Comment 13 browseria 2020-02-20 22:40:27 UTC
Same problem also occurs on Fedora-Workstation-Live-x86_64-32-20200220.n.0.iso, Fedora-Workstation-Live-x86_64-32-20200218.n.0.iso and Fedora-Workstation-Live-x86_64-32-20200214.n.0.iso. See, for example: https://openqa.fedoraproject.org/tests/524144#step/_do_install_and_reboot/39

Comment 14 browseria 2020-02-20 22:47:20 UTC
See also: bug 1804953

Comment 15 Vendula Poncova 2020-02-21 10:34:21 UTC
From journalctl:

Feb 19 13:33:04 localhost-live audit[19971]: ANOM_ABEND auid=1000 uid=0 gid=0 ses=2 subj=unconfined_u:system_r:install_t:s0-s0:c0.c1023 pid=19971 comm="efibootmgr" exe="/usr/sbin/efibootmgr" sig=11 res=1
Feb 19 13:33:04 localhost-live kernel: efibootmgr[19971]: segfault at 55c2d987cd02 ip 00007f91232282f5 sp 00007ffd7a360fe8 error 4 in libc-2.31.so[7f91230eb000+150000]

Reassigning to efibootmgr.

Comment 16 browseria 2020-02-24 23:51:49 UTC
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1806233

Comment 17 Yu-Ann Chen 2020-03-18 23:46:53 UTC
This problem is still reproducible on F32 beta when installing on a Lenovo Ideapad S130.
The installation worked just fine on F31.

Comment 18 Hans de Goede 2020-04-22 17:25:16 UTC
(In reply to Yu-Ann Chen from comment #17)
> This problem is still reproducible on F32 beta when installing on a Lenovo
> Ideapad S130.
> The installation worked just fine on F31.

According to the Lenovo specs page for the S130 the S130 has a "64 GB eMMC" so you are very likely not hitting this bug (which is about a segfault in efibootmgr) but rather hitting bug 1826864, which is about a libefivar bug which causes efibootmgr to not work properly when used with an eMMC, but it does cleanly exit with an error, rather then crashing as it does in this bug.

Comment 19 Fedora Program Management 2021-04-29 16:52:29 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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.

Comment 20 Ben Cotton 2021-05-25 17:18:00 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.


Note You need to log in before you can comment on or make changes to this bug.