On Thu, Jul 15, 2021 at 12:01 PM Patrick Dupre <pdupre@xxxxxxx> wrote: > > Hello, > > On a dual boot machine (one fc32, and one fc34). > after I upgraded the fc32 to fc34, I cannot boot on the new fc34. What does happen? I'm not sure what "cannot boot" means because it doesn't tell me how it's failing. > I get > failed to mount /boot/efi > /boot/efi is shared by both machines > > Here is the fstab of the fc34 machine > > # > UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4 defaults 1 1 > UUID=B2EF-0CE4 /boot/efi vfat umask=0077,shortname=winnt 0 2 > > > The /boot/efi seem correct (it is currently mounted by the fc32). > > blkid |grep B2EF > /dev/sdb1: UUID="B2EF-0CE4" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="0fe1d405-6683-456c-a306-140e882e322c" > blkid |grep 9faad39 > /dev/sda6: LABEL="fedora_rescue" UUID="a5b809ae-61c2-4d67-b0f3-109e99faad39" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="OS" PARTUUID="41b9d134-b477-4ef5-8602-15fdc482a51e" > > What should I do ? > It seems that the installer create /boot/efi/EFI/fedora/grub.cfg I'm not really certain the best way to share a single /boot/efi/EFI/fedora between two Fedoras. My idea would be for Fedora 34 to be primary, and exclude shim and all of grub2 from being updated on Fedora 32. Well, ha, as I think about it, that doesn't matter anymore because there are no more updates, it's EOL. What you really want to do though is share a single /boot because the single bootloader needs to see a single set of configuration files found in /boot/loader/entries. And the f32 snippets will point to the f32 kernels and f32 system root. And the f34 snippets will point to the f34 kernels and system root. It definitely works, except for one problem: https://bugzilla.redhat.com/show_bug.cgi?id=1874724 > with > search --no-floppy --fs-uuid --set=dev a5b809ae-61c2-4d67-b0f3-109e99faad39 > set prefix=($dev)/boot/grub2 > export $prefix > configfile $prefix/grub.cfg > > (I could not boot either) > Then I run (from the fc32) > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg.new > > and used this file to boot (by renamed). OK I can't tell where the f32 /boot is, but you need all the snippets in one /boot/loader/entries that both f32 and f34 share. I'm not sure why /boot/efi is failing to mount need to see logs for that, but you can also add nofail to the fstab for it so at least boot won't hang. The gist of what you need is one f34 bootloader in /boot/efi/EFI/fedora/ and its grub.cfg points to the real grub.cfg at /boot/grub2 which in turn loads blscfg.mod which finds and reads /boot/loader/entries and then creates a GRUB menu from all the snippets found there. -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
