15.1 dup to 426.2 from 416.2 trashed GPT table

Forking from 15.1 initial comments thread.

After what seemed to be a normal zypper dup, from openSUSE-release lp151.247 to lp151.259, rebooting only produced BIOS setup. Ultimately, first several sectors were found to be trash.
Complete 52k recovery log can be found here:
http://fm.no-ip.com/Tmp/Dfsee/mush/dfsL043.txt

Partitions were all recreated, but my Debians, Mint and all three openSUSE entries are missing from NVRAM, while the raw disk and three *buntu entries remain. I booted raw to reach a grub> prompt, then went back to reexamine BIOS, found nothing to change, then booted raw again, typing out all the required grub commands at the prompt. load_video produced a not found message, but the rest worked. TW20190310 is currently booted.

# efibootmgr
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0003,0002,0000,0001
Boot0000* ubuntu
Boot0001* UEFI OS
Boot0002* ubuntu
Boot0003* ubuntu
# efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0003,0002,0000,0001
Boot0000* ubuntuCould not parse device path: Invalid argument

This is TW /boot/efi/EFI/ content

drwxr-xr-x  2 root root  8192 Jun 28  2018 .debian/
drwxr-xr-x  2 root root  8192 Jun 28  2018 .debian102/
drwxr-xr-x  3 root root  8192 Nov 27 12:49 .linuxmint1901/
drwxr-xr-x  2 root root  8192 Jun 21  2018 .opensuse01/
drwxr-xr-x  2 root root  8192 Jun 21  2018 .opensuse02/
drwxr-xr-x  3 root root  8192 Jul 18  2018 .opensuse15001/
drwxr-xr-x  2 root root  8192 Jun 21  2018 .opensuseX/
drwxr-xr-x  2 root root  8192 Jun 21  2018 .opensusetw01/
drwxr-xr-x  2 root root  8192 Jun 21  2018 .opensusetw02/
drwxr-xr-x  2 root root  8192 Jun 21  2018 .opensusetw03/
drwxr-xr-x  2 root root  8192 Jun 21  2018 .opensusetw04/
drwxr-xr-x  2 root root  8192 Nov 29 07:56 BOOT/
drwxr-xr-x  2 root root  8192 Jun 24  2018 debian10/
drwxr-xr-x  3 root root  8192 Nov 27 12:49 linuxmint19/
drwxr-xr-x  3 root root  8192 Jul 18  2018 opensuse150/
drwxr-xr-x  2 root root  8192 Jun 21  2018 opensusetw/
drwxr-xr-x  2 root root  8192 Jul 20  2018 tubuntu/

These are the headings of the relevant entries from custom.cfg:

menuentry "memtest86 7.4 EFI" 
menuentry "openSUSE TW defkernel 3 on P07" 
menuentry "openSUSE 15.0 defkernel on P08" 
menuentry "openSUSE 15.1 defkernel on P09" 
menuentry "Debian 10 Buster defkernel 3 on P10" 
menuentry "Tubuntu 18.04 defkernel 5 on P12" 
menuentry "Linuxmint 19 defkernel 5 on P13" 
menuentry "Debian 10 Fat Buster defkernel 5 on P11" 
menuentry "Debian 124 Buster defkernel 5 on P14" 
menuentry "Debian 125 Buster defkernel 5 on P15" 

What needs to be reinstalled or reconfigured before I reboot, only grub2-mkconfig, or something more? Is another TW dup required before TW’s efibootmgr will work right?

Before I found out 20190312 was released I found and installed 37-45.1 of efivar. Then I ran2 yast2-bootloader to increase the timeout, and saved.

efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0004,0003,0002,0000,0001
Boot0000* ubuntu        HD(1,GPT,5b331d7f-9488-4df5-9eed-c7250696b833,0x800,0xa0000)/File(\EFI	ubuntu\shimx64.efi)
Boot0001* UEFI OS       HD(1,GPT,5b331d7f-9488-4df5-9eed-c7250696b833,0x800,0xa0000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0002* ubuntu        HD(1,GPT,5b331d7f-9488-4df5-9eed-c7250696b833,0x800,0xa0000)/File(\EFI\linuxmint19\shimx64.efi)
Boot0003* ubuntu        HD(1,GPT,5b331d7f-9488-4df5-9eed-c7250696b833,0x800,0xa0000)/File(\EFI\.linuxmint1901\shimx64.efi)
Boot0004* opensusetw    HD(1,GPT,5b331d7f-9488-4df5-9eed-c7250696b833,0x800,0xa0000)/File(\EFI\opensusetw\grubx64.efi)

Rebooting gave me a grub> prompt on first try. BIOS remained set to UEFI disk rather than opensusetw, so worked with correct selection on 2nd try. :slight_smile:

Still need to troubleshoot what happened in duping 15.1. Any suggestions where to start that?

I’m not sure whether I can help here. I have not run into similar problems.

Yes, Tumbleweed broke “efibootmgr” a while ago. The fix was in the 20190312 snapshot which came out today.

I have not seen that problem show up in Leap 15.1.

If it is still not booting properly, you might need to run “shim-install” to properly setup the booting.

I filed a bug and attached a bunch of data y2logs don’t contain: https://bugzilla.opensuse.org/show_bug.cgi?id=1129328
15.1beta zypper dup from 416.2 (20190219) to 426.2 (20190311) trashed GPT

I’ve added myself to that bug report (CC list). I’ll wait and see what the Yast folk say after looking at the logs.