Public bug reported:
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).
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765484
Title:
grub-install should handle /boot/efi on RAID1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1765484/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
