Correct me if I'm wrong, according to [this
documentation](https://www.gnu.org/software/grub/manual/grub/html_node/Environment-
block.html), on LVM or RAID disk the `/boot/grub/grubenv` file cannot be
modified by GRUB, in that case, by the `save_env` routine. Only the OS
via `grub-reboot`, `grub-ed
This bug was fixed in the package grub2 - 2.02-2ubuntu8.6
---
grub2 (2.02-2ubuntu8.6) bionic; urgency=medium
* debian/patches/linuxefi_fix_relocate_coff.patch: fix typo in
relocate_coff() causing issues with relocation of code in chainload.
(LP: #1792575)
* debian/patches/
This bug was fixed in the package grub2-signed - 1.93.7
---
grub2-signed (1.93.7) bionic; urgency=medium
* Rebuild against grub2 2.02-2ubuntu8.6 (LP: #1792575)
grub2-signed (1.93.6) bionic; urgency=medium
* Rebuild against grub2 2.02-2ubuntu8.5 (LP: #788298)
-- Mathieu Trudel-
Retested with 2.02-2ubuntu8.6:
dannf@mdraid:~$ sudo grub-reboot 0
WARNING: Detected GRUB environment block on diskfilter device
0 will remain the default boot entry until manually cleared with:
grub-editenv /boot/grub/grubenv unset next_entry
--
You received this bug notification because yo
@dannf, can you please confirm which version of grub you were using for
the tests?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788298
Title:
grub-reboot changes boot default permanently on Lucid L
Verification was done earlier by dannf; this is the same SRU with more
patches included for a different issue.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Hello Mike, or anyone else affected,
Accepted grub2 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.6
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
Verification:
On a system w/ /boot on an md device:
dannf@mdraid:~$ sudo grub-reboot 0
[sudo] password for dannf:
WARNING: Detected GRUB environment block on diskfilter device
0 will remain the default boot entry until manually cleared with:
grub-editenv /boot/grub/grubenv unset next_entry
Hello Mike, or anyone else affected,
Accepted grub2 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.5
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
** Changed in: grub2 (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
This bug was fixed in the package grub2 - 2.02+dfsg1-5ubuntu4
---
grub2 (2.02+dfsg1-5ubuntu4) cosmic; urgency=medium
* debian/patches/linuxefi_fix_relocate_coff.patch: fix typo in
relocate_coff() causing issues with relocation of code in chainload.
(LP: #1792575)
-- Mathie
** Description changed:
- Binary package hint: grub-pc
+ [Impact]
+ The grub-reboot manpage says it will "Set the default boot menu entry for
GRUB, for the next boot only." But, that's a promise it cannot keep when GRUB
cannot write to the environment block, such as when it is stored on Linux
s
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: grub2 (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubunt
It still occurs in Raring with no RAID, just a SSD and a HDD.
** Tags added: raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788298
Title:
grub-reboot changes boot default permanently on Lucid
The bug is actual still for 12.04 LTS on mirror RAID devices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788298
Title:
grub-reboot changes boot default permanently on Lucid LTS
To manage notifica
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788298
Title:
grub-
Regarding the problem of grub-reboot not working with /boot on a RAID array
(and in my case not being able to boot back into Ubuntu), I would be happy with
a timed default. It wouldn't require GRUB_DEFAULT=saved or grubenv. As I
imagine it, a user who normally uses e.g. GRUB_DEFAULT=0 would edit
Jordan Uggla points out that his fourth patch in
http://lists.gnu.org/archive/html/grub-devel/2009-12/msg00276.html
addresses part of this, by at least making grub-reboot not do anything
rather than acting like grub-set-default; I'll think about that patch
some more but it seems reasonable. Making
It appears that this bug may not actually be related to bug #497326 as
per the recent update in that thread. Perhaps this has more to do with
the disk configuration that's being used?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Attachment added: "/etc/default/grub"
https://bugs.launchpad.net/bugs/788298/+attachment/2142670/+files/grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788298
Title:
grub-reboot changes boo
20 matches
Mail list logo
