15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub menu.

**rnturner** · 25-Nov-2020, 18:44

I just finished a fresh install on a spare/repartitioned disk (used to hold 12.2 at one time) in a system. Upon rebooting, the 15.2 system(s) did not appear in the grub boot menu---just the 15.1. I'm guessing that a.) grub did not run or b.) my partitioning was flawed in some way.

New disk (Seen as /dev/sda while installing but seen as /dev/sdd under 15.1 --- why can't this be consistent????) :

Code:

# gdisk -l /dev/sdd
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/sdd: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98BA2212-3DE7-4F25-AC19-924511E79820
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         2099199   1024.0 MiB  EF00  EFI System
   2         2099200       247465983   117.0 GiB   8303  Linux x86 root (/)
   3       247465984       281020415   16.0 GiB    8200  Linux swap
   4       281020416       976773134   331.8 GiB   8300  Linux filesystem

I partitioned this disk under 15.1 and edited the entries 1 and 2 while in the installer's partitioning editor.

The 15.1 system disk (Seen as /dev/sde under 15.1. I've forgotten what the 15.1 installer called it.)

Code:

# gdisk -l /dev/sde
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/sde: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9AAAD248-47FE-45E3-9A49-37A4278764CE
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048        37750783   18.0 GiB    EF00  
   2        37750784       247465983   100.0 GiB   8300  
   3       247465984      1953525134   813.5 GiB   8300

To my eyes, these don't look appreciably different. (Other than my giving a huge EFI partition for the 15.1 config.)

Qs:

Is there a way to repair the newly installed system?

Or is a full re-installation going to be required?

Any hints/tips welcomed.

TIA...

**malcolmlewis** · 25-Nov-2020, 18:56

Hi
This won't work.... on sde

Code:

 1            2048        37750783   18.0 GiB    EF00

18GB.... 260MB is good...

Controller ports reversed, seen that on ASUS boards..., when one disk installed all ok, two or more it switches them around, review what it says in the BIOS.

**nrickert** · 25-Nov-2020, 19:09

The partitioning suggests that you are using UEFI booting. Perhaps you can confirm whether that is correct.

What is the output from

Code:

efibootmgr -v

run that as root.

If you boot into the 15.1 system, and then run:

Code:

grub2-mkconfig -o /boot/grub2/grub.cfg

then that should put a entry to boot 15.2 into the 15.1 grub boot menu.

If you boot the install media, there should be an option to boot hard drive. You could perhaps try that.

General comments:

If the installer failed to install booting, you should know about that. The installer should stop with an error message at that point, so you would not miss it. It is more likely that it did install booting, but your system is configured to boot a different way from what was installed.

**rnturner** · 25-Nov-2020, 20:24

Originally Posted by malcolmlewis

Hi
This won't work.... on sde

Code:

 1            2048        37750783   18.0 GiB    EF00

18GB.... 260MB is good...

Actually. .. it's working. I mentioned that 18GB was excessive but /dev/sde is the 15.1 boot device. I pared that down to 1GB on /dev/sda or /dev/sdd when installing the unbootable 15.2.

Controller ports reversed, seen that on ASUS boards..., when one disk installed all ok, two or more it switches them around, review what it says in the BIOS.

.
What I've seen since using openSUSE over the years is that the hardware doesn't change but the disk ordering seems to change with each release.

Any ideas why the 15.2 installation isn't booting? Is it because there is an EFI partition on the 15.1 disk as well as on the 15.2 disk? For a time, I'll be wanting to be able to boot both. (I'm beginning to long for the days of boot flags on partitions.)

**rnturner** · 25-Nov-2020, 20:51

Originally Posted by nrickert

The partitioning suggests that you are using UEFI booting. Perhaps you can confirm whether that is correct.

Yes... UEFI booting.

What is the output from

Code:

efibootmgr -v

run that as root.

Code:

# efibootmgr -v
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,000A,0001,000D,000C,0002,0007,0004,0008,000B
Boot0000* opensuse    HD(1,GPT,5029dc23-9b84-4470-acc0-ba323d9f5a10,0x800,0x2400000)/File(\EFI\opensuse\grubx64.efi)
Boot0001* opensuse-secureboot    HD(1,GPT,85ffb614-26c5-47ca-879d-b0e757bbcbe8,0x800,0x200000)/File(\EFI\opensuse\shim.efi)
Boot0002* UEFI: Built-in EFI Shell     VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0004  Hard Drive     BBS(HD,,0x0)..GO..NO........o.S.T.5.0.0.D.M.0.0.2.-.1.B.D.1.4.2....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .3.S.0.T.L.5.S.2........BO..NO........o.S.T.1.0.0.0.D.M.0.0.3.-.1.C.H.1.6.2....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .1.S.J.D.D.R.W.E........BO..NO........o.S.T.3.5.0.0.6.3.0.A.S....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .Q.9.6.G.K.K.H.1........BO..NO........o.S.T.5.0.0.D.M.0.0.2.-.1.B.D.1.4.2....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .3.Z.5.T.M.L.S.9........BO..NO........o.W.D.C. .W.D.3.0.E.F.R.X.-.6.8.E.U.Z.N.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.C.W.4.C.1.N.N.P.Z.L.6.A........BO..NO..........0.5.:.0.0.-.0. .W.D.C. .W.D.3.0.E.F.R.X.-.6.8.E.U.Z.N.0....................A..............................1.N........>.;......N..Gd-.;.A..MQ..L.0.5.:.0.0.-.0. .W.D.C. .W.D.3.0.E.F.R.X.-.6.8.E.U.Z.N.0........BO..NO..........0.5.:.0.0.-.2. .W.D.C. .W.D.1.0.E.F.R.X.-.6.8.F.Y.T.N.0....................A..............................1.N........>.;......N..Gd-.;.A..MQ..L.0.5.:.0.0.-.2. .W.D.C. .W.D.1.0.E.F.R.X.-.6.8.F.Y.T.N.0........BO..NO..........0.5.:.0.0.-.3. .W.D.C. .W.D.1.0.E.F.R.X.-.6.8.F.Y.T.N.0....................A..............................1.N........>.;......N..Gd-.;.A..MQ..L.0.5.:.0.0.-.3. .W.D.C. .W.D.1.0.E.F.R.X.-.6.8.F.Y.T.N.0........BO
Boot0007  CD/DVD Drive     BBS(CDROM,,0x0)..GO..NO........o.A.T.A.P.I. . . .i.H.A.S.3.2.4. . . .F....................A...........................>..Gd-.;.A..MQ..L.5.3.4.2.6.7. .8.J.2.6.8.5.1.0.5.6.0.8.2........BO
Boot0008  Unknown Device     BBS(9,,0x0)..GO..NO........w.S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4....................A.............................D..Gd-.;.A..MQ..L.S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4........BO..NO.........S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4....................A.....................................D..Gd-.;.A..MQ..L.S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4........BO..NO.........S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4....................A.....................................D..Gd-.;.A..MQ..L.S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4........BO
Boot000A* UEFI OS    HD(1,GPT,5029dc23-9b84-4470-acc0-ba323d9f5a10,0x800,0x2400000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot000B  Unknown Device     BBS(11,,0x0)..GO..NO..........G.e.n.e.r.i.c. .U.S.B. .S.D. .R.e.a.d.e.r. .1...0.0....................A...................................J..Gd-.;.A..MQ..L.G.e.n.e.r.i.c. .U.S.B. .S.D. .R.e.a.d.e.r. .1...0.0........BO
Boot000C* UEFI: Generic USB SD Reader 1.00    PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(1,0)/USB(3,0)/HD(1,MBR,0x0,0x2000,0xf05800)..BO
Boot000D* UEFI OS    HD(1,GPT,85ffb614-26c5-47ca-879d-b0e757bbcbe8,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)

I'm not sure how to interpret that output. Pointers welcomed.

If you boot into the 15.1 system, and then run:

Code:

grub2-mkconfig -o /boot/grub2/grub.cfg

then that should put a entry to boot 15.2 into the 15.1 grub boot menu.

When I ran that, it did find the 15.2 partition (as /dev sdd2, not /dev/sda2 as seen in the installer). I haven't shutdown yet to see what shows up in the boot menu. Stay tuned.

If you boot the install media, there should be an option to boot hard drive. You could perhaps try that.

Yes. I know. If I hadn't ejected the drive following the installation, it would have eventually taken that option. I'll have to shut down to try that. I'll post the results later.

General comments:

If the installer failed to install booting, you should know about that. The installer should stop with an error message at that point, so you would not miss it. It is more likely that it did install booting, but your system is configured to boot a different way from what was installed.

The installer didn't fail and I saw no error messages. Just the pop-up about the reboot. I ejected the DVD before the reboot occurred so it immediately went to the hard disk. Except it was the wrong one.

I also need to double check if there is something in the BIOS that is preventing the 15.2 install from booting directly. I'll update with findings.

Thanks...

**nrickert** · 25-Nov-2020, 21:11

Originally Posted by rnturner

Yes... UEFI booting.

Code:

# efibootmgr -v
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,000A,0001,000D,000C,0002,0007,0004,0008,000B
Boot0000* opensuse    HD(1,GPT,5029dc23-9b84-4470-acc0-ba323d9f5a10,0x800,0x2400000)/File(\EFI\opensuse\grubx64.efi)
Boot0001* opensuse-secureboot    HD(1,GPT,85ffb614-26c5-47ca-879d-b0e757bbcbe8,0x800,0x200000)/File(\EFI\opensuse\shim.efi)
Boot0002* UEFI: Built-in EFI Shell     VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0004  Hard Drive     BBS(HD,,0x0)..GO..NO........o.S.T.5.0.0.D.M.0.0.2.-.1.B.D.1.4.2....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .3.S.0.T.L.5.S.2........BO..NO........o.S.T.1.0.0.0.D.M.0.0.3.-.1.C.H.1.6.2....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .1.S.J.D.D.R.W.E........BO..NO........o.S.T.3.5.0.0.6.3.0.A.S....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .Q.9.6.G.K.K.H.1........BO..NO........o.S.T.5.0.0.D.M.0.0.2.-.1.B.D.1.4.2....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .3.Z.5.T.M.L.S.9........BO..NO........o.W.D.C. .W.D.3.0.E.F.R.X.-.6.8.E.U.Z.N.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.C.W.4.C.1.N.N.P.Z.L.6.A........BO..NO..........0.5.:.0.0.-.0. .W.D.C. .W.D.3.0.E.F.R.X.-.6.8.E.U.Z.N.0....................A..............................1.N........>.;......N..Gd-.;.A..MQ..L.0.5.:.0.0.-.0. .W.D.C. .W.D.3.0.E.F.R.X.-.6.8.E.U.Z.N.0........BO..NO..........0.5.:.0.0.-.2. .W.D.C. .W.D.1.0.E.F.R.X.-.6.8.F.Y.T.N.0....................A..............................1.N........>.;......N..Gd-.;.A..MQ..L.0.5.:.0.0.-.2. .W.D.C. .W.D.1.0.E.F.R.X.-.6.8.F.Y.T.N.0........BO..NO..........0.5.:.0.0.-.3. .W.D.C. .W.D.1.0.E.F.R.X.-.6.8.F.Y.T.N.0....................A..............................1.N........>.;......N..Gd-.;.A..MQ..L.0.5.:.0.0.-.3. .W.D.C. .W.D.1.0.E.F.R.X.-.6.8.F.Y.T.N.0........BO
Boot0007  CD/DVD Drive     BBS(CDROM,,0x0)..GO..NO........o.A.T.A.P.I. . . .i.H.A.S.3.2.4. . . .F....................A...........................>..Gd-.;.A..MQ..L.5.3.4.2.6.7. .8.J.2.6.8.5.1.0.5.6.0.8.2........BO
Boot0008  Unknown Device     BBS(9,,0x0)..GO..NO........w.S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4....................A.............................D..Gd-.;.A..MQ..L.S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4........BO..NO.........S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4....................A.....................................D..Gd-.;.A..MQ..L.S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4........BO..NO.........S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4....................A.....................................D..Gd-.;.A..MQ..L.S.T.2.0.0.0.D.M.0.0.1.-.1.E.R.1.6.4. .0.X.0.4........BO
Boot000A* UEFI OS    HD(1,GPT,5029dc23-9b84-4470-acc0-ba323d9f5a10,0x800,0x2400000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot000B  Unknown Device     BBS(11,,0x0)..GO..NO..........G.e.n.e.r.i.c. .U.S.B. .S.D. .R.e.a.d.e.r. .1...0.0....................A...................................J..Gd-.;.A..MQ..L.G.e.n.e.r.i.c. .U.S.B. .S.D. .R.e.a.d.e.r. .1...0.0........BO
Boot000C* UEFI: Generic USB SD Reader 1.00    PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(1,0)/USB(3,0)/HD(1,MBR,0x0,0x2000,0xf05800)..BO
Boot000D* UEFI OS    HD(1,GPT,85ffb614-26c5-47ca-879d-b0e757bbcbe8,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)

Boot0000 and Boot0001 are using different EFI partitions.

If you look at those lines in the output, the string following the "GPT" is the PARTUUID for the partition. And that value is different for the two boot entries.

Is this, by any chance, a Lenovo system?

My best guess is boot was installed fine, and Boot0001 will boot 15.2, while Boot0000 is booting 15.1.

There's possibly a key you can use, often F12, to get the BIOS boot menu. And if you try that, then select the entry named "opensuse-secureboot" to see if it works for 15.2.

Normally, the installer would delete all boot entries with "opensuse" as part of the name. And then it would create an entry (by default "opensuse-secureboot") to boot the newly installed system. And that new entry would be first in boot order.

I happen to have a Lenovo ThinkServer, and it breaks the rules. So when the installer deletes those entries, the Lenovo BIOS puts them back at the next boot. And when the installer puts the new entry first, the Lenovo BIOS ignores that and goes by its own order. Your system seems to have done something similar. So you might have to go into the BIOS settings screen to set the boot order the way that you want.

**rnturner** · 25-Nov-2020, 22:28

Originally Posted by nrickert

Boot0000 and Boot0001 are using different EFI partitions.

Which makes some sense given the partition tables I posted.

If you look at those lines in the output, the string following the "GPT" is the PARTUUID for the partition. And that value is different for the two boot entries.

I looked for that but didn't see any matching UUIDs---I didn't think to look at the PARTUUIDs ("lsblk -f" didn't show those). But it turns out to not matter so much (see below).

Is this, by any chance, a Lenovo system?

No. Older MSI motherboard.

My best guess is boot was installed fine, and Boot0001 will boot 15.2, while Boot0000 is booting 15.1.

There's possibly a key you can use, often F12, to get the BIOS boot menu. And if you try that, then select the entry named "opensuse-secureboot" to see if it works for 15.2.

MSI uses "Del".

Normally, the installer would delete all boot entries with "opensuse" as part of the name. And then it would create an entry (by default "opensuse-secureboot") to boot the newly installed system. And that new entry would be first in boot order.

I happen to have a Lenovo ThinkServer, and it breaks the rules. So when the installer deletes those entries, the Lenovo BIOS puts them back at the next boot. And when the installer puts the new entry first, the Lenovo BIOS ignores that and goes by its own order. Your system seems to have done something similar. So you might have to go into the BIOS settings screen to set the boot order the way that you want.

When I went into the BIOS, I noticed that the first hard disk in the boot order was not "opensuse-secureboot". Thinking that was the cause of the boot mystery, I changed the boot order to make sure that was the first boot device after the CD/DVD drive. Worked like a charm. Oy!

Oddly, the disks that were sdd and sde under 15.1 are now sda and sdb. I'll check in a bit to see where 15.1's sda, sdb, and sdc went under 15.2.

Thanks for the tips.

Now I'm off to settle an argument between Nouveau and nVidia... (It's been a while since I've dealt with that one.)

**nrickert** · 25-Nov-2020, 22:51

Originally Posted by rnturner

Worked like a charm. Oy!

I'm glad to hear that.

**mrmazda** · 28-Nov-2020, 03:12

Originally Posted by rnturner

Now I'm off to settle an argument between Nouveau and nVidia...

I sense a need to read the graphics driver primer.

FINAL DAY for switching accounts was 18th June, 2020. you WILL now have to create a new openSUSE Account if you did not migrate!

Thread: 15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub menu.

Thread Tools

Display

15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub menu.

Re: 15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub men

Re: 15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub men

Re: 15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub men

Re: 15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub men

Re: 15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub men

Re: 15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub men

Re: 15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub men

Re: 15.2 Installation apparently fails to run Grub. Post-installation reboot brings up 15.1 grub men

Bookmarks

Bookmarks

Posting Permissions