[Bug 1695666] Re: users shoot themselves in the foot by removing /boot/efi from /etc/fstab; u-r-u should warn and refuse to let them upgrade

Steve Langasek steve.langasek at canonical.com
Sat Jan 13 01:52:56 UTC 2018


For completeness we should also check that the filesystem mounted at
/boot/efi is of type vfat.

+                             _("The UEFI Boot partition of your system "
+                               "is not mounted on /boot/efi. "
+                               "Please ensure that it is properly configured "
+                               "and retry."))

Suggested wording:

Your EFI System Partition (ESP) is not mounted at /boot/efi.  Please
ensure that it is properly configured and try again.

+        else:
+            self._view.error(_("UEFI Boot partition not usable"),
+                             _("The UEFI Boot partition of your system "
+                               "(/boot/efi) is not writable. "
+                               "Please ensure that it is properly configured "
+                               "and retry."))

The EFI System Partition (ESP) mounted at /boot/efi is not writable.
Please mount this partition read-write and try again.

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

Title:
  users shoot themselves in the foot by removing /boot/efi from
  /etc/fstab; u-r-u should warn and refuse to let them upgrade

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader source package in Artful:
  Fix Committed

Bug description:
  We currently have 6 open bug reports at
  <https://bugs.launchpad.net/ubuntu/+source/shim-signed>, and several
  closed ones, from users who have by one means or another gotten
  /boot/efi unmounted on their systems and then tried to apply updates.

  On a UEFI system, /boot/efi must be a separate mount point (it's the
  EFI System Partition); and it must be mounted at the time of upgrading
  the shim-signed/grub-efi-amd64 packages, because it's meaningless to
  "upgrade" these packages without installing the new bootloader to the
  ESP - if you don't want to use the Ubuntu UEFI bootloader, uninstall
  the package.

  However, a surprising number of users (i.e., more than 0) are leaving
  /boot/efi unmounted on their systems, and as a result get upgrade
  failures.  This is a bad thing to have happen in the middle of a dist-
  upgrade between releases.

  I think u-r-u should detect the case where either of the shim-signed
  and grub-efi-amd64 packages are installed, and /boot/efi is not in a
  sane state (is mountpoint + is mounted rw), and refuse to let the user
  start the upgrade until this is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1695666/+subscriptions



More information about the foundations-bugs mailing list