Missing grub entry to new install of F38

Hi

i am having a number of issues with an install of F38

First and foremost I do not have an entry to F38 on my grub menu.
To get to the login page to F38, I need to push F11 at booting, and then to select the hard disk which I know hosts F38.

I tried

$ sudo grub2-mkconfig -o /etc/grub2.cfg
Generating grub configuration file ...
Adding boot menu entry for UEFI Firmware Settings ...
done

and

$ sudo grub2-mkconfig -o /etc/grub2-efi.cfg
Generating grub configuration file ...
Adding boot menu entry for UEFI Firmware Settings ...
done

but to no avail.

Also

/boot/efi/EFI/fedora/grub.cfg is:

search --no-floppy --fs-uuid --set=dev 3e(snip)
set prefix=($dev)/grub2

export $prefix
configfile $prefix/grub.cfg

Is it ok?

I am not sure how to interpret that grubby shows all the correct entries:

[root@fedora grub2]# grubby --info=ALL
index=0
kernel="/boot/vmlinuz-6.8.4-100.fc38.x86_64"
args="ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau"
root="UUID=9f1ad084-bcae-4ccf-beed-5177bc7fe703"
initrd="/boot/initramfs-6.8.4-100.fc38.x86_64.img"
title="Fedora Linux (6.8.4-100.fc38.x86_64) 38 (Workstation Edition)"
id="1baae1104b7e46979405f0af21638585-6.8.4-100.fc38.x86_64"
index=1
kernel="/boot/vmlinuz-6.2.9-300.fc38.x86_64"
args="ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau"
root="UUID=9f1ad084-bcae-4ccf-beed-5177bc7fe703"
initrd="/boot/initramfs-6.2.9-300.fc38.x86_64.img"
title="Fedora Linux (6.2.9-300.fc38.x86_64) 38 (Workstation Edition)"
id="1baae1104b7e46979405f0af21638585-6.2.9-300.fc38.x86_64"
index=2
kernel="/boot/vmlinuz-0-rescue-1baae1104b7e46979405f0af21638585"
args="ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau"
root="UUID=9f1ad084-bcae-4ccf-beed-5177bc7fe703"
initrd="/boot/initramfs-0-rescue-1baae1104b7e46979405f0af21638585.img"
title="Fedora Linux (0-rescue-1baae1104b7e46979405f0af21638585) 38 (Workstation Edition)"
id="1baae1104b7e46979405f0af21638585-0-rescue"

Your help is welcome
cheers
mario

Can’t tell due to the snip.

The uuid has to match up with the uuid you see when running lsblk -fp.

yes, here you have it:


[root@fedora grub2]# lsblk -fp
NAME        FSTYPE FSVER LABEL                 UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
/dev/sda                                                                                           
├─/dev/sda1 vfat   FAT32                       66C8-C0B1                             579.8M     3% /boot/efi
├─/dev/sda2 ext4   1.0                         3ec538e7-43b3-4585-a545-fdf4db63799f  632.4M    28% /boot
└─/dev/sda3 btrfs        fedora_localhost-live 9f1ad084-bcae-4ccf-beed-5177bc7fe703  221.5G     4% /home
(snip)

/boot/efi/EFI/fedora/grub.cfg:

search --no-floppy --fs-uuid --set=dev 3ec538e7-43b3-4585-a545-fdf4db63799f
set prefix=($dev)/grub2

export $prefix
configfile $prefix/grub.cfg

They match, don’t they?
Also, am I missing something, don’t I need a swap partition?
Also, I don’t see any menuentry within my grub.cfg as described by Red Hat

Hey there, It looks like you never got back to us on the Failed to Upgrade F36 to F37 post , where we were going to help you fix the OS, here was your last comment :

Then you started a new thread, I am unable to install F38 , While you did leave some interesting tips about your computer set up here :

Are you trying to Dual Boot the machine with Windows or another OS? If not, What is the Boot Order in your BIOS ? If you have it set up to start something other that the HDD that Fedora is on you will get a screen prompting you for it.

Some BIOS allow you to choose the Boot Order like ( CD, Floppy, PXE or USB or another device. It’s usually 3 options and you need to assure you are setting it to the HDD you have Fedora On)

Actually, I have indeed a (out of business) second hd, with a old Debian 8 I have never used.

Disk /dev/sdb: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 850 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8D8E9E3E-D88C-4E3C-997B-1AFDF5385508

my present grb menu (debian is not working, underlying disk neither)

options for boot device


third entry gets into the working F38. HP SDD disk is relatively new.

1 Like

I am trying to understand the configuration, So you have 2 HDD’s and 1 has Debian, 1 has Fedora ? If not, when you can please provide us the answer the the question below

hammerhead corvette, please see pictures in my edited previous post. Is that enough info to understand what is going on?

Yup ! just as I suspected. . . Very clearly, Your BIOS is telling you "What Should I Boot from ??? " This is normal behaviour when there are several boot entries, The questions remain :

  • Do you have an active Debian install you would like to keep?
  • if Fedora is the only OS you want to keep, We need to clear those boot entries.

No, I have never used it (actually, I think it was even a double boot with an older Fedora, wIth the new disk, I just kept Fedora).
Yes, for the time being, I just need Fedora.

How do I clear those boot entries? (and, so to speak, where are they?)

Thanks
m.

Can you provide the results of ls /boot/loader/entries/

yep

[root@fedora mario]# ls /boot/loader/entries/
1baae1104b7e46979405f0af21638585-0-rescue.conf
1baae1104b7e46979405f0af21638585-6.2.9-300.fc38.x86_64.conf
1baae1104b7e46979405f0af21638585-6.8.4-100.fc38.x86_64.conf

see complete grubby --info=ALL at edited post 1 above.

m.

Please show us the output of efibootmgr

1 Like

@computersavvy I have to step away, if you can pick up from here would be great.

1 Like

(I tried to rearrange boot order from within BIOS, but to no avail)

[root@fedora mario]# efibootmgr
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0001,0003,0004,0007,0008,0002,0005
Boot0001* Hard Drive	BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fbb000000010000008500480050002000530053004400200053003700300030002000320035003000470042000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce64200480041005300300032003900300033003000300030003800390020003100200020002000200000007fff04000000424f00004e4fcb000000010000008500530061006d00730075006e006700200053005300440020003800350030002000450056004f002000320035003000470042000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce6320053005000310058004e004700410036003700340039003200360020005000200020002000200000007fff04000000424f00004e4fbd00000001000000850054004f0053004800490042004100200044005400300031004100430041003100300030000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000200ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce6200020002000200020002000200020002000200031002000490036004c005000380034005300460000007fff04000000424f
Boot0002* CD/DVD Drive	BBS(CDROM,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0300)0000474f00004e4fc900000001000000850048004c002d00440054002d00530054002000440056004400520041004d00200047004800320034004e005300440031000000050109000300000000010416008b12e85cec2cf040837280640e3dc85803007fff040002010c00d041030a0000000001010600001703120a000500ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce631004b00460046004e0036003300470034003500200034002000200020002000200020002000200000007fff04000000424f
Boot0003* Fedora	HD(1,GPT,0551b26a-20df-4d7c-9049-727f944c4154,0x800,0x64000)/\EFI\FEDORA\SHIM.EFI0000424f
Boot0004* debian	HD(1,GPT,0551b26a-20df-4d7c-9049-727f944c4154,0x800,0x64000)/\EFI\DEBIAN\GRUBX64.EFI0000424f
Boot0005* USB HDD	BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0900)0000474f00004e4fbf00000001000000730054004f00530048004900420041002000450078007400650072006e0061006c002000550053004200200033002e00300030003000300031000000050109000200000000010416008b12e85cec2cf040837280640e3dc85809007fff040002010c00d041030a000000000101060000140305060007007fff040001043000ef47642dc93ba041ac194d51d01b4ce6320030003100320030003100300034003000320036003400310000007fff04000000424f00004e4f9900000001000000770054004f00530048004900420041000000050109000200000000010416008b12e85cec2cf040837280640e3dc85809007fff040002010c00d041030a000000000101060000140305060011007fff040001043400ef47642dc93ba041ac194d51d01b4ce632003000320033003100300032003000300030003700310035003000460000007fff04000000424f
Boot0007* Fedora	HD(1,GPT,d37e5584-95c3-4281-ac44-3c98d101a185,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI
Boot0008* Fedora	HD(1,GPT,d37e5584-95c3-4281-ac44-3c98d101a185,0x800,0x12c000)/\EFI\FEDORA\SHIM.EFI0000424f

m.

You can use efibootmgr to modify the booting.
You are currently booted from entry 0007 so we can eliminate the unnecessary entries, especially the one that is shown as first in boot order.
One at a time try this.
sudo efibootmgr -B -b 0001
Then repeat that for the entries 0002, 0003, 0004, & 0005

You also can set a default boot order with sudo efibootmgr -o 0007,0008 which should set it so only those two entries would be in the boot order list.

Use man efibootmgr or efibootmgr --help to get more information on what that command may be able to do for you.

Hi

nope!
I may set them in a different order

[root@fedora mario]#  efibootmgr -o 0007,0008,0001,0002,0003,0004,0005
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0007,0008,0001,0002,0003,0004,0005
[root@fedora mario]#  efibootmgr
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0007,0008,0001,0002,0003,0004,0005

but it is not really saved. When i reboot, and get back to check it, it is as before :frowning:

EDIT:
some good news!
I tried efibootmgr -B -b 0001, efibootmgr -B -b 0003, and efibootmgr -B -b 0004, and indeed something got fixed.
At reboot, I got into the F38 login page (good new!); I was not shown any grub menu (why not?)
and something had been generated anew:

[root@fedora mario]#  efibootmgr
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0007,0008,000A,000B,0009,0002,0005
Boot0002* CD/DVD Drive	BBS(CDROM,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0300)0000474f00004e4fc900000001000000850048004c002d00440054002d00530054002000440056004400520041004d00200047004800320034004e005300440031000000050109000300000000010416008b12e85cec2cf040837280640e3dc85803007fff040002010c00d041030a0000000001010600001703120a000500ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce631004b00460046004e0036003300470034003500200034002000200020002000200020002000200000007fff04000000424f
Boot0005* USB HDD	BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0900)0000474f00004e4fbf00000001000000730054004f00530048004900420041002000450078007400650072006e0061006c002000550053004200200033002e00300030003000300031000000050109000200000000010416008b12e85cec2cf040837280640e3dc85809007fff040002010c00d041030a000000000101060000140305060007007fff040001043000ef47642dc93ba041ac194d51d01b4ce6320030003100320030003100300034003000320036003400310000007fff04000000424f00004e4f9900000001000000770054004f00530048004900420041000000050109000200000000010416008b12e85cec2cf040837280640e3dc85809007fff040002010c00d041030a000000000101060000140305060011007fff040001043400ef47642dc93ba041ac194d51d01b4ce632003000320033003100300032003000300030003700310035003000460000007fff04000000424f
Boot0007* Fedora	HD(1,GPT,d37e5584-95c3-4281-ac44-3c98d101a185,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI
Boot0008* Fedora	HD(1,GPT,d37e5584-95c3-4281-ac44-3c98d101a185,0x800,0x12c000)/\EFI\FEDORA\SHIM.EFI0000424f
Boot0009* Hard Drive	BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fbb000000010000008500480050002000530053004400200053003700300030002000320035003000470042000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce64200480041005300300032003900300033003000300030003800390020003100200020002000200000007fff04000000424f00004e4fcb000000010000008500530061006d00730075006e006700200053005300440020003800350030002000450056004f002000320035003000470042000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce6320053005000310058004e004700410036003700340039003200360020005000200020002000200000007fff04000000424f00004e4fbd00000001000000850054004f0053004800490042004100200044005400300031004100430041003100300030000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000200ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce6200020002000200020002000200020002000200031002000490036004c005000380034005300460000007fff04000000424f
Boot000A* Fedora	HD(1,GPT,0551b26a-20df-4d7c-9049-727f944c4154,0x800,0x64000)/\EFI\FEDORA\SHIM.EFI0000424f
Boot000B* debian	HD(1,GPT,0551b26a-20df-4d7c-9049-727f944c4154,0x800,0x64000)/\EFI\DEBIAN\GRUBX64.EFI0000424f

I am not sure to understand what is going on, and what does what.
Your tutoring is welcome.

By default the grub boot menu is hidden, but if you hold the shift key down while booting it should show.

1 Like

Are you still looking to remove these two enteies?

I see, I’ll try and report.
What I see now is that to push either F11 or DEL while booting doesn’t let me enter BIOS any more, is it ok?

EDIT:

yes, it works, very nice indeed!

(How/where could I have learned about it??)

yes, how?