[Bug 1765484] Re: grub-install should handle /boot/efi on RAID1
Osmin Alexei Lazo Santos
1765484 at bugs.launchpad.net
Thu Sep 3 02:59:45 UTC 2020
*** This bug is a duplicate of bug 1466150 ***
https://bugs.launchpad.net/bugs/1466150
Adding --no-nvram to grub-install
grub-install --efi-directory=$mntpoint --target=x86_64-efi --no-nvram
fixes this, the --no-nvram bypasses updating efi vars with efibootmgr
but this entries don't need to be modified after install and on every
grub pkg update.
Modifying this line in /usr/lib/grub/grub-multi-install will allow the
grub pkg update to complete succesfully...
The error seems to be caused by the efibootmgr command using mduuid of
raid.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1765484
Title:
grub-install should handle /boot/efi on RAID1
Status in grub-installer package in Ubuntu:
Confirmed
Bug description:
I am using grub-efi. I have /boot/efi as a RAID1 with metadata=1.0 at
the _end_ of the partition so it can still be seen by UEFI boot
firmware as a FAT32 filesystem. grub-install calls efibootmgr with and
empty -d argument:
efibootmgr -c -d "" ...
since it can't figure out what drive /boot/efi is on. With grub-pc,
when /boot was on a RAID1, grub-install would get run via the grub-pc
postinst for each component of the raid (and/or as a list presented to
the user via debconf).
For example, with this:
# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda1[2] sdb1[0]
524224 blocks super 1.0 [2/2] [UU]
if /dev/md0 was mounted on /boot, grub-pc's postinst would run grub-
install on /dev/sda and /dev/sdb.
In the UEFI case, if /dev/md0 is mounted on /boot/efi, I would expect
efibootmgr to be run multiple times for each component:
efibootmgr -c -d /dev/sda1 -L ubuntu-sda1 ...
efibootmgr -c -d /dev/sdb1 -L ubuntu-sdb1 ...
Dunno about boot ordering, etc. I'm not actually using efibootmgr
currently. As a work-around, I ran "dpkg-reconfigure -p low grub-efi"
and disabled the NVRAM setting in debconf (to avoid efibootmgr failing
grub-install and causing package installs/upgrades to fail).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1765484/+subscriptions
More information about the foundations-bugs
mailing list