I originally posted this reply in an other thread, because I to did not follow the guidelines for installing solus alongside windows7 with UEFI:
viewtopic.php?f=14&t=10828Re: SOLVED: clr-boot-manager can't update the kernel
Tue Aug 14, 2018 9:09 pm
I have the same problem. Usually I can just mount the efi partition and delete the old kernels, and then do the update. But now it seems to be stuck on two and a half kernel (three kernel files and two initrd files).
How can I clear out these old kernels to make room, and is possible to point my old installation to a new and larger partition, as I should have done before installing?
I then thought it finally was time to try out the Solus Plasma image. This made things even worse. This time i followed the guidelines for installing alongside windows, and created an 512mb fat32. When I rebooted, all my UEFI entries were gone. Solus Plasma was installed, and it seemed like it had used the fat32 partition I had created for it. I tried the "boot rescue" in help center, to rescue my old installation:
https://solus-project.com/articles/trou ... rescue/en/
I tried chroot in to my old solus-mate installation and run "sudo clr-boot-manager update" to make it use the newly created efi-partition on sda4. Later the old efi-partition on sda1. Non of it worked, i still had no bootentries in my UEFI. Lastly I removed the solus plasma partition, used an image to recreate windows, which cleared out the original efi on sda1, so it now only holds the files for windows booting. Only windows boots now.
Can I in any way create a new efi-partition for my old solus-mate, and make it boot again?