openSUSE 15.1 is stuck in GRUB2 bash

My openSUSE 15.1 is installed to a BTRFS, LUKS2 LVM, UEFI only computer, during installation I got asked to select a separated partition for /boot/efi. After finishing the installation and restart, the OS only can boot into GRUB2 bash, how can I do?

I start the installer by booting USB pendrive which contains a very small image openSUSE-Leap-15.1-NET-x86_64.iso, its boot screen in UEFI computer has no option to select the installation image from a hard disk, I enter Installation on the screen menu, after loading failed it would switch to a screen with more options including the installation image from a hard disk. So I did it and everything is ok until restart to GRUB2.

I’m not sure what “GRUB2 bash” means. I’m guessing that you have a grub2 minimal shell.

At this stage, it is not at all clear what you did. It is not even clear whether you completed the install.

Maybe you can provide a bit more information.

Note that you should be able to boot the NET installer to the “rescue system”. At the login prompt, login as root (no password required). And you can maybe look around the system, check what partitions you have

parted -l

I don’t put my disk schema on the network for some reason, I have installed openSUSE several times over years before this time, that I switch my computer from UEFI+Legacy to UEFI Only, disk from MBR to GTP.

Many people use UEFI only, GPT partitioning – and they are not having problems.

It is your choice whether you provide more information. But it is difficult to help without information about your system.

The problem of grub2 failure is that the system defaultly set the /boot mountpoint in the encrypted partition. In fact both /boot and /boot/efi should have their own seperated physical partition. Its what I do, but can I have only one partition to contain both /boot and /boot/efi?

This seems confused.

Yes, “/boot” can be a separate partition. But you will need to use the expert partitioner during install if you want that. The default is for “/boot” to be part of the root file system. And “/boot/efi” is always a separate partition. It is the system EFI partition, with a FAT32 file system.

I normally use a separate “/boot” partition, because it makes encryption easier. But I also have two systems where “/boot” is part of the encrypted root file system. That still works. I am prompted for the encryption key by grub during boot – before I see a boot menu. And I am prompted a second time for the encryption key after the kernel has been loaded. That’s a minor inconvenience (the need to give key twice). But it does work.

If you are using “btrfs” for the root file system, it is better to not have a separate “/boot”. I normally use “ext4” for the root file system, so a separate “/boot” is fine.

I still don’t know enough about your system to be able to help with your boot problem.

Here’s a possibility that just occurred to me.

When I boot a system setup as you hint, the first thing that I see on the screen is:

Welcome to GRUB!

Attempting to decrypt master key...
Enter passphrase for hd0,gpt2 (e80a722f877d4572a68903e088c26c7c): 

If I were to just hit enter at that point, then I would get a minimal grub shell.

Instead, I must enter the encryption key. And I must get it right. If I enter it wrongly, I will need to use CTRL-ALT-DEL to restart the boot process.

Incidentally, that string of numbers and letters (really hex digits) in parentheses is the UUID of the encrypted partition.