[Bug 1594903] [NEW] Ubuntu does not reset grubenv's recordfail

Arbiel Perlacremaz arbiel.perlacremaz at gmx.fr
Tue Jun 21 17:04:28 UTC 2016


Public bug reported:

This is a conceptual bug in the way it aims at the interface between grub2 and ubuntu.
This situation arises when Ubuntu's /boot/grub/grubenv does not point to the same grubenv file as the one that is used by grub at booting time.
To say it another way, let's suppose grub has been installed on a removable device with --boot-directory referring to a directory on the same removable device. As the contents of the /boot directory have no reason to remain in the file tree on a running system, the user is well entitled to include a line in /etc/fstab to mount any other partition on /boot, so as to free the port on which the booting device is connected. In which case, the system reset recordfail in an environment which is not the right one.
At booting time, recordfail is then always true.

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1594903

Title:
  Ubuntu does not reset grubenv's recordfail

Status in grub2 package in Ubuntu:
  New

Bug description:
  This is a conceptual bug in the way it aims at the interface between grub2 and ubuntu.
  This situation arises when Ubuntu's /boot/grub/grubenv does not point to the same grubenv file as the one that is used by grub at booting time.
  To say it another way, let's suppose grub has been installed on a removable device with --boot-directory referring to a directory on the same removable device. As the contents of the /boot directory have no reason to remain in the file tree on a running system, the user is well entitled to include a line in /etc/fstab to mount any other partition on /boot, so as to free the port on which the booting device is connected. In which case, the system reset recordfail in an environment which is not the right one.
  At booting time, recordfail is then always true.

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



More information about the foundations-bugs mailing list