The command: lsblk -f
will reveal the UUID of the respective partitions. This is normally used in your fstab, unless you created this manually, in which case you can use logical names or filesystem labels. The efibootmgr will display the partition UUID where the .efi executable resides. You can check which block device has the same partition UUID with: lsblk -o NAME,SIZE,PARTTYPENAME,PARTUUID Note: the partition UUID is different to the partition type UUID. You probably need to be explicit where the ESP mountpoint is, when you install grub; e.g.: grub-install --efi-directory=/efi /dev/sda You may in addition need to specify where the '--boot-directory' is. Best you check this page to compare against the contents of your /efi and /boot, in case you missed any steps: https://wiki.gentoo.org/wiki/GRUB#UEFI_with_GPT On Monday, 27 May 2024 14:05:49 BST Jude DaShiell wrote: > grub-update found boot partition in /dev/sda3. The problem I now have is > I cannot boot into gentoo. > The efibootmgr program on original system shows no available gentoo boot > drive and has lots of hex output so I can't locate /dev/sda3 in efibootmgr > and all gentoo partitions I created have been changed to conform to the > discoverable standard mentioned in the handbook. > > > -- > Jude <jdashiel at panix dot com> > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. > Please use in that order." > Ed Howdershelt 1940. > > On Mon, 27 May 2024, Jude DaShiell wrote: > > I think I fixed the problem by putting all of the boot stuff into the > > /mnt/gentoo/efi directory which has /dev/sda1 mounted to it. Reason I > > think that problem got fixed was I repeated the steps and iucode steps > > from emerge linux-firmware all the way down to emerge gentoo-kernel-bin > > and emerge didn't once mention it assumes I have no separate boot > > partition. So I expect to be testing the system a little later today > > after running update-grub on the existing system which has osprober > > enabled. If boot partition is found on sda1 I will have succeeded.
signature.asc
Description: This is a digitally signed message part.
