Solved Grub confused after installing OpenSUSE since... still finding Fedora!

[Unforgiven79]

Hi Folks!

I have just migrated from Fedora with Gnome to OpenSUSE to KDE, but... grub doesn't work at start up! And I get this happens since it finds two kernels to boot: both the old Fedora and the new OpenSUSE. Problem is, of course I should only have the new one (and Windows along with it). When I access the UEFI menu, I see it still proposes the old Fedora boots from my Kingston drive:

I have 3 disks: KINGSTON is for Linux, SanDisk for Windows, and Samsung for data storage only:

I cannot understanda why Grub should find any Fedora "residual"... do you have any idea?

Thank you

 

[Alexzee]

Hi Folks!

I have just migrated from Fedora with Gnome to OpenSUSE to KDE, but... grub doesn't work at start up! And I get this happens since it finds two kernels to boot: both the old Fedora and the new OpenSUSE. Problem is, of course I should only have the new one (and Windows along with it). When I access the UEFI menu, I see it still proposes the old Fedora boots from my Kingston drive:

View attachment 22096

View attachment 22097

I have 3 disks: KINGSTON is for Linux, SanDisk for Windows, and Samsung for data storage only:

View attachment 22098
View attachment 22099
View attachment 22100

I cannot understanda why Grub should find any Fedora "residual"... do you have any idea?

Thank you

If Grub doesn't know about the new kernel that's in your new installation of OpenSuse it won't boot.

OR> the configuration file that Grub needs to see so that OpenSuse can boot is either missing or badly mis-configured.
And the other thing that it could be is that Grub didn't install at all.

Looking at the Kingston drive it looks like the /efi/boot partition is missing a boot flag

IS that Kingston drive a USB thumb drive?

I wrote an article for this type of issue. I hope it helps.

Rescue Grub & Reinstalling Grub

It's happened to the best of us. You reboot your computer after a fresh Linux installation and all you've got is the grub rescue> prompt. You may have accidentally deleted the wrong partition or maybe an update/upgrade changed the boot order but you just aren't sure what went wrong.In this...

writerforlinux.wixsite.com

If not let me know.

 

[Unforgiven79]

Thanks a lot!
No, my Kingston drive is not a USB but a regular, internal SDD unit.

You are in fact right that the boot label is missing and possibly Grub is the "old" one and thus not updated with the new setup.
I will read your article and also try with the labelling.

 

[Alexzee]

Thanks a lot!
No, my Kingston drive is not a USB but a regular, internal SDD unit.

You are in fact right that the boot label is missing and possibly Grub is the "old" one and thus not updated with the new setup.
I will read your article and also try with the labelling.

You're welcome.

Thanks for confirming that your Kingston is a SSD install.

You can use g-parted to edit the partition that is missing the boot label and or the boot flag.

 

[Unforgiven79]

I have set the boot flag, but with no improvement.
Nonetheless, I have read your article and, after a failed attempt at setting grub at prompt, taken inspiration from your passage when you write that your BIOS had sorted the disk priorities incorrectly.
Indeed, my own BIOS had weird boot priorities settings, still calling for the former Fedora partition at #1 spot. I have re-assigned top priority to OpenSUSE, 2nd to Windows, and 3rd to OpenSUSE failsafe boot, while leaving all the remaing spots as disabled, so that Fedora is no longer even mentioned... voilà!
It now boots smooth as silk - thanks a lot!

 

[Alexzee]

I have set the boot flag, but with no improvement.
Nonetheless, I have read your article and, after a failed attempt at setting grub at prompt, taken inspiration from your passage when you write that your BIOS had sorted the disk priorities incorrectly.
Indeed, my own BIOS had weird boot priorities settings, still calling for the former Fedora partition at #1 spot. I have re-assigned top priority to OpenSUSE, 2nd to Windows, and 3rd to OpenSUSE failsafe boot, while leaving all the remaing spots as disabled, so that Fedora is no longer even mentioned... voilà!
It now boots smooth as silk - thanks a lot!

You're Welcome.
Glad to hear your system now boots.

Sounds like your BIOS did the same or similar to what I had going on last year.

Does OpenSuse still come with YAST ?
If you don't want to update with zypper in the command-line I found YAST to be easy to use.

 

[Unforgiven79]

Yes, it's got YAST.
I do not mind though to update with zypper, just like I did not mind updating Fedora with dnf.
However, I do acknowledge that GUI applications to install and maintain softwares and packages is more up to date with the pace of times.

 

[Alexzee]

Yes, it's got YAST.
I do not mind though to update with zypper, just like I did not mind updating Fedora with dnf.
However, I do acknowledge that GUI applications to install and maintain softwares and packages is more up to date with the pace of times.

Glad they didn't get rid of YAST.

Like you I'm a command-line man and use that to update all my Linux machines.

When you have time don't forget to go to the first post here in your thread and mark it soloved.
Have a good week ahead.

 

[Unforgiven79]

You too - DONE!