Systemd-boot and grub2 destroy each others startup code

English Install/Boot/Login
1

I have been trying to multiboot Ubuntu, Mint, and openSUSE. This “used” to work.

I was running openSUSE Tumbleweed and had Mint and Ubuntu also on my computer. I destroyed my openSUSE system and rebuilt it. When I tried to log into my Mint or Ubuntu system, I got an emergency stop in the boot process. Since I like to keep some OS redundancy, I rebuilt Ubuntu. Now openSUSE wouldn’t work. My conclusion is that grub2 and systemd-boot are destroying each other’s startup sequence.

This is a serious problem and at this point, the other linux systems I would consider dual booting all use grub2.

I don’t know how to correct this problem.

2

Simplest solution is to use grub2-efi to boot Tumbleweed.

Perhaps reinstall. On the installer page, click on “Booting” and set the booting to use “grub2-efi”.

2 Likes
3

Can you post the output of efibootmgr -v , bootctl status , and lsblk -f from openSUSE? Also, what is the exact emergency error when Ubuntu or Mint fail to boot?

+1 to Neil’s advice.

4

“Can you post the output of efibootmgr -v , bootctl status , and lsblk -f from openSUSE? Also, what is the exact emergency error when Ubuntu or Mint fail to boot?”

openSUSE is not currently bootable. I stopped reinstalling systems once I realized what was happening.

5

Since openSUSE is no longer bootable, you could boot any live Linux distro via USB, and inspect the EFI boot entries (efibootmgr -v ) and the partition layout (lsblk -f ). That should help determine what changed and whether the bootloader or boot entries simply need repairing perhaps.

6

I finally rebuilt my system and made sure I was using grub. This fixed the problem. Thank you for your help.

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.