[Bug 1891718] Re: [Regression] breaks GRUB install on an nvme device
Bug Watch Updater
1891718 at bugs.launchpad.net
Wed Oct 25 17:01:54 UTC 2023
** Changed in: efivar
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to efivar in Ubuntu.
https://bugs.launchpad.net/bugs/1891718
Title:
[Regression] breaks GRUB install on an nvme device
Status in Efivar:
Fix Released
Status in efivar package in Ubuntu:
Fix Released
Status in efivar source package in Focal:
Fix Released
Status in efivar source package in Groovy:
Fix Released
Bug description:
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
I've hit this on 2 systems so far - a high-end Nvidia server and an
older ARM Server.
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most at risk are systems with NVMe block devices. Supposedly nvme-fabrics systems were not previously supported and, as a side-effect of this backport, will now be. However, it's possible - like was the case with bionic/nvme-subsys - that nvme-fabrics *used* to happen to work, and now will work differently or even break. Ideally we'd be able to test on such a system, but I don't know where to find that hardware.
This fix has been in groovy since just after beta (minus an innocuous
debug statement that upstream requested during review), and the same
patches apply cleanly to focal, which should help mitigate the risk by
way of some real world exposure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/efivar/+bug/1891718/+subscriptions
More information about the foundations-bugs
mailing list