Talk:Efibootmgr
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (
~~~~), and indent successive comments with colons (:).
Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.openrc efivars
As per gentoo-dev mailing list,
The documentation should be updated to say that with OpenRC 0.28 that you'll have to remount efivars as RW before you can install the bootloader (e.g., grub-install)
The command I use locally to remount rw (since I have configured efivars to be mounted read-only in fstab) is
mount -o remount,rw /sys/firmware/efi/efivars
from mattst88@gentoo.org
--Rage (talk) 01:16, 13 July 2017 (UTC)
Motherboard Will Quietly Delete Malformed Entries on Reboot
I am told by someone who works at these low levels and whose opinion I highly regard that all UEFI systems will remove entries which it cannot resolve at boot time, and, presumably without any indication or notice the user. So a user may create an entry with efibootmgr, the efibootmgr will show it when the user confirms it in the same session that the entry was created, but when the system is rebooted, the motherboard's UEFI software will remove the entry if it cannot be resolved or is invalid, e.g. bad path. So the disappearance of an entry is an indication something in it was malformed or the disk/partition referenced cannot be found.
Since there is nothing to alert the user of the deletion, this page should have something to educate those learning about UEFI entries that deletions can occur without notice.
- If course, I passed the question by Google Bard ("Do all UEFI implementations remove entries that are invalid?") and its response was "No, not all UEFI implementations automatically remove invalid boot entries. The behavior regarding invalid entries varies among different UEFI vendors and firmware versions." So perhaps the more conservative approach on this documentation would be to say a UEFI system may delete invalid entries, so if what you just created, or had registered in the motherboard's UEFI inventory, disappears, then that is an indication the entry was auto-deleted.