[Bug 913336] Re: grub-common recreates /etc/grub/grubenv

[Richard Laager]

Jordan_U in #grub suggested that GRUB should just not fail on boot when
grubenv is read-only. That would sidestep the need for these changes.
I'll pursue that option a bit. Ignore the patches for now.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/913336

Title:
  grub-common recreates /etc/grub/grubenv

Status in “grub2” package in Ubuntu:
  Confirmed

Bug description:
  /etc/init.d/grub-common and /etc/pm/sleep.d/10_grub-common call grub-
  editenv to clear the recordfail setting to indicate that the system
  booted or awoke successfully. They call grub-editenv, which creates
  the grubenv file if it doesn't exist.

  If the admin has deleted the grubenv file intentionally because they
  don't want grub writing to the filesystem, this behavior is annoying.
  If the admin has deleted the file because grub does not have write
  support for the root filesystem, then this behavior breaks booting;
  someone has to hit a key on the console for the machine to boot.

  The attached patch fixes this. However, I'm not sure what is supposed
  to create /boot/grub/grubenv originally. If it's the init script, then
  some further changes will be required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/913336/+subscriptions