Only option to selected /dev/sda during uefi install for grup

sgvd

WetGeek
Another topic also discusses this. There are some use-cases where different partitions are preferable:

When moving disks between computers
When dual booting the same OS, which leads to duplicate entries without knowing which is which.

Also it just makes it very decoupled, use the BIOS for booting the OS, then use the bootloader to boot a different version than the default. It makes it easier to remove as well. Just format/remove the bootloader partition when you remove the OS. No need to find it how to remove only the entries of the OS you just removed from the shared bootloader partition. Saves some hassle. Of course, if you're not a distrohopper this is not really that beneficial, but still 🙂

jsluk
There is no need to physically remove the disks to force the installer to recognize your wanted bootloader partrition:

Boot the live USB
open up the partition manager (Disks, Gparted, etc.)
Remove the boot/esp flags of all bootloader partitions you do not want to install to
Install Solus
Reboot in new install
Put flags back to the bootloader partitions.

This does not fix your current grub, but if you reinstall this should force the installer to only see your wanted bootloader partition.

jsluk

sgvd Thanks for jumping in on this discussion. I just starting doing the distrohop thing on separate drives and I really like the Budgie DE.

sgvd Remove the boot/esp flags of all bootloader partitions you do not want to install to
Install Solus
Reboot in new install
Currently, the bootloader for Solus installed on dev/sda where I have MX Linux. If I remove the boot/flag, will I loose the ability to boot MX? Utlimately, I want to put the bootloader for Solus on dev/sde.

I searched the web and found this command.

sudo grub-mkconfig -o /boot/grub/grub.cfg
Will this fix my grup problem? Right now, Solus boots up to a terminal where I have to issue the exit command. Then Solus will boot up to the greetings / log on screen.

Here is another thought. What if I use the USB installer for MX and try the boot repair option there?
Best regards.

sgvd

jsluk
There are two solutions, and I only know for one of them what to do:

Repairing the current Solus install by moving the Solus bootloader through that grub command to the dev/sde partition.
(assuming that grub command actually does that. I do not know)
Reinstalling Solus completely with the bootloader in dev/sde
This will probably leave some nonfunctional Solus entries in the dev/sda (MX Linux) bootloader.

I have little knowledge on moving an existing grub, so I am solely talking about (2) a new Solus install. This is also the easiest, depending on how much you lose by reinstalling Solus. 😁

Just to make the steps more specific with the locations you gave:

Boot the Solus live USB

open up the partition manager (Disks, Gparted, etc.)

Format partitions on dev/sde (failed solus install)
(If not present, create boot partition on dev/sde: Fat32, 512Mb, boot/esp flags)

Remove the boot/esp flags from dev/sda (and other bootloaders I do not know about)
(MX Linux may be unbootable after this)

Install Solus to dev/sde; the dev/sde bootloader should be selectable now.

Reboot in Solus now installed on dev/sde

Open partition manager

Re-add the boot/esp flags to dev/sda
(MX Linux should work again)

jsluk

sgvd (MX Linux should work again)

Thanks to all who participated in the discussion. I booted into MX one more time and used their boot repair tool. Hopefully, that efi partition is back to normal without the Solus stuff added to it. I think what I will do at the point is to do another fresh install and see if I could put the Solus boot loader in its own proper efi partition.

Justin

https://getsol.us/articles/troubleshooting/boot-management/en/ to add boot parameters.

Justin

jsluk put the Solus boot loader in its own proper efi partition

This is always recommended.

aquasp

@Justin#28986 I was trying to dual boot with windows 10, but I could only select win10 boot manager, even creating a new fat 32 with 1024mb in gparted. I really prefer different partitions to efi. Is there anyway to do it with solus?
Thanks

Justin

aquasp What do you mean? If you want to boot via EFI you need an EFI partition. Otherwise you'll need to use legacy (BIOS) boot.

aquasp

Justin

I mean, I want to install solus in another EFI partition, but I was able to select only /dev/sda (the EFI of windows).

Justin

aquasp Ah OK. I've seen this before. If you remove the esp flag from that partition before running the installer it won't detect it. Then you can add it back after.

aquasp

Justin

I will try it, thanks!

Is there some possibility of solus installer being able to install on any fat32 partition? Thanks

Justin

aquasp Why would you want to install on FAT32? It can't even handle a file larger than 4GB.

aquasp

Justin
Oh, my bad.
I was talking about the solus boot manager, not the OS.
I mean, I need to do this thing of disabling the flags of windows boot manager to be able to select another fat32 partition to install the boot manager, but in ubiquity for instance you can install in any adequate partition

Justin

aquasp It's a bug I believe, the option is a dropdown but doesn't show all options for some reason.

aquasp

Justin
Oh, got it
I will do a youtube video in those days about how to dual boot windows 10 and solus in different partitions after what I learned here