As mentioned before, support for multiple ESPs has been introduced to
deal with raid devices, installing directly to an ESP inside a raid is
not supported.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of
Here's a Debian bug report from 2019 for the same issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925591
** Bug watch added: Debian Bug tracker #925591
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925591
--
You received this bug notification because you are a member of Ubuntu
FWIW, my prior comment was confusing. GRUB handles both
efibootmgr entries correctly on its own with this new
functionality.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868553
Title:
libefi*
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868553
Title:
libefi* integration breaks grub-install on MD devices
To manage
Paride,
It was a limited-duration copy of the original text pasted into my previous
ticket comment, so it contained unblemished formatting but was otherwise
identical content.
As an addendum, I tested 20.04 with a two-ESP system and I was able to
specify both ESPs when I ran:
@TJ: could you please share how your efi partition is mounted? For
example by pasting the output of:
grep efi /proc/self/mounts
Also: what happens if you run grub-install without parameters? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Mason: that pastebin doesn't work: 404 That page does not exist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868553
Title:
libefi* integration breaks grub-install on MD devices
To manage
So, "dpkg-reconfigure grub-efi-amd64" now has a screen that matches what
we'd get reconfiguring the old grub-pc:
┌──┤ Configuring grub-efi-amd64 ├───┐
│ The grub-efi package is being upgraded.
https://bpa.st/FQOQ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868553
Title:
libefi* integration breaks grub-install on MD devices
To manage notifications about this bug go to:
Hmm, I guess I'm not understanding. My only system with md root has:
/dev/md126p1 on /boot/efi type vfat
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors
=remount-ro)
I'm hoping that if either drive dies, this system can still boot. (But
I've not been
"for each device in the array"
You cannot put EFI system partitions in a Linux software raid device.
This is unsupported. You will get corruption the first time your EFI
writes data to one of the VFAT filesystems (which EFI is allowed to do).
As of Ubuntu 20.04, the grub package has support for
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868553
Title:
13 matches
Mail list logo
