Hi there,

I'm using KDE Neon as my main operating system and i really like it. I've set up a dual boot system with Windows 10 (for gaming) and KDE Neon (for serious things such as work, photo editing and watching cat videos on youtube).

Yesterday the following happened:
Windows was running and I wanted to restart to switch to KDE Neon. However, Grub2 didn't show up, instead it booted directly into Windows again.
I've checked in the EFI settings that the boot option for KDE Neon is still present, but when I select this option it shows me the UEFI boot menu again immediately.

Up until now I've tried the following:

booted up a live CD and tried to use boot-repair https://help.ubuntu.com/community/Boot-Repair - after a few minutes it showed an error message and presented a link to the front page of pastebin.com - please note, the link didn't lead to an actual pastebin entry, it lead to the front page, so that wasn't much help

booted up a live CD and tried to reinstall Grub2 by using chroot: This improved things somehow: Now the grub command prompt is shown at startup. I can boot into KDE Neon manually by invoking set root, linux, initrd and boot as described here: https://www.linux.com/training-tutorial ... b-2-linux/

after being back in KDE Neon I reinstalled Grub2 using the following commands:

Code: Select all

sudo apt-get --reinstall install grub-common grub-efi-amd64 os-prober

This made things marginally better: I'm still greeted with Grub2's command prompt, but now I can use Grub2's configfile command to start Grub2's menu where I can select which OS should be launched.

Afterwards I've tried the following, but it didn't change anything:

Code: Select all

sudo grub-install
sudo update-grub

So in the end I am now stuck with having to invoke configfile manually at startup in Grub2's command line. This is not a total blocker, but it's still freaking me out

Here are some hopefully helpful infos:
output of fdisk -l: https://pastebin.com/McHSudKV
output of parted -l: https://pastebin.com/AUiydYPw

Do you have an idea how this can be fixed?
Any help would be greatly appreciated!

Thank you!

Achim

I think I found the solution, although I do not really undersand it:

https://unix.stackexchange.com/question ... omatically

The last answer on this page helped:

In my case, as I have KDE NEON the folder /boot/efi/EFI/ubuntu/ doesnt exist, but the folder //boot/efi/EFI/neon/ It does exist. SO the problem is that is pointing to an non exsiting folder
...
So I copied all the folder /boot/efi/EFI/neon/ to /boot/efi/EFI/ubuntu/ . That did the trick

I did this and now I finally see GRUB2's regular menu at startup.

I still don't get why this suddenly stopped working and why the folder name unter /boot/efi/EFI is expected to be "ubuntu". Maybe this is a bug in KDE Neon, where the underlying Ubuntu infrastructure wasn't correctly adapted?

Thanks for your solution. I met the same bug today.

Same issue here as soon as I deleted the "unwanted" ubuntu folder grub just broke... so I just used my bootable supergrub usb stick to fire up kde neon to copy the grub.cfg file from neon to the ubuntu folder and it did the trick! thanks for the inspiration! (only that file is for some reason needed in the ubuntu folder for kde neon to boot >.>)
It would be really helpful if someone found a way to properly fix this issue so that we can remove the ubuntu folder altogether. (kde neon 5.27 user here)