This bug was fixed in the package grub2 - 2.02-2ubuntu8.21
---
grub2 (2.02-2ubuntu8.21) bionic; urgency=medium
* d/build-efi-images:
- Add xfs module to signed UEFI images
(Closes: #911147) (LP: #1652822)
-- Eric Desrochers Thu, 07 Jan 2021
08:45:31 -0500
** Changed
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to access root
To manage notifications about this bug go
[PART 2]
Here some output to confirm my above statement:
* release:
$ lsb_release -cs
bionic
* df:
/dev/sda224G 8.0G 17G 34% /
/dev/sda1 511M 6.1M 505M 2% /boot/efi
* /etc/fstab:
# / was on /dev/sda2 during curtin installation
[VERIFICATION BIONIC]
I have reproduced the problem with grub2 (2.02-2ubuntu8.20) w/ this
layout:
/boot/efi
/ xfs
I then boot with a live cd, mount the partitions, mount --bind {dev, proc, run,
sys} and chroot to enable proposed and update grub to version 2.02-2ubuntu8.21
and grub2-signed
I don't fix grub2 often ... And I missed/forgot changing the build-
depends version instruction in grub2-signed to no longer point to 8.20
but 8.21.
I just did the modification, re-uploaded, and let sil2100 knows about my
oversight
-Build-Depends: debhelper (>= 9), lsb-release, python3,
Hello Jeremiah, or anyone else affected,
Accepted grub2 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.21
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
One can't deploy using root XFS partition using 18.04 on UEFI platform.
[Test case]
* Deploy a Bionic machine with a storage layout as follows:
vda-part1 536.9 MB fat32 /boot/efi
vgroot-lvroot 31.7 GB xfs / ## Only xfs is important here.
** Description changed:
- ### SRU TMPL DRAFT ###
-
[Impact]
One can't deploy using root XFS partition using 18.04 on UEFI platform.
[Test case]
* Deploy a Bionic machine with a storage layout as follows:
vda-part1 536.9 MB fat32 /boot/efi
vgroot-lvroot 31.7 GB xfs / ##
** Description changed:
### SRU TMPL DRAFT ###
[Impact]
One can't deploy using root XFS partition using 18.04 on UEFI platform.
[Test case]
* Deploy a Bionic machine with a storage layout as follows:
vda-part1 536.9 MB fat32 /boot/efi
vgroot-lvroot 31.7 GB xfs / ##
** Description changed:
### SRU TMPL DRAFT ###
[Impact]
One can't deploy using root XFS partition using 18.04 on UEFI platform.
[Test case]
* Deploy a Bionic machine with a storage layout as follows:
vda-part1 536.9 MB fat32 /boot/efi
vgroot-lvroot 31.7 GB xfs / ##
** Description changed:
+ ### SRU TMPL DRAFT ###
+
+ [Impact]
+
+ One can't deploy using root XFS partition using 18.04 on UEFI platform.
+
+ [Test case]
+
+ * Deploy a Bionic machine with a storage layout as follows:
+
+ vda-part1 536.9 MB fat32 /boot/efi
+ vgroot-lvroot 31.7 GB xfs / ##
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: grub2 (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: grub2 (Ubuntu Bionic)
At least for Xenial, this still fails, the xfs module either not build-
in, or not copied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to
This bug was fixed in the package grub2 - 2.02+dfsg1-12ubuntu1
---
grub2 (2.02+dfsg1-12ubuntu1) disco; urgency=medium
* Merge against Debian unstable; remaining changes (LP: #564853):
- debian/control: Update Vcs fields for code location on Ubuntu.
- debian/control: Breaks
Correction to that date I write above: 2019 02 06 not 2019 02 26 blargh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to access root
To
... Ah I see, it does look like possibly the debian upstream might have
fixed it, and merely the ubuntu package has not yet got it. Which is
what this bug declares at the top, so no discrepency there after all.
They mention signed images, where in my own case I have uefi boot
security disabled
On 19.04 I still get my grub.cfg broken by normal updates. Not by kernel
updates, and not by running update-grub. But there is some package that
whenever that package is updated, part of the update process generates a
new grub.cfg, and it's a broken one because it makes a bad assumption
somewhere.
This definitively affects 18.04 as well. The main culprit is that the
/boot/efi/EFI/ubuntu/grubx64.efi binary in 18.04 lacks XFS support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
** Changed in: grub2 (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to access root
To manage
** Bug watch added: Debian Bug tracker #908232
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908232
** Also affects: grub2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908232
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Same here. I had to write myself a google drive doc that I could consult
every time a the grub-efi package was updated and broke my boot again.
In addition to the steps explained previously, I also copy my working
manually edited grub.cfg to emergency.cfg, so that every time I get a
failed boot
** Tags added: id-5a8df3b7e96d9c9d3ffc8f7b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to access root
To manage notifications about this
It's not that simple. The module should have been copied if xfs was
detected as the filesystem for /boot... But there's more to it than
that. In UEFI, you also need a signed grub binary that already includes
the module, otherwise Secure Boot might prohibit you loading it from
disk.
This is
In analyzing this over in Bug 1731490; grub-install does not check the
filesystem of /boot; even if it did, it still needs to do the follwing:
1) copying the proper modules into /boot/efi/EFI/ubuntu/x86_64-efi/
2) updating /boot/efi/EFI/ubuntu/grub.cfg to insmod the required modules for
the the
** Branch linked: lp:~raharper/curtin/trunk.lvmroot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to access root
To manage notifications
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to access root
To manage
** Summary changed:
- grub efi xfs unsupported filesystem
+ grub efi doesn't install fs module needed to access root
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't
27 matches
Mail list logo
