[Bug 1918314] Re: Cannot boot from grub after upgrade

Paul Goins 1918314 at bugs.launchpad.net
Wed Mar 10 17:14:05 UTC 2021


Additionally, tried grub-install directly from within hirsute:

root at dell2018:~# grub-install
Installing for x86_64-efi platform.
Installation finished. No error reported.

When I reboot... same problem.  Had to again recover via the USB
installer.

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

Title:
  Cannot boot from grub after upgrade

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading from Focal, it seems that I'm hitting boot problems
  every time Grub is ugpraded.

  For context, I recently upgrade from Focal to Groovy, then on the same
  day, to Hirsute (prerelease).

  On the upgrade to Groovy, my system stopped booting to grub, and I
  needed to load a Groovy install USB and run "grub-install" to make my
  system bootable.  (More specifically: grub-install --uefi-secure-boot
  --boot-directory=<mounted /boot> --efi-directory=<mounted /boot>/efi)

  On the upgrade to Hirsute, the same thing occurred, and I had to
  repeat the same to be able to boot.

  And after package upgrades yesterday, when I powered on my machine
  today, the same thing occurred again, so I gathered some details this
  time around.

  The following grub packages changed during last night's upgrade:

  grub-pc-bin:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44)
  grub-efi-amd64-signed:amd64 (1.163+2.04-1ubuntu40 -> 1.166+2.04-1ubuntu44)
  grub-efi-amd64-bin:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44)
  grub-common:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44)
  grub-pc:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44)

  As context, my system uses EFI (secure boot on if I recall right), and
  my disk is partitioned as follows:

  Device         Start        End   Sectors   Size Type
  /dev/sda1       2048    1050623   1048576   512M EFI System             <- /boot/efi
  /dev/sda2    1050624    2549759   1499136   732M Linux filesystem       <- /boot
  /dev/sda3    2549760  500632903 498083144 237.5G Linux filesystem       <- / (encrypted LVM)
  /dev/sda4  500633600  500666367     32768    16M Microsoft reserved
  /dev/sda5  500666368  999149401 498483034 237.7G Microsoft basic data
  /dev/sda6  999149568 1000212479   1062912   519M Windows recovery environment

  Also, note that simply doing "sudo update-grub" does *not* trigger
  this problem.  It seems to be something which happens at upgrade time.

  Please let me know if there's any other info I can gather for this; I
  fully expect this problem to recur the next time grub gets upgraded as
  well.

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



More information about the foundations-bugs mailing list