Gentoo won't boot after successful GRUB install

[pietinger]

I do not want to confuse greek here, but my idea was to copy grub EFI executable into EFI spec location and rename it bootx64.efi. In this case UEFI firmware should boot it even when variable is not set with efibootmgr, one thing less that can go wrong. If there still is no boot then it is quite clear something is wrong with that motherboard firmware setup.

Yes this is one good possibility. I would suggest to do it even simpler with installing the correct entry again manually with:

Code: Select all

efibootmgr -c -d /dev/sda -p 2 -L "Grub2" -l '\Efi\gentoo\grubx64.efi'

... IF ... this is the correct path to his installation. I suppose he did some copying instead a complete new begin of the installation and the UEFI entry is pointing still to his old 2. partition.

[greek]

Boot with your install-CD again and mount all partitions you need (described in the first steps of th AMD64 installation handbook). Then give us the output of (its not the number "one" - it is the letter "L" in small):
ls -Rl /boot/Efi/
and
"lsblk" and "blkid"

I've done that. I'm now in chroot with all mounted.
Here's the output of ls -Rl /boot/Efi:

Code: Select all

(chroot) ls -Rl /boot/Efi
/boot/Efi:
total 1
drwxr-xr-x 2 root root 512 Jan  4 19:54 gentoo

/boot/Efi/gentoo:
total 124
-rwxr-xr-x 1 root root 126976 Jan  4 19:54 grubx64.efi

Here's the output of lsblk:

Code: Select all

 lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0 378.1M  1 loop
sda      8:0    0 111.8G  0 disk
├─sda1   8:1    0     2M  0 part
├─sda2   8:2    0   128M  0 part /boot
├─sda3   8:3    0   2.4G  0 part [SWAP]
└─sda4   8:4    0 109.3G  0 part /
sdb      8:16   1   7.2G  0 disk
├─sdb1   8:17   1   415M  0 part
└─sdb2   8:18   1   6.4M  0 part

Here's the output of blkid

Code: Select all

blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: SEC_TYPE="msdos" UUID="7748-322D" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="grub" PARTUUID="032492a0-addd-4022-b11e-9d9cf486766b"
/dev/sda2: UUID="AB7A-2478" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="boot" PARTUUID="6a77ae3b-1a26-408e-a789-bad5c42b777b"
/dev/sda3: UUID="83105fc6-1388-45d5-9405-72daf17810bc" TYPE="swap" PARTLABEL="swap" PARTUUID="a12da7c5-6b89-44ec-a63d-a1f9f6778ee2"
/dev/sda4: UUID="bc8ca50c-40ba-452f-beaf-99bf6089306b" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="510c4211-0e88-47ea-a3dd-d651609483bf"
/dev/sdb1: BLOCK_SIZE="2048" UUID="2021-01-03-23-32-51-81" LABEL="Gentoo amd64 20210103T214503Z" TYPE="iso9660" PTUUID="366e7cdd" PTTYPE="dos" PARTUUID="366e7cdd-01"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="GENTOOLIVE" LABEL="GENTOOLIVE" UUID="423A-6C6A" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="366e7cdd-02"

P.D. I have sucessfully installed archlinux earlier on this exact machine, but couldn't get voidlinux to boot as well (same issue!). Don't know if that's useful, but there it goes..

[Buffoon]

greek,

why don't you try what I suggested. Some manufacturers have real sloppy firmware, but it has to boot from standard location.

[greek]

Hi, Buffoon.

Sorry, I did not see your response! How would I move the grub file to whatever location it'll work?

[pietinger]

I've done that. I'm now in chroot with all mounted.

Perfect. I was right: Your UEFI-entry points to a non-existent partition. Do the command I described above and then do an "efibootmgr -v" again. You should see now a new UEFI-entry with the SAME PARTUUID as you see with "blkid" for your 2. partition (=your ESP). If this is true then reboot ... and you should see at minimum "grub2"

[nick_gentoo]

Code: Select all

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* gentoo HD(2,GPT,b055a88d-2bc3-4b72-8728-72c54e5e4e09,0x1800,0x40000)/File(\Efi\gentoo\grubx64.efi)
Boot0001* UEFI: TOSHIBA TransMemory 1.00 PciRoot(0x0)/Pci(ox14,0x0)/USB(6,0)/CDROM(1,0xc0,0xcc30). . BO

Also, one more idea: greek, what options do you see in that BIOS menu?
I think the efibootmgr output shows that the default boot option is from an USB drive (BootCurrent: 0001). Can you select another option within the BIOS menu?

Nick, this is normal when booting from a CD. If he pulls out the CD and do a reboot, the UEFI (=BIOS) checks there is no CD adn change automatically to "Boot0000".

Ok, thank you! It pretty clear actually (now), as the efibootmgr man page explains very well what everything in the listing means.

[Buffoon]

BootCurrent and BootOrder are two different things.

Code: Select all

BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0000
Boot0000* Gentoo Backup
Boot0001* Gentoo

See? BootOrder is set 0001 first, this will be booted if present. If I hit F11 to bring up menu at boot and boot backup kernel then it will change to:

Code: Select all

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0001,0000
Boot0000* Gentoo Backup
Boot0001* Gentoo

[pietinger]

BootCurrent and BootOrder are two different things.

Yes.

If I hit F11 at boot and boot backup kernel then it will change to [...]

In every UEFI you have the possibility to change the order permanent (in the BIOS-settings) or temporary (with my gigabyte-mainboard with F12). I have two kernels and sometime I must boot the other one. I do this with F12. When I want to boot "back" to my normal kernel I just do a reboot without going into BIOS again.

With "efibootmgr" you can also change the boot order permanent ... but not all mainboards accepts this change and you have to do it in the settings.

[greek]

Perfect. I was right: Your UEFI-entry points to a non-existent partition. Do the command I described above and then do an "efibootmgr -v" again. You should see now a new UEFI-entry with the SAME PARTUUID as you see with "blkid" for your 2. partition (=your ESP). If this is true then reboot ... and you should see at minimum "grub2"

Peter, are you saying that I should do that "efibootmgr -c -v grub..."(don't remember the full command) when i have my partitions mounted? Or I should do a normal installation and then when it comes to GRUB2 install i should do that command?

[pietinger]

Peter, are you saying that I should do that "efibootmgr -c -v grub..."(don't remember the full command) when i have my partitions mounted? Or I should do a normal installation and then when it comes to GRUB2 install i should do that command?

It doesnt matter if your boot partition is mounted or not. The command you have to type in:

Code: Select all

efibootmgr -c -d /dev/sda -p 2 -L "Grub2" -l '\Efi\gentoo\grubx64.efi'

talks only with your UEFI (using the efivarfs file-system; therfore this is the only prerequisite you need; you can check with "mount" and "ls /sys/firmware/efi" must exist).(I dont know, if efibootmgr is on the installation-CD. If not you must mount and chroot into your gentoo.) Dont do another new installation right now.

Then check with "efibootmgr -v" and "blkid" what I have said.

(type in above command very carefully and exact with all inverted comma and BACKslash)


P.S.: the part '-L "Grub2"' is just a name, you will see later in your BIOS settings. You can choose what you want, but please NOT "gentoo" again, because you already have one entry with this name. If you want you can name it '-L "MYLINUX" and so on ...

[greek]

Thanks for the support, Peter. I'll get back to you when I finish the install!

[pietinger]

Thanks for the support, Peter. I'll get back to you when I finish the install!

Wait. Do you do another new installation ? If yes, dont forget: the installing-routine for grub2 usually does the same I tried to do with you manually and there is usually no need for doing it by yourself. Just check with "efibootmgr -v" before and after installing grub2. You now know what you must check ? (same PARTUUID from ESP with UEFI-entry).

Good luck,
Peter

P.S.: I dont know how intelligent the installation-routine for grub2 is. Maybe it is necessary to delete the old UEFI-entry in your BIOS before, because it can be that if there is an existant "gentoo"-entry it will not be updated ... but you will see it with "efibootmgr -v" (in this case we can do my plan again).

[Buffoon]

One question is unanswered still, why did it go wrong in the first place? When grub install is executed properly from chroot it should get it right ... right? Maverick as I am I do everything manually, therefore if something goes wrong then it is my fault. Who's fault it is if grub-install screws up?

[pietinger]

One question is unanswered still, why did it go wrong in the first place? When grub install is executed properly from chroot it should get it right ... right? Maverick as I am I do everything manually, therefore if something goes wrong then it is my fault. Who's fault it is if grub-install screws up?

I BELIEVE (= dont know) with the first installation grub2 did all right; the only reason for not booting correct was the missing ESP-flag for his boot partition (forgot to do a "set 2 boot on" in parted). Then he tried to do another installation with new partitioning the sda; this leads to a new PARTUUID; but he didnt a complete new installation, only copying grub-files back from somewhere.

[DespLock]

Hi,
i think you might have missread the handbook.

/dev/sda1 BIOS boot partition
/dev/sda2 Boot partition
/dev/sda3 Swap partition
/dev/sda4 Root partition

[...]

Using UEFI with MBR partition layout is discouraged. If an UEFI capable system is used, please use GPT layout.

You made /dev/sda2 ESP,boot, so there is no need for your first partition (dev/sda1).

As a first advice:
Usually UEFI has support for a boot menu (press F12, ESC or similar). Try to open it and see if there are any entries.

And there is imho no need for a reinstall on grub issues.

On your live-cd try:

1) chroot (handbook)
2) edit /etc/default/grub:

Code: Select all

GRUB_DISTRIBUTOR="your_new_special_name_for_this_install"

2) mount /boot
3) grub-install --target=x86_64-efi --efi-directory=/boot
4) grub-mkconfig -o /boot/grub/grub.cfg
5) Reboot and open the UEFI boot menu.

If it fails, i would recommend
(0) chroot (handbook)
1) copy all your files on /boot (without subdirectories, esp don't copy EFI folder) to another drive/partition (/root/boot or usb stick).
2) umount /boot
3) mkfs.vfat -F32 /dev/sda2
(optional: edit /etc/fstab if you used UUID instead of /dev/sda2 for "/boot")
4) mount /boot
5) copy your files back to /boot
6) grub-install --target=x86_64-efi --efi-directory=/boot
7) grub-mkconfig -o /boot/grub/grub.cfg
8) Reboot and open the UEFI boot menu.

That's usually all to do about grub.

P. S. optional:
Since you don't need partion /dev/sda1 for your setup, you could merge it with gparted or similar.
(optional: use gparted to merge partiton sda1 + sda2). In this case all steps above needs to be modified to use the correct partition (fdisk -l /dev/sda)

[pietinger]

Hi,
i think you might have missread the handbook.
[...]
You made /dev/sda2 ESP,boot, so there is no need for your first partition (dev/sda1)

Yes, we all know that this first partition is not needed with UEFI. The handbook tries to describe both methods (UEFI and MBR) and not to confuse people, like you do now.

greek will manage it surely with the information he got and (because he is a nice guy) he will report us the next time. Be patient and wait for this.

[greek]

Hello! I am here again.

Same problem. Flashed me away into my BIOS... Starting to think I'm booting in CSM mode or something like that. Did everything you guys said.
Not going to risk it and start a new installation. Once more, I ask for your help! I don't know what's happening.

[pietinger]

Hello! I am here again.

Same problem. Flashed me away into my BIOS... Starting to think I'm booting in CSM mode or something like that. Did everything you guys said.
Not going to risk it and start a new installation. Once more, I ask for your help! I don't know what's happening.

Cant believe. What is the output from "efibootmgr -v" and "blkid" NOW ?

[Buffoon]

Reinstall never helps with Gentoo, [well, almost never]. I believe all information you (or anybody else) ever need is scattered all over this thread, just sit down and put it all nicely together.

[sluggeek]

Hi,

I am not a pro but when I try to install gentoo the first time I had the same issu : grub was installed successfully but I can't boot.

I read a lot, and found a solution : you need a free space before the first partition of your disk. A least 2 or 3 MB. Don't format it, just let it free.
I see in your post u let a free space of 1049kb, I think it is too small.

If you want a "speed install", skip the emerge -avuDN @world command. You can run it after the first reboot.

I hope it helps,

Sorry for my terrible english,

See You

[pietinger]

I see in your post u let a free space of 1049kb, I think it is too small.

One MB should be more than enough if you boot a gpt-disk with UEFI (and it should be enough for a MBR-boot also, even if some space is lost for a part of grub). I never reached the limit, even with very many partitions. See also: https://en.wikipedia.org/wiki/GUID_Partition_Table

One KB could be not enough ... and if you did the wrong configuration in parted: "unit KIb" instead of "unit MIB" ... then you will run into problems ... if you start the beginning of your first partition with 1 !

P.S.: If it would be a problem you wouldnt find it in the official AMD64-Installation-Guide ... written by profis ...

[Tony0945]

1 Mib is plenty

Code: Select all

isk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: CT500MX500SSD1  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3EE9432E-169D-4EC5-A9EC-7F932FBDCD61

Device      Start       End   Sectors   Size Type
/dev/sda1    2048    206847    204800   100M EFI System
/dev/sda2  206848 976773134 976566287 465.7G Linux filesystem

Notice that you don't need a /seperate boot either unless grub2 needs it. Don't use grub. Grub has outlived it's usefullness. Use either refind or stub kernel.
Grub was designed for MBR then extended. New system, use new tools.

https://www.linux-magazine.com/Online/F ... ot-Process

[sluggeek]

Thanks Pietinger and Tony

To find the solution of my problem, I install Manjaro and I do the same partitions as Manjaro do (2Mo free before the first partition). I just change that and gentoo boot ...

But, on the installations I fail, I dont remember the space I leave free before the first partition. Maybe it was less than 1049kb.

As you said "AMD64-Installation-Guide [is] written by profis" but in english ... There is no translation in french https://wiki.gentoo.org/wiki/Handbook:A ... n/Disks/fr

So I just wonder I miss something because my english

Sorry if my answer wasn't appropriate, I hope Greek will find a solution.

See you,

[greek]

Hi all,

I've already solved the issue. For whatever reason, when I installed GRUB into /Efi instead of /Boot it booted straight up.

Thanks for the help and patience.

[pietinger]

Notice that you don't need a /seperate boot either unless grub2 needs it.

This is not correct. You ALWAYS need a partition where UEFI can load the first program (stub-kernel or grub2 or refind or ...). This partition is called "ESP" = EFI System Partition (https://en.wikipedia.org/wiki/EFI_system_partition). In this partition you have at minimum one folder named "efi". It doesnt matter if it is named "EFI" or "efi" or "Efi" because this partition must be formatted with FAT32 ...

You can mount this partition to whatever mountpoint you like. If you want you can mount it to "/mnt/myEfiSP" - BUT, if you want to install grub2 you should mount it to /boot. So you have then "/boot/efi". In this efi-directory you can install ervery subfolder you want, you only have to tell UEFI the correct position of your starting programm (you do this with "efibootmgr -c ..."). When installing grub2 it creates the subfolder "gentoo", so you have /boot/efi/gentoo". I installed two stub-kernels in two other subfolders named "Boot" and "unlocked". When you look to my output of "efibootmgr -v" you will not find the path /boot/efi.... because /boot is ONLY OUR MOUNTPOINT. UEFI will see this partition native and the the first folder is /efi/ ... (for me it is /EFI/ because I did a manually "mkdir" in uppercase letters).

Code: Select all

# efibootmgr  -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0002,0000
Boot0000* gentoo        HD(2,GPT,e6cccc9a-40e0-4b59-b6d2-082596500077,0x1800,0x1fe800)/File(\EFI\gentoo\grubx64.efi)
Boot0001* DIRECT        HD(2,GPT,e6cccc9a-40e0-4b59-b6d2-082596500077,0x1800,0x1fe800)/File(\EFI\Boot\bzImage.efi)
Boot0002* UNLOCKED      HD(2,GPT,e6cccc9a-40e0-4b59-b6d2-082596500077,0x1800,0x1fe800)/File(\EFI\unlocked\bzImage.efi)

For more info look also here:
https://wiki.gentoo.org/wiki/EFI_System_Partition
https://wiki.gentoo.org/wiki/Efibootmgr
https://wiki.gentoo.org/wiki/EFI_stub_kernel
or in german: Chapter "Stub Kernel" viewtopic-t-1112848.html