Dual boot, No option for LEAP in boot menu

English Install/Boot/Login
1

Hello,

1st time poster, 1st time installing any SUSE Linux.

I have tried installing both NET/DVD Leap ISO, always end up w/out LEAP in boot menu. I am installing on an external USB WD 1TB HD, alongside latest version of Linux Mint. Internal drive is eMMC (Win 10), I was unable to install any Linux distro there. My Bios has no options for enabling/disabling eMMC.

Just before Mint Boot Menu appears, this message is on screen: “System Bootloader not found. Initializing defaults.”


jim@jHP:~$ inxi -Fxxxrz
System:
  Kernel: 5.4.0-65-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: HP product: HP Laptop 14-fq0xxx v: N/A 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: HP model: 87B7 v: 28.17 serial: <filter> UEFI: AMI v: F.20 
  date: 11/18/2020 
CPU:
  Topology: Dual Core model: AMD 3020e with Radeon Graphics bits: 64 
  type: MCP arch: Zen 2 rev: 1 L2 cache: 1024 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 4791 
  Speed: 691 MHz min/max: 800/1200 MHz boost: enabled Core speeds (MHz): 
  1: 691 2: 898 
Drives:
  Local Storage: total: 960.64 GiB used: 15.57 GiB (1.6%) 
  ID-1: /dev/sda type: USB vendor: Western Digital model: WD easystore 2647 
  size: 931.48 GiB serial: <filter> rev: 1020 scheme: GPT 
  ID-2: /dev/sdb type: USB model: Multiple Card Reader size: 29.16 GiB 
  serial: <filter> rev: 1.00 scheme: MBR 
Partition:
  ID-1: / size: 27.94 GiB used: 7.44 GiB (26.6%) fs: btrfs dev: /dev/sda2 
  ID-2: /home size: 46.57 GiB used: 1.26 GiB (2.7%) fs: btrfs dev: /dev/sda4 
  ID-3: swap-1 size: 525.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyssa main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner

I ran Boot Repair Disk and received this:

boot-info-4ppa125                                              [20210208_0208]

============================== Boot Info Summary ===============================

 => Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sda.
 => libparted MBR boot code is installed in the MBR of /dev/sdb.

sda1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 6.03
    Boot sector info:  Syslinux looks at sector 32800 of /dev/sda1 for its 
                       second stage. The integrity check of Syslinux failed. 
                       No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /boot/grub/grub.cfg /syslinux.cfg 
                       /efi/BOOT/grubx64.efi /ldlinux.sys

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        


================================ 0 OS detected =================================


============================ Architecture/Host Info ============================

CPU architecture: 64-bit
Live-session OS is Ubuntu 64-bit (Boot-Repair-Disk 64bit 20200604, bionic, x86_64)


===================================== UEFI =====================================

BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
SecureBoot disabled.

efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,0003,0000,0001,0002
Boot0000* ubuntu    HD(1,GPT,e5646349-a444-405b-b50f-be11be286c1f,0x800,0x10642b)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* Windows Boot Manager    HD(1,GPT,5f904bf9-8cf2-4843-9029-fda026ea4452,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...._...............
Boot0002* Internal Hard Disk    VenHw(f29fcb02-029e-4206-bc18-942faabafa2a,01)/eMMC(0)/HD(1,GPT,5f904bf9-8cf2-4843-9029-fda026ea4452,0x800,0x82000)..BO
Boot0003* opensuse-secureboot    HD(1,GPT,e5646349-a444-405b-b50f-be11be286c1f,0x800,0x10642b)/File(\EFI\opensuse\shim.efi)
Boot0004* USB Drive (UEFI) - SanDisk Cruzer Fit 1.27    PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(2,0)/HD(1,MBR,0x16f9c6,0x800,0x3a39c40)..BO



============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

sdb    : notGPT,    no-BIOSboot,    has---ESP,     usb-disk,    not-mmc, no-os,    2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

sdb1    : no-os,    32, nopakmgr,    no-docgrub,    nogrub,    nogrubinstall,    no-grubenv,    noupdategrub,    not-far

Partitions info (2/3): _________________________________________________________

sdb1    : is---ESP,    part-has-no-fstab,    no-nt,    no-winload,    no-recov-nor-hid,    no-bmgr,    notwinboot

Partitions info (3/3): _________________________________________________________

sdb1    : not-sepboot,    no-boot,    part-has-no-fstab,    not-sep-usr,    no---usr,    part-has-no-fstab,    std-grub.d,    sdb

fdisk -l (filtered): ___________________________________________________________

Disk sda: 29.1 GiB, 31260704768 bytes, 61056064 sectors
Disk identifier: 0x0016f9c6
      Boot Start      End  Sectors  Size Id Type
sda1  *     2048 61056063 61054016 29.1G  c W95 FAT32 (LBA)
Disk sdb: 29.2 GiB, 31312576512 bytes, 61157376 sectors
Disk identifier: 0x6d6e64d9
      Boot Start      End  Sectors  Size Id Type
sdb1  *     2048 61157375 61155328 29.2G  c W95 FAT32 (LBA)
Disk zram0: 843.5 MiB, 884498432 bytes, 215942 sectors
Disk zram1: 843.5 MiB, 884498432 bytes, 215942 sectors

parted -lm (filtered): _________________________________________________________

sda:31.3GB:scsi:512:512:msdos:SanDisk Cruzer Fit:;
1:1049kB:31.3GB:31.3GB:fat32::boot, lba;
sdb:31.3GB:scsi:512:512:msdos:Multiple Card Reader:;
1:1049kB:31.3GB:31.3GB:fat32::boot, lba;
zram1:884MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:884MB:884MB:linux-swap(v1)::;
zram0:884MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:884MB:884MB:linux-swap(v1)::;

blkid (filtered): ______________________________________________________________

NAME   FSTYPE   UUID                                 PARTUUID                             LABEL       PARTLABEL
sda                                                                                                   
└─sda1 vfat     08B3-9967                            0016f9c6-01                          BOOT-REPAIR 
sdb                                                                                                   
└─sdb1 vfat     2A07-6B36                            6d6e64d9-01                          BACK-UP     
zram0                                                                                                 
zram1                                                                                                 

df (filtered): _________________________________________________________________

        Avail Use% Mounted on
sda1    28.2G   3% /cdrom
sdb1    27.7G   5% /media/lubuntu/BACK-UP

Mount options: __________________________________________________________________

sda1   ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sdb1   rw,nosuid,nodev,relatime,uid=999,gid=999,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro

====================== sda1/boot/grub/grub.cfg (filtered) ======================

Boot-Repair-Disk session
Boot-Repair-Disk session (failsafe)

========================= sda1/syslinux.cfg (filtered) =========================

DEFAULT loadconfig

LABEL loadconfig
  CONFIG /isolinux/isolinux.cfg
  APPEND /isolinux/

==================== sda1: Location of files loaded by Grub ====================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/grub.cfg                             1

================== sda1: Location of files loaded by Syslinux ==================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             syslinux.cfg                                   1
            ?? = ??             ldlinux.sys                                    1


=============================== StdErr Messages ================================

File descriptor 63 (pipe:[58869]) leaked on lvs invocation. Parent PID 24210: /bin/bash

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.

And from Boot Repair, also this:

Please enable a repository containing the [grub-efi-amd64-signed] packages in the software sources of openSUSE Leap 15.2 (sda5). Then try again.

Any help appreciated. Thx

2

I will do some guessing, because there’s a lack of useful information.

Are you using UEFI for booting? At least some of the messages seem to suggest that.

If you are using UEFI, then where is the EFI partition? Is that on the Windows drive, or do you also have an EFI partition on the external drive?

The normal think to do, would be to update grub (probably grub-mkconfig -o /boot/grub/grub.cfg) on your Mint system. And that should add a boot entry for openSUSE. However, I am guessing that you have tried this and it didn’t work. So you are probably using “btrfs” for the root file system, and Mint possibly can’t boot openSUSE from there.

Did your openSUSE install try to install booting? And how did it want to boot. For that matter, did you boot the openSUSE installer with UEFI or with legacy booting?

3

Thanks for jumping in.

I will do some guessing, because there’s a lack of useful information.

Ask me for anything you need, I’ll get it.

Are you using UEFI for booting? At least some of the messages seem to suggest that.

Yes

If you are using UEFI, then where is the EFI partition? Is that on the Windows drive, or do you also have an EFI partition on the external drive?

Windows drive has its own, but as I said cannot write to that drive. I have 1 have EFI partition on external drive, told LEAP installer to use it.

The normal think to do, would be to update grub (probably grub-mkconfig -o /boot/grub/grub.cfg) on your Mint system. And that should add a boot entry for openSUSE. However, I am guessing that you have tried this and it didn’t work.

Actually I did not try that. Did so, and LEAP now in my boot menu (thanks!)

So you are probably using “btrfs” for the root file system, and Mint possibly can’t boot openSUSE from there.

I am using btrfs, also using it on entire Mint install.

Did your openSUSE install try to install booting?

I am not certain, other then selecting existing EFI partition in LEAP installer.

And how did it want to boot.

Sorry, not sure what you mean.

For that matter, did you boot the openSUSE installer with UEFI or with legacy booting?

UEFI.

…

Now, selecting the LEAP option for Mint boot menu, I am getting this message:

Error: file /boot/VMLinuz-5.3.18-lpl52.63-default not found.
Error: You need to load the kernel first.

Thanks again. I’m fairly new to Linux, main reason for this new machine is to learn Linux inside out.

4

Like nrickert, I’m confused by your data.

According to the data you provided, the WD 1TB HD found has only the three Mint partitions, and no eMMC device(s). It seems as though Mint is not supporting eMMC, so the report is missing information, or the filtering is excluding important data.

Possibly unfiltered output from ‘parted -l’ and ‘blkid’ and ‘lsblk’ pasted here would clarify.

Shown is what seems to be an ESP, but it’s confusingly listed as 29.2GB, way beyond the normal 100MB-500MB range for an ESP.

If your rescue media is booting in legacy/CSM mode,

5

The correct spelling of vmlinuz* is entirely lower case. Linux native filesystems are always case sensitive. Did you type that, or copy and paste it from somewhere where it was misspelled?

6

According to the data you provided, the WD 1TB HD found has only the three Mint partitions, and no eMMC device(s). It seems as though Mint is not supporting eMMC, so the report is missing information, or the filtering is excluding important data.

I’ll try and clarify. eMMC is internal storage on this new laptop with only Win 10. WD external drive is exclusively for Linux installs and back up.

jim@jHP:~$ sudo parted -l
[sudo] password for jim:         
Model: WD easystore 2647 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name       Flags
 1      1049kB  551MB   550MB   fat32           easystore  boot, esp
 2      552MB   30.6GB  30.0GB  btrfs
 3      30.6GB  31.1GB  551MB   linux-swap(v1)             swap
 4      31.1GB  81.1GB  50.0GB  btrfs
 5      81.1GB  135GB   53.7GB  btrfs
 6      397GB   451GB   53.7GB  btrfs
 7      998GB   1000GB  2149MB  linux-swap(v1)             swap


Model: Multiple Card Reader (scsi)
Disk /dev/sdb: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  31.3GB  31.3GB  primary  fat32        boot, lba



jim@jHP:~$ blkid
/dev/sda3: UUID="64b76876-ba9d-4a28-9555-fdd6b481cdd8" TYPE="swap" PARTUUID="9ca7cc5a-bbe8-460a-b648-fa9ac92cd242"
/dev/sda2: UUID="8ba14258-3c8a-4147-a4c2-f37fd5fad224" UUID_SUB="052cc658-357c-48bb-96c1-383741c03d13" TYPE="btrfs" PARTUUID="b879ba6c-03bd-4618-ba33-6aee7d98a02b"

jim@jHP:~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0 524.5M  0 part /boot/efi
├─sda2   8:2    0    28G  0 part /run/timeshift/backup
├─sda3   8:3    0   525M  0 part [SWAP]
├─sda4   8:4    0  46.6G  0 part /run/timeshift/backup-home
├─sda5   8:5    0    50G  0 part /media/jim/eda347e7-1250-48c4-bbe0-f57b1ab8ffab
├─sda6   8:6    0    50G  0 part /media/jim/afef2813-4a6a-4d93-b8b1-1677d6de1407
└─sda7   8:7    0     2G  0 part 
sdb      8:16   1  29.2G  0 disk 
└─sdb1   8:17   1  29.2G  0 part /media/jim/BACK-UP

Shown is what seems to be an ESP, but it’s confusingly listed as 29.2GB, way beyond the normal 100MB-500MB range for an ESP.

I think that is my 32 gb SD USB storage device.

If your rescue media is booting in legacy/CSM mode,

Thanks, I will see what I can do. That ISO I burned w/Mint’s native USB writer (which has been reliable) but it would not boot. So I tried again with RUFUS in Windows. I’ll see if I can find a better USB writer.

The correct spelling of vmlinuz* is entirely lower case. Linux native filesystems are always case sensitive. Did you type that, or copy and paste it from somewhere where it was misspelled?

sorry, I wrote it down after clicking LEAP in Mint boot menu (no way to copy/paste).

Thanks so much.

7

As mrmazda said, the capitalization is wrong. And you used a QUOTE block instead of a CODE block to post.

Disable secure-boot in your BIOS, and it will probably boot.

This happens because you are using the Mint shim (or Ubuntu shim), which can verify signatures on Mint kernels but not on openSUSE kernels.

Another possibility you could try: Mount the openSUSE root partition at “/mnt”.

Then look at “/mnt/etc/uefi/certs”. If there is a file there “33CEA71B.crt” you can enroll that, and then you will probably be able to boot with secure-boot enabled. To enroll:


cd /mnt/etc/uefi/certs
mokutil --import 33CEA71B.crt

On your next boot, you will get a blue screen where you can complete the enroll of that key.

What might go wrong: Perhaps that file/directory is deep in a “btrfs” subvolume, and you can’t see it. And perhaps “mokutil” is not installed for Mint.
If either of those happens, then disable secure-boot, and boot into the openSUSE system. Then copy 33CEA71B.crt to the EFI partition of Mint, which you will then be able to see in Mint (maybe with “sudo”). Then, back in Mint, try again. Install “mokutil” in Mint if needed.

8

As mrmazda said, the capitalization is wrong. And you used a QUOTE block instead of a CODE block to post.

Apologies for capitalization, & not using CODE tags. Duly noted.

Disable secure-boot in your BIOS, and it will probably boot.

secure-boot has been disabled since I installed Mint.

Thx.

9

Then it is probably because of the “btrfs”. The Mint grub may lack some changes needed for “btrfs”.

Is there a boot entry for openSUSE?

Try:

efibootmgr

to list the boot entries. That might need “sudo”. If there’s an entry named “opensuse” or “opensuse-secureboot” use that.

If the appropriate entry has a number, say 0003, then you can use:

sudo efibootmgr -n 0003

so that your next boot will use it. That can also be made permanent by changing the boot order, but the one shot “next boot” is good for at least testing.

10 
 efibootmgr

That brought up SUSE boot menu, and I can boot into LEAP. However, selecting MINT from that menu fails.

to list the boot entries. That might need “sudo”. If there’s an entry named “opensuse” or “opensuse-secureboot” use that.

If the appropriate entry has a number, say 0003, then you can use:

sudo efibootmgr -n 0003

That brings me back to Mint boot menu, with default set to LEAP. However, it will not boot.

…

I’m doing this (playing with LEAP) mostly to learn, get proficient with Linux internals. I’m just going to go through all the GRUB/GRUB2 docs and figure this out.

Thx