Rocky not showing in BIOS Boot entries

I am on a multiple OS system with 3 drives, one for rocky 8.10, one for windows, and another for NobaraOS. I recently updated my BIOS to F20d (I have the B550M DS3H), but now the boot entries only show Nobara and Windows, rocky is missing. I attempted to, in windows, run bcedit /set {bootmgr} path \EFI\rocky\grubx64.efi but that just added another Windows entry to the boot options.

Some potentially useful info

[moksh@resolve ~]$ sudo lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0   1.9T  0 disk 
├─sda1        8:1    0   600M  0 part 
├─sda2        8:2    0     1G  0 part 
├─sda3        8:3    0   1.8T  0 part 
└─sda4        8:4    0    69G  0 part 
sdb           8:16   0   1.8T  0 disk 
├─sdb1        8:17   0    16M  0 part 
└─sdb2        8:18   0   1.8T  0 part 
nvme1n1     259:0    0 931.5G  0 disk 
├─nvme1n1p1 259:1    0   600M  0 part /boot/efi
├─nvme1n1p2 259:2    0     1G  0 part /boot
└─nvme1n1p3 259:3    0 929.9G  0 part 
  ├─rl-swap 253:0    0  31.5G  0 lvm  [SWAP]
  ├─rl-home 253:1    0 828.5G  0 lvm  /home
  └─rl-root 253:2    0    70G  0 lvm  /
nvme0n1     259:4    0 465.8G  0 disk 
├─nvme0n1p1 259:5    0    16M  0 part 
└─nvme0n1p2 259:6    0 465.8G  0 part 
[moksh@resolve ~]$ sudo parted -l
Model: ATA Micron_1100_MTFD (scsi)
Disk /dev/sda: 2048GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      2097kB  631MB   629MB   fat32           EFI   boot, esp
 2      631MB   1705MB  1074MB  ext4            boot
 3      1705MB  1974GB  1973GB  btrfs           root
 4      1974GB  2048GB  74.0GB  linux-swap(v1)        swap


Model: ATA WD Blue SA510 2. (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      17.4kB  16.8MB  16.8MB               Microsoft reserved partition  msftres
 2      16.8MB  2000GB  2000GB  ntfs         Basic data partition          msftdata


Model: NVMe Device (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  17.8MB  16.8MB               Microsoft reserved partition  msftres
 2      17.8MB  500GB   500GB   ntfs         Basic data partition          msftdata


Model: NVMe Device (nvme)
Disk /dev/nvme1n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  630MB   629MB   fat32        EFI System Partition  boot, esp
 2      630MB   1704MB  1074MB  xfs
 3      1704MB  1000GB  999GB                                      lvm

[moksh@resolve ~]$ efibootmgr -uv
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0000,0002
Boot0000* Windows Boot Manager	HD(1,GPT,930879fe-42af-4704-b8ca-03d242f3b2a7,0x800,0x12c000)/File(\EFI\ROCKY\GRUBX64.EFI)䥗䑎坏S
Boot0001* Fedora	HD(1,GPT,b911ca76-7215-4458-b81d-b7e39996d393,0x1000,0x12c000)/File(\EFI\FEDORA\SHIM.EFI)
Boot0002* Windows Boot Manager	HD(1,GPT,930879fe-42af-4704-b8ca-03d242f3b2a7,0x800,0x12c000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)

First a note: the ‘lsblk’ does not require ‘sudo’. Nice. Second, with lsblk -f you do see filesystem types and UUIDs too.

You can run efibootmgr in Nobara. That can create/delete boot entries.

You have ESP on two drives? One you have mounted as /boot/efi on Nobara.
If it has the directory for Rocky too, then create entry like the “Fedora” (with correct path to shim).

If not, then mount the other ESP somewhere to check that Rocky’s files are there and
create entry with that partition UUID (that sudo blkid should tell / is on the Windows entries).

1 Like

So when it was working, how did you choose the o/s to run? Were you using the BIOS menu selector (as opposed to grub)?

The Rocky entry is no longer on the BIOS menu, but what about the boot order list in the BIOS, is it missing from there too?