Hi there,

after spending hours today to find a solution for my problem I want to share my experiences. Maybe there's a Bug in KDE Neon?

I have 2 SSDs in my PC (/dev/sda, /dev/sdb). Both drives have their own EFI partition (sda1, sdb1). On sda I've installed windows and sdb is used for KDE Neon. While installing I made a mistake and used /dev/sda1 as EFI partition. Not a big problem because everything was running. But I want to be able to use both disks independently, so my bootloader for KDE Neon should be placed on sbd1.

First I formatted sdb1 as fat32 to be save with a clean partition. After this I did the following:

Code: Select all

sudo -s
umount /boot/efi
mount /dev/sdb1 /boot/efi
update-grub
grub-install
nano /etc/fstab #change UUID of EFI partition to newly formatted partition sdb1


I thought this should do the job but after restarting I landed in grub shell. There I was able to boot using

Code: Select all

set root=(hd2,2)
linux /vmlinuz root=/dev/sdb2
initrd /initrd.img
boot


After looking into my backup I found a second folder unter /boot/efi/EFI. After my fresh KDE Neon installation there have been 2 folders: "neon" and "ubuntu".
But after recreation there was only "neon". After copying neon/* to ubuntu boot process was fine.

Why does the installer creates these 2 directories? I think everything should be in "neon". If both is necessary a update-grub / install-grub should create these two directories as well. Or am I wrong and this works like intended?

Would be great if someone could follow my thoughts

€dit: Seems to be discussed here: https://bugs.kde.org/show_bug.cgi?id=369077#c2

Not sure if it makes a difference but in your snippet you seem to have done "update-grub" before "grub-install" but it should be the other way around? Also, is it right to run "grub-install" without a target location, like "grub-install /dev/sdb" ?

Thanks for your reply! Don't know the correct order so actually I used both combinations. Target for grub-install is not needed on EFI installations (at least it produces the same output, I think it's looking for an EFI mount).

Solution was to copy "ubuntu" subfolder within the EFI folder. Seems to be a known big/issue in Neon.