Hi
Can you use;
gdisk -l /dev/sda
“lsblk -o +partuuid” would be more informative.
It does exactly match /dev/sda6, so it is likely the partition which is used as /boot/efi by openSUSE.
Boot0003* openSUSE HD(5,GPT,6a40e21d-6045-48d8-8ca3-94620ed1e964,0x74e57000,0x117701)/File(\EFI\opensuse\grubx64.efi)
This looks more like leftover from some previous installation.
Okay. So that’s “/dev/sda6”.
Here’s what I suggest you now try:
Again, boot your live media, and get a terminal. That is, open a “konsole” window and us “su” to get a root command line.
Mount your root partition at “/mnt” as before. I think that was “/dev/sda9”.
So try this. Lines beginning with ### are just my comments, and don’t need to be typed in.
mount /dev/sda9
mkdir /mnt/boot/efi
mount /dev/sda6 /mnt/boot/efi
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
### this is now a chroot rescue environment
mount -a
### that mounts anything else, including btrfs subvolumes
shim-install
grub2-mkconfig -o /boot/grub2/grub.cfg
### this should install booting so that it works
exit
### that leaves the rescue environment
Now reboot, and see if you can boot into your system.
If that works, there is still more to do from within the system. So be sure to report back how this works out.
linux@MININT-J122378:~> su -
MININT-J122378:~ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9EA32C74-8472-4238-AE99-D7C9EC5DE8E1
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2157 sectors (1.1 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 3074047 1.5 GiB EF00 EFI system partition
2 3074048 7170047 2.0 GiB 0C01 Microsoft reserved ...
3 7170048 107726847 47.9 GiB 0700 Basic data partition
4 112967680 145735679 15.6 GiB 8200
5 107726848 111822847 2.0 GiB 2700 Basic data partition
6 111822848 112967679 559.0 MiB 0700 primary
7 145735680 268615679 58.6 GiB 8300 linux partition
8 268615680 391495679 58.6 GiB 8300 linux partition
9 391495680 516423679 59.6 GiB 8300 limux partition
10 516423680 641351679 59.6 GiB 8300 linux partition
11 641351680 3907028991 1.5 TiB 0700 linux dati
MININT-J122378:~ #
MININT-J122378:~ # lsblk -o +partuuid
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT PARTUUID
loop0 7:0 0 797.1M 1 loop /run/initramfs/squashfs_container
loop1 7:1 0 4.5G 1 loop /run/rootfsbase
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 1.5G 0 part ce96f7fa-91a6-42d0-8fdd-20c80fc00c55
├─sda2 8:2 0 2G 0 part 2fa39131-2b4b-4daf-b83e-1f5d11b50fc2
├─sda3 8:3 0 48G 0 part b621e3b7-caa0-44a8-a32b-853aee9ff875
├─sda4 8:4 0 15.6G 0 part 2996bf14-0442-4b50-8164-bd44bf85e30b
├─sda5 8:5 0 2G 0 part 3c870263-4971-4713-8d1b-e1a504f9d1b4
├─sda6 8:6 0 559M 0 part 6a40e21d-6045-48d8-8ca3-94620ed1e964
├─sda7 8:7 0 58.6G 0 part 7c4bd3a8-ee6d-4277-9a82-96aebdf675c4
├─sda8 8:8 0 58.6G 0 part 898aab0f-2cd7-4a71-bea4-faba088d20d5
├─sda9 8:9 0 59.6G 0 part c43b3118-888a-4f85-89d9-be1cb404e2d8
├─sda10 8:10 0 59.6G 0 part 0a6537d7-907a-4148-a39b-38b0c87df7f0
└─sda11 8:11 0 1.5T 0 part 1ab93a1b-b346-405a-8ee0-0dd33d45dbbb
sdb 8:16 1 7.5G 0 disk
├─sdb1 8:17 1 895M 0 part /run/initramfs/live 74cbb7c4-01
├─sdb2 8:18 1 15M 0 part 74cbb7c4-02
└─sdb3 8:19 1 6.6G 0 part /run/overlayfs 74cbb7c4-03
sdc 8:32 1 57.3G 0 disk
└─sdc1 8:33 1 57.3G 0 part /run/media/linux/STEEL 0b840e54-01
MININT-J122378:~ #
done
MININT-J122378:~ # mount /dev/sda9 /mnt
MININT-J122378:~ # mkdir /mnt/boot/efi
MININT-J122378:~ # mount /dev/sda6 /mnt/boot/efi
MININT-J122378:~ # mount --bind /dev /mnt/dev
MININT-J122378:~ # mount --bind /proc /mnt/proc
MININT-J122378:~ # mount --bind /sys /mnt/sys
MININT-J122378:~ # chroot /mnt
MININT-J122378:/ # mount -a
MININT-J122378:/ # shim-install
copying /usr/lib64/efi/grub.efi to /boot/efi/EFI/opensuse/grub.efi
Installing for x86_64-efi platform.
Installation finished. No error reported.
BootCurrent: 0004
Timeout: 2 seconds
BootOrder: 0003,0001,2003,2001,2002
Boot0000* EFI PXE 0 for IPv4 (80-FA-5B-69-82-7D)
Boot0001* Windows Boot Manager
Boot0003* openSUSE
Boot0004* EFI USB Device (SanDisk)
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
BootCurrent: 0004
Timeout: 2 seconds
BootOrder: 0002,0003,0001,2003,2001,2002
Boot0000* EFI PXE 0 for IPv4 (80-FA-5B-69-82-7D)
Boot0001* Windows Boot Manager
Boot0003* openSUSE
Boot0004* EFI USB Device (SanDisk)
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
Boot0002* opensuse-secureboot
MININT-J122378:/ # grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-5.3.18-lp152.20.7-default
Found initrd image: /boot/initrd-5.3.18-lp152.20.7-default
Found Windows Boot Manager on /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi
Found openSUSE Leap 15.1 on /dev/sda7
done
MININT-J122378:/ # exit
exit
MININT-J122378:~ #
yeaaahh manythanks it boootttsssss!!!rotfl! in leap 15.2, windows and leap 15.1, …ready for
…more to do from within the system…
I’m glad to hear that.
First: You need to make sure that “/dev/sda6” is mounted at boot.
Perhaps it already is. Check the output from
df
and see if it shows up – should be at “/boot/efi”.
From what you have already told us, I think it does not show up there. So you need to make sure that it does.
Easiest way for you to do this is to use
Yast → System → Partitioner
You will get a warning about the risks of using this. You need to take those risks.
Then click on “/dev/sda6”. There should be a “Modify” near the bottom of the screen.
That “Modify” should offer several choices. One of those will be “Edit partition”. Click on that.
On the next screen, check the box for “Mount device”.
There will be a place for mount point. That needs to be “/boot/efi”.
Then click “Next”
If you run into some errors, report that. I’m not expecting any, but since this was not set up properly for your install, I’m not sure what will happen.
If that all works out as expected, I suggest you then reboot and check again with
df
to see that it now mounts at boot.
Second: When that is working, go into Yast bootloader.
Make sure that it says “GRUB2 for EFI” as the boot loader.
The box “Enable Secure Boot Support” will probably be already checked. And that’s fine.
If that looks good, click on the “Bootloader options” tab. And then change something on that screen. An easy change is to increase the “Timeout in Seconds” by 1 second. The reason for the change is to make sure that Yast doesn’t just decide that nothing needs to be done. With that change, click “OK” and Yast bootloader should make any changes needed so that your booting continues to work in the future.
it doesn’t show up
this booting in leap 15.1
pla@pla4ST:~> df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 16310504 0 16310504 0% /dev
tmpfs 16318976 883672 15435304 6% /dev/shm
tmpfs 16318976 9900 16309076 1% /run
tmpfs 16318976 0 16318976 0% /sys/fs/cgroup
/dev/sda7 60213124 13787812 43336928 25% /
/dev/sda8 60213124 4918844 52205896 9% /home
/dev/sda11 1632838652 705489612 927349040 44% /dati
tmpfs 3263792 16 3263776 1% /run/user/1000
pla@pla4ST:~>
this booting in leap 15.2
pla@pla4ST:~> df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 16281684 0 16281684 0% /dev
tmpfs 16324988 0 16324988 0% /dev/shm
tmpfs 16324988 18096 16306892 1% /run
tmpfs 16324988 0 16324988 0% /sys/fs/cgroup
/dev/sda9 61220676 6006440 52074652 11% /
/dev/sda10 61220676 12572900 45508192 22% /home
/dev/sda11 1632838652 705480444 927358208 44% /dati
tmpfs 3264996 16 3264980 1% /run/user/1000
pla@pla4ST:~>
have I to do this in both systems leap 15.1 and 15.2?
I don’t know your systems. This thread was about 15.2. I assume that Leap 15.1 was working, but that’s only a guess.
it seems ok, no errors, df is here, I made it booting in leap 15.2
booting in 15.1
pla@pla4ST:~> df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 16310504 0 16310504 0% /dev
tmpfs 16318976 0 16318976 0% /dev/shm
tmpfs 16318976 9884 16309092 1% /run
tmpfs 16318976 0 16318976 0% /sys/fs/cgroup
/dev/sda7 60213124 13788532 43336208 25% /
/dev/sda8 60213124 4899724 52225016 9% /home
/dev/sda11 1632838652 705480572 927358080 44% /dati
tmpfs 3263792 16 3263776 1% /run/user/1000
pla@pla4ST:~>
booting in 15.2
pla@localhost:~> df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 16281684 0 16281684 0% /dev
tmpfs 16324988 0 16324988 0% /dev/shm
tmpfs 16324988 18064 16306924 1% /run
tmpfs 16324988 0 16324988 0% /sys/fs/cgroup
/dev/sda9 61220676 5994800 52086292 11% /
/dev/sda6 571276 5236 566040 1% /boot/efi
/dev/sda10 61220676 12578896 45502196 22% /home
/dev/sda11 1632838652 705480572 927358080 44% /dati
tmpfs 3264996 16 3264980 1% /run/user/1000
pla@localhost:~>
as I have also leap 15.1 installed in /dev/sda7, so I would like that in the future when I upgrade it should not happen strange things, can I set to mount /dev/sda6 as /boot/efi also in 15.1 following your instructions?
Yast –> System –> Partitioner
You will get a warning about the risks of using this. You need to take those risks.
Then click on “/dev/sda6”. There should be a “Modify” near the bottom of the screen.
That “Modify” should offer several choices. One of those will be “Edit partition”. Click on that.
On the next screen, check the box for “Mount device”.
There will be a place for mount point. That needs to be “/boot/efi”.
Then click “Next”
Second: When that is working, go into Yast bootloader.
Make sure that it says “GRUB2 for EFI” as the boot loader.
The box “Enable Secure Boot Support” will probably be already checked. And that’s fine.
If that looks good, click on the “Bootloader options” tab. And then change something on that screen. An easy change is to increase the “Timeout in Seconds” by 1 second. The reason for the change is to make sure that Yast doesn’t just decide that nothing needs to be done. With that change, click “OK” and Yast bootloader should make any changes needed so that your booting continues to work in the future.
ok, also the second step worked rotfl!, manythanks again
Yes, it would be a good idea to make that change. And if you then also use Yast bootloader in the same way, your system will probably start booting to 15.1 instead of 15.2. But there will be a menu entry for 15.2, so not a big issue. Whichever last updated the bootloader will end up as default.
That’s not exactly my idea of “good idea” 
At the very least one should change GRUB_DISTRIBUTOR to use different sub-directories in ESP.
Even using GRUB_DISTRIBUTOR, the most recently updated will be the winner, because the update puts that first in boot order.
Yes, you could still use the BIOS/firmware boot menu to choose the other. But whether that works at all depends on the firmware.
On my current desktop, the firmware only accepts one NVRAM entry. So the last one updated would still win, even using different GRUB_DISTRIBUTOR and using the firmware boot menu. My other UEFI box is much better at managing multiple NVRAM entries.