Grub won't recognize Fedora distro

**DougT** · 05-Apr-2022, 05:41

Currently Leap 15.3 recognizes mint 20.3, but not Fedora 35 on booting.
Each distro is on a separate nvme device.

If I do: sudo grub2-mkconfig -o /boot/grub2/grub.cfg
then one of the messages is
Found Fedora Linux 35 (Workstation Edition) on /dev/nvme2n1p2

But in grub.cfg there is no info about Fedora and after using yast to write the boot record, there is no option for Fedora on booting.

**malcolmlewis** · 05-Apr-2022, 06:02

Originally Posted by DougT

Currently Leap 15.3 recognizes mint 20.3, but not Fedora 35 on booting.
Each distro is on a separate nvme device.

If I do: sudo grub2-mkconfig -o /boot/grub2/grub.cfg
then one of the messages is
Found Fedora Linux 35 (Workstation Edition) on /dev/nvme2n1p2

But in grub.cfg there is no info about Fedora and after using yast to write the boot record, there is no option for Fedora on booting.

Hi and welcome to the Forum

Can you show the output from the following as root user, also is this system UEFI or Legacy boot?

Code:

os-prober
{if uefi boot}
efibootmgr -v

**nrickert** · 05-Apr-2022, 06:16

Originally Posted by DougT

But in grub.cfg there is no info about Fedora and after using yast to write the boot record, there is no option for Fedora on booting.

"Fedora" is probably using "btrfs", and using a different subvolume structure than that expected by grub2 configured for "openSUSE".

That doesn't solve your problem, but it perhaps explains it.

**DougT** · 07-Apr-2022, 04:56

Originally Posted by malcolmlewis

Hi and welcome to the Forum

Can you show the output from the following as root user, also is this system UEFI or Legacy boot?

Code:

os-prober
{if uefi boot}
efibootmgr -v

os-prober:
/dev/nvme1n1p4:Linux Mint 20.3 Una (20.3):LinuxMint:linux
/dev/nvme2n1p2:Fedora Linux 35 (Workstation Edition):Fedora:linux:
btrfs:UUID=7c2e4f20-2c10-4420-b9f4-246d4e39b196:subvol=root
/dev/sdb1:MS-DOS 5.x/6.x/Win3.1:MS-DOS:chain

sudo efibootmgr -v :

EFI variables are not supported on this system.

running as root I get the same message.

As pointed out by another reply, I believe the Fedora btrs file system is the problem.

**arvidjaar** · 07-Apr-2022, 08:34

Originally Posted by DougT

oI believe the Fedora btrs file system is the problem.

Run and post full protocol of execution

Code:

START=$(date +%s)
grub2-mkconfig
journalctl --since=@$START

**gogalthorp** · 08-Apr-2022, 06:55

Another possible is that they are using different booting ie one is EFI and the other is MBR in such cases they will not see one another

Note:EFI variables are not supported on this system. is strange how old is the system If EFI is not supported then your installs must be all MBR.