After 6 years of almost flawless Solus/Budgie performance I finally decided to wipe and reinstall my dual boot system because I need one of the OS's to be a 'mainstream' Linux (e.g. Debian based) for just a couple tasks (going with Ubuntu Budgie).

In the process, I discovered I have two boot entries for Solus, one as MBR, the other as GPT (some numbers shortened with dashes):

Boot0001* Solus Linux Bootloader HD(3,MBR,0x-----5,0x800,0x1f4000)/File(\EFI\com.solus-project\bootloaderx64.efi)
Boot0002* Solus Linux Bootloader HD(4,GPT,ef9-------2jd,0x800,0x1ff800)/File(\EFI\com.solus-project\bootloaderx64.efi)

While the previous install was based on MBR and now it's GPT, it would seem to make sense, however, since I completely wiped my HDD, shouldn't the MBR entry have been deleted? I'm wondering if this may be one of the issues that might be causing a conflict with my first attempt with a wipe and reinstall (but more likely the issue is that I should have installed Ubuntu Budgie first then Solus). Or, does Solus automatically make two entries so if one doesn't boot the other will?

Thanks,
Mike

    • [deleted]

    MichaelFinko

    since I completely wiped my HDD, shouldn't the MBR entry have been deleted?

    No. The boot entry is an EFI variable that resides on the motherboard firmware, so it doesn't get automatically removed when you wipe your drive.

      [deleted] Aha, got it, thanks! Should I delete the MBR entry (sudo efibootmgr -b 0001 -B) or just leave it as it is?

      You can remove some entries like this, but be careful not to delete the ones you are using.
      efibootmgr
      Will show you UEFI entries by numbers 0000 0001 etc
      sudo efibootmgr -b #### -B
      To remove an entry. Replace #### with number.

        BuzzPCSOS Ok, thanks. I'll be wiping and re-installing once more (to first install Ubuntu Budgie then Solus Budgie) so will delete just the MBR entry just before this.