Installer not seeing new efi boot partition

Djinnx

I'm new to linux, trying to install Solus, my last question about installation went ignored for the most part and now I'm having the following issue. First issue being that installing Solus is not creating a boot option in the boot menu of my uefi. So, the only time I have been able to install Solus was when I had installed Pop OS previously, to install POP OS i created a new EFI partition for boot. When installing Solus it took over the POP OS entry in my uefi, still called POP OS and even though I had since deleted that efi partion created to install POP OS. So, I thought, maybe Solus wants me to create a separate EFI Partition, so I did.

See attached screenshot, but as you can see I only have the option to chose the original windows efi partition

Any help is appreciated, please bare in mind I am new to Linux and am trying to learn, what's obvious to you might not be to me

sgvd

Djinnx
There is an issue with the installer that it will only list the first efi partition it finds, hence you always see only one value there. This is why the solution by @Justin works, as it will make the installer ignore the first (windows) efi partition.

Justin

Remove the boot flags from the windows partition and rerun the installer. You can replace the boot flags after the installation is done.

bigrammy

Justin Wish I had Know this a couple of day back.
I fixed mine by removing the drive with none efi Windows 10 and Ubuntu on it and I could then install efi on my separate dedicated Solus ssd.
There is a cautionary tale though for Windows 10 dual boot which I think should be more publicised as it cost me ALL my data on the 1tb ssd and the cause of my New installation. See my post here https://discuss.getsol.us/d/4425-can-find-my-windows-10-dual-boot-in-grub
I hope it saves someone else a super bad experience.

EDIT: 3 Fixed link.

Djinnx

Excellent thank you, I'll give this a go

Justin

bigrammy Backups are so very important. 😀

bigrammy

Justin I thought my important stuff would be safe on the separate ext4 "Storage" partition that I had made on the drive for just such an event but Sadly it wasn't because I used Solus to create it.
So even my two re-purposed external hard drives I created with Solus using ext4 would of all been rendered useless had they been connected when I booted Windows 10 or tried to retrieve data from them using Windows 10.
Like I said I removed the offending ext2fsd from my Windows 10 installation and all is fine now and I should hopefully remain safe in the future.
But and it's a big but anyone sticking a backup external drive that was created with a later Linux kernel using a ext4 partitions (maybe other ex type fs types too?) into Windows 10 will have them corrupted. Am I correct in this assumption ?

So just to confirm and for future Reference:
Which Kernel version and Solus release was this issue effective from?
Note: My Old Ubuntu 14.04 LTS and all the ext4 partitions it created were all completely unaffected.

Justin

bigrammy I'm not entirely sure why you lost data but backups should be on drives that are only connected during the backup.

bigrammy

Yes that's what I am saying.
So if made a backup that includes (ext4) using Solus or whatever using a newer Kernel version
Take it and pop it into a Windows 10 leave it a minute then put it back into linux and try get the data from it could be corrupted and for the novice this is the end of the world.
I am unsure if this only happens at windows runtime (Startup) and only affects installed hard drives or if it affects hard drives connected via USB or not?

EDIT:
Please see this https://github.com/matt-wu/Ext3Fsd/issues/6
It explains the issue and how to fix it or should I say how to make the drive readable again. The only fix is to remove ext2fsd from windows.

I am surprised this has not raised it's head more with so many dual booters around and Solus's popularity increasing.
I am not trying to make a big issue of this I just want to try prevent anyone else going through what I did and to let them know it's fixable before they take any drastic steps as I sadly did.

sgvd

bigrammy
It's not that surprising to me. There may be a lot of dual booters, but most probably would use NTFS for storage; that is the number one solution in an online search on shared storage between OSes. It's also more newb-friendly than using some third party driver.

Not to say it's the better solution, just to explain why the issue wasn't raised by more people. It's very good to have issues like these (and their solutions) documented on the forum 😉