How to down (Or upgrade) grub

English Install/Boot/Login
1

Hi Guys
It seems that the upgrade to tumbleweed 20221111 crashed my Grub configuration. That’s a bit of a shame because i can’t boot the snapshoots too.

So I booted the rescue from USB stick, mounted my root partition, mounted /proc. /sys and also /dev and chroot. So far so good. whats next?

i have tried snapper list (to roll back a working snapshoot) but

Failure (dbus fatal exception).

I tried zypper dup (to see whether there is fa fixed package around) but there is no network around.

i can execute YAST, and then over System -> Bootloader reinstall Grub from the Current Package.

Is there a downgrade Command for zypper that works offline?

2

Hi and welcome to the Forum :slight_smile:
Is this a dual(multi) boot system, and are you using UEFI to boot? If so, pop into the system BIOS and check the UEFI boot order has not changed.

3

Was your first command following chroot mount -a?

Did you first try to boot the installed system from the USB stick?

4

Ahm its a Mac, so the bootingsystem ist EFI rather than UEFI. I try to… just dont touch it :smile:?

Yes i die Idee mount -a after chroot as sugessted by the manual.

I didn even know its possible to boot an installed System out of an other (in this case Live System) Linux. I will Google that an try this next.

5

Hi
So can you press the option key and see multiple EFI Icons? Also when booted via the rescue USB, can you see if openSUSE entries exist in the output of efibootmgr -v

6

Yes. The machine has a so-called “Fusion drive”, which means that there are actually two physical drives. An SSD (sdb) and an HDD (sda). I started using linux mint next to Mac and installed it to the HDD (/dev/sda3)

However. Having an SSD but NOT use it doesn’t make too much sense. So i decided 3 of 4 Weeks ago to install opensuse to the SSD (sdb2) and that’s root (/) while I also used some free space on the HDD as /home (sda2). I kept Ubuntu “for a while” to copy over personal data (Letters, Pictures ect)

Thanks for the tip with efibootmgr -v. looks like a lot of rubbish has assembled.

BootCurrent: 0000Timeout: 5 seconds
BootOrder: 000B,0006,000A,000A,000A,0008,0009,0080,0007,0005,0004,0002
Boot0000* Windows Boot Manager    HD(1,GPT,5204615b-be46-4bdf-bbab-15baa56a9b99,0x28,0x64000)/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.}....................
Boot0001* Windows Boot Manager    HD(1,GPT,5204615b-be46-4bdf-bbab-15baa56a9b99,0x28,0x64000)/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* Windows Boot Manager    HD(1,GPT,5204615b-be46-4bdf-bbab-15baa56a9b99,0x28,0x64000)/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.}....................
Boot0003* Windows Boot Manager    HD(1,GPT,5204615b-be46-4bdf-bbab-15baa56a9b99,0x28,0x64000)/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.}....................
Boot0004* Windows Boot Manager    HD(1,GPT,5204615b-be46-4bdf-bbab-15baa56a9b99,0x28,0x64000)/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.}....................
Boot0005* linuxmint    HD(1,GPT,8bc9aaf2-0cb0-405e-a2a2-7cfadaa50c62,0x28,0x64000)/File(\EFI\linuxmint\grubx64.efi)
Boot0006* ubuntu    HD(1,GPT,8bc9aaf2-0cb0-405e-a2a2-7cfadaa50c62,0x28,0x64000)/File(\EFI\ubuntu\shimx64.efi)
Boot0007* Manjaro    HD(1,GPT,5204615b-be46-4bdf-bbab-15baa56a9b99,0x28,0x64000)/File(\EFI\Manjaro\grubx64.efi)
Boot0008* rEFInd Boot Manager    HD(1,GPT,5204615b-be46-4bdf-bbab-15baa56a9b99,0x28,0x64000)/File(\EFI\refind\refind_x64.efi)
Boot0009* ubuntu    HD(1,GPT,5204615b-be46-4bdf-bbab-15baa56a9b99,0x28,0x64000)/File(\EFI\ubuntu\shimx64.efi)
Boot000A* opensuse-secureboot    HD(1,GPT,5204615b-be46-4bdf-bbab-15baa56a9b99,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
Boot000B* opensuse-secureboot    HD(1,GPT,8bc9aaf2-0cb0-405e-a2a2-7cfadaa50c62,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
Boot0080* Mac OS X    PciRoot(0x0)/Pci(0x1c,0x5)/Pci(0x0,0x0)/Sata(0,0,0)/HD(2,GPT,4d5be32b-fa29-470b-8355-a0ff1966c288,0x64028,0xe15bfb0)/VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,d64931eb40dcac4ba12a43177821c636)/File(\7AF9ACF6-46A5-473A-ACC9-50AFE525C7B2\System\Library\CoreServices\boot.efi)
Boot0081* Mac OS X    PciRoot(0x0)/Pci(0x1c,0x5)/Pci(0x0,0x0)/Sata(0,0,0)/HD(3,GPT,0d703566-24e7-414f-aea7-dda78d927885,0xe1bffd8,0x40000)
Boot0082*     PciRoot(0x0)/Pci(0x1c,0x5)/Pci(0x0,0x0)/Sata(0,0,0)/HD(2,GPT,8ba160c6-f549-43a0-8372-ee1baaf9eb6c,0x64028,0xe19bfb0)/VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,cb2101dbdfbfdd449e8590c3f1b42a39)/File(\D90A6652-D5B7-3D80-A305-B3E009CC5E1C\System\Library\CoreServices\boot.efi)
BootFFFF*     PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(3,GPT,6cf0c9c6-10c7-4548-a4cd-193562910e88,0x745d0e68,0x135f20)/File(\System\Library\CoreServices\boot.efi)

i should probably delete some of those…

7

Hi
So with efibootmgr, select 000A opensuse-secureboot entry as ‘boot next’ and see if that will get you back, since the current default is 000B;


efibootmgr -n 000A
systemctl reboot
8

I’m afraid i can’t still not get any way beyond this point
https://am3pap003files.storage.live.com/y4mupACFPFrbSy29oQGswk_ra7oR4TFIrn1zUl33IoFvSNTdqFe8nkkzGYwGj9R-5l7Y1lwczr2uFdQ-AtHqwFSdYfGKkUqNlS81liSnYPFLP1xFrk4ZC_fXNm5VkLNZ7evz0_oamSehTYfvlmEXaBdbYt8V6Fm_aUtjf0uRmQTeIG10t8Fj_2ahR_j8cM5NMmy1atB7eImq8JV2YWjkRKXWDgCLZ0HeKanfTiTyla3Y1I?encodeFailures=1&width=1260&height=945

That’s why I tried to fix GRUB in the frist place by chroot in.
Anyway. As i have /home on a seperate Partition, i should condider to just reinstall the full system from USB Stick on the System Partiton and mound the /home partition - this might be quicker.
https://1drv.ms/u/s!ApzL8KKeKzxmriFPQzfLzdYDcuus?e=gzWWEX
https://1drv.ms/u/s!ApzL8KKeKzxmriFPQzfLzdYDcuus?e=gzWWEX

9

Hi
That’s not a grub problem, so can you select the recovery mode or an earlier snapshot to boot from? If not, then I would press the ‘e’ key to edit and then on the linuxefi line add at the end after quiet;


nomodeset

Press F10 to boot and see how that goes, but you get to grub so it’s working fine…

10

I agree. Some BIOS do not manage replacements well to prevent duplication that elevates likelihood of trouble, particularly including my own iMac. If it looks like it’s obsolete or a dupe of more recent, I would delete it.

11

I can NOT boot any snapshot or Recovery from here - that’s true. The only way to boot is by plugging a USB Key and boot from it by using the OPT key.

What is about the Security=apparmor option? I tried various options:


linuxefi ....... quiet; nomodeset
linuxefi ....... quiet; security=apparmor nomodeset
linuxefi ....... quiet; nomodeset security=apparmor

but none of this solved the solution (Sorry for typos, can’t copy and paste out of GRUB :D)

12

I think you hit this: https://bugzilla.opensuse.org/show_bug.cgi?id=1205380
A fix has been reported for TW20221114, so if you can upgrade via a chroot it should be fixed.

13

I can’t update with chroot, but I can update my USB Stick by downloading the most recent Image from the website. Afterwards, I can use Upgrade from Yast live Medium to update? At least this used to work for Leap -can anyone confirm this works with Tumbledweed too?

14

Yes. This is it. Updated to TW20221115 by using Upgrade from USB Mediun, causing YAST to Upgrade an installed System (YES it works for Tumbledweed too). Thanks guys. Problem solved.