Summary: | sys-boot/grub - grub2-reboot sets next_entry but reboot does not clear it | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Romain Riviere <gentoo> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ahferroin7, floppym, joe |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Romain Riviere
2014-12-22 08:04:35 UTC
This is actually intended behavior in GRUB. You're supposed to set up your grub.cfg to clear the variable. Try adding something like this to each of the menu entries in your grub.cfg: if [ "${next_entry}" ] ; then set next_entry= save_env next_entry fi (In reply to Austin S. Hemmelgarn from comment #1) > This is actually intended behavior in GRUB. You're supposed to set up your > grub.cfg to clear the variable. > > Try adding something like this to each of the menu entries in your grub.cfg: > > if [ "${next_entry}" ] ; then > set next_entry= > save_env next_entry > fi The whole point of the command is to do it once (as interpreted from the man page) and not to make it a permanent setting (grub2-set-default is for that). So I believe this bug report is valid. Your statement that this code needs to be added is also correct and we should likely have that in our default output of grub2-mkconfig. Send a patch upstream please. It appears if grub2 has an issue with writing on boot partitions that are on raid/lvm Source: https://bugzilla.suse.com/show_bug.cgi?id=865227#c3 Potentially related bug report: https://savannah.gnu.org/bugs/index.php?44167 00_header in grub-2.06 has this: if cmostest $GRUB_BUTTON_CMOS_ADDRESS ; then set default="${GRUB_DEFAULT_BUTTON}" elif [ "\${next_entry}" ] ; then set default="\${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="${GRUB_DEFAULT}" fi |