[Bug 1182592] New: 15.3 installation obliterated custom EFI bootloader entry "opensusetw"
http://bugzilla.opensuse.org/show_bug.cgi?id=1182592 Bug ID: 1182592 Summary: 15.3 installation obliterated custom EFI bootloader entry "opensusetw" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: mrmazda@earthlink.net QA Contact: jsrain@suse.com CC: nwr10cst-oslnx@yahoo.com Found By: --- Blocker: --- Created attachment 846394 --> http://bugzilla.opensuse.org/attachment.cgi?id=846394&action=edit y2logs .tgz Original Summary: 15.3 installation obliterated custom EFI bootloader entry "opensusetw" Forum thread post: https://forums.opensuse.org/showthread.php/549991-Make-new-ssd-the-boot-driv... Selected data from prior to installing 15.3 Alpha 20210207: # parted -l ... Disk /dev/sda: 512GB ... Number Start End Size File system Name Flags 1 1049kB 337MB 336MB fat32 TVGP01 EFI System (ESP) boot, esp 2 337MB 2174MB 1837MB linux-swap(v1) TVGP02 Linux Swap swap ... 7 26.7GB 35.1GB 8389MB ext4 TVGP07 openSUSE Tumbleweed ... 21 428GB 512GB 83.9GB ext2 New: Linux Data ... Disk /dev/nvme0n1: 256GB ... Number Start End Size File system Name Flags 1 1049kB 337MB 336MB ntfs EFI System (ESP) TM8FP6256G 0068 boot, esp (not formatted) 2 337MB 10.4GB 10.1GB ext4 openSUSE NVME boot from SATA test # efibootmgr (as best as I can recall) BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0000,0003,0004,0005 Boot0000* opensusetw Boot0003* UEFI OS Boot0004* UEFI: SanDisk Boot0005* CD/DVD Drive # inxi-CIMSy System: Host: asa88 Kernel: 5.10.7-1-default x86_64 bits: 64 Console: tty 3 Distro: openSUSE Tumbleweed 20210114 Machine: Type: Desktop Mobo: ASUSTeK model: A88X-PRO v: Rev X.0x serial: 140323952800121 UEFI: American Megatrends v: 2603 date: 03/10/2016 CPU: Info: Quad Core model: AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G bits: 64 type: MCP L2 cache: 2 MiB Speed: 1700 MHz min/max: 1700/3700 MHz Core speeds (MHz): 1: 1700 2: 1696 3: 1697 4: 1695 Info:...Shell: Bash inxi: 3.3.01 I booted installation 15.3 USB in UEFI mode, proceeding to select expert partitioner, format nothing, and make not partitioning changes: Mount existing /dev/sda1 320MB ESP on /boot/efi/ Mount existing /dev/nvme0n1p2 9600MB EXT4 on / Proceed to complete minimal installation and reboot. Actual behavior: Result would not boot, producing: Welcome to GRUB! error: ../../grub-core/commands/search.c:296:no such device: eb73...a77b. error: ../../grub-core/kern/fs.c:121:unknown filesystem. Entering rescue mode... grub rescue> help Unknown command -help'. grub rescue> _ While rescue booted (required as consequence of 15.3 installation): # efibootmgr BootCurrent: 0004 Timeout: 0 seconds BootOrder: 0000,0003,0004,0005 Boot0000* opensuse Boot0003* UEFI OS Boot0004* UEFI: SanDisk Boot0005* CD/DVD Drive Expected behavior: 1-attempting boot of new 15.3 succeeds 2-new efibootmgr entry for 15.3 added: Boot0001* opensuse (or Boot0002*, or Boot0006*) 3-old efibootmgr entry for TW remains: Boot0000* opensusetw (aka existing TW entry not destroyed) Epilogue: 1-After finding new installation fails to boot, I rescue restored to: # efibootmgr BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0000,0003,0004,0005 Boot0000* opensusetw Boot0003* UEFI OS Boot0004* UEFI: SanDisk Boot0005* CD/DVD Drive 2-I can boot new 15.3 on nvme0n1p2 only by copying its kernel and initrd to some native filesystem on sda and having TW's custom.cfg load them. 3-new 15.3 takes more than 4 times as long to boot to multi-user as TW according to systemd-analyze, more than 20s compared to less than 5s (new 15.3 on nvme about the same as old 15.3 on sda18). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182592 http://bugzilla.opensuse.org/show_bug.cgi?id=1182592#c1 --- Comment #1 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- Just a general comment. When you install 15.3, you should indicate which build. You should also indicate whether you used the DVD installer or the NET installer. That makes a big difference, because the repos used by the NET installer are out of date. If you want multiple NVRAM entries, I suggest you select the option to not update NVRAM in the bootloader installation. However, I'm not sure what that would have done in your situation. For me, boot speed is fine with 15.3. If the BIOS does not recognize your NVME disk, then I would expect that you would need "/boot" to be on a disk that the BIOS does recognize. That's because grub2 has to depend on BIOS services to load the kernels and to read grub.cfg. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182592 http://bugzilla.opensuse.org/show_bug.cgi?id=1182592#c2 --- Comment #2 from Felix Miata (offline until ???) <mrmazda@earthlink.net> --- (In reply to Neil Rickert from comment #1)
When you install 15.3, you should indicate which build.
76.1. What I downloaded was "Current"
You should also indicate whether you used the DVD installer or the NET installer.
DVD installer, mention intended, but an oversight. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182592 http://bugzilla.opensuse.org/show_bug.cgi?id=1182592#c3 --- Comment #3 from Felix Miata (offline until ???) <mrmazda@earthlink.net> --- Created attachment 846589 --> http://bugzilla.opensuse.org/attachment.cgi?id=846589&action=edit y2logs.tgz from another 15.3-20210207 DVD .iso installation on comment 0 UEFI Haswell PC I repeated a similar installation from DVD 20210207 iso, without enabling online repos, on comment #0 PC. Again, I elected to allow updating NVRAM, and "Boot0000* opensusetw" on sda1 was replaced with "Boot0000* opensuse" on sda21. Again, first attempt to boot failed with same message as in comment #0: [quote]Welcome to GRUB! error: ../../grub-core/commands/search.c:296:no such device: eb73...a77b. error: ../../grub-core/kern/fs.c:121:unknown filesystem. Entering rescue mode... grub rescue> help Unknown command -help'. grub rescue> _[/quote] I was able to fix this by booting the following Boot0004* into TW: #efiboomgr BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0000,0004,0005 Boot0000* opensuse Boot0004* UEFI OS Boot0005* UEFI: SanDisk This I repaired with efibootmgr, /etc/default/grub changes (to GRUB_DISTRIBUTOR="opensuse153"; and rearranging GRUB_CMDLINE_LINUX_DEFAULT=), then updated bootloader with YaST2, to result in: #efiboomgr BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0001,0000,0004,0005 Boot0000* opensusetw Boot0001* opensuse153 Boot0004* UEFI OS Boot0005* UEFI: SanDisk after which booting from the new 15.3's sda21 ESP proceeded as expected. Possibly relevant partitions were as follows: # parted -l ... Disk /dev/sda: 512GB Partition Table: gpt ... Number Start End Size File system Name Flags 1 1049kB 337MB 336MB fat32 TVGP01 EFI System (ESP) boot, esp (original) 2 337MB 2174MB 1837MB linux-swap(v1) TVGP02 Linux Swap swap ... 7 26.7GB 35.1GB 8389MB ext4 TVGP07 openSUSE Tumbleweed ... 21 427GB 428GB 273MB fat16 EFI System (ESP) test extra boot, esp (formatted by 15.3 installer) 22 428GB 428GB 524MB ext2 TVG NVME boot test 23 428GB 512GB 83.9GB ext2 New: Linux Data ... Disk /dev/nvme0n1: 256GB Partition Table: gpt ... Number Start End Size File system Name Flags 1 1049kB 337MB 336MB ntfs EFI System (ESP) TM8FP6256G 0068 boot, esp (not formatted) 2 337MB 10.4GB 10.1GB ext4 openSUSE NVME boot from SATA test In expert partitioner: ESP on sda21 was set to format and mount on /boot/efi. Formatted EXT2 on sda22 was set to mount on /boot. Formatted EXT4 on nvme0n1p2 was set to mount on /. All other partitions partitions were ignored. Again I did not enable os-prober. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1182592 http://bugzilla.opensuse.org/show_bug.cgi?id=1182592#c4 Neil Rickert <nwr10cst-oslnx@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #4 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- I can confirm this. I setup a KVM virtual machine to test it. I first installed Tumbleweed. Then I set GRUB_DISTRIBUTOR=opensusetw in "/etc/default/grub", and used Yast bootloader to update the settings. That gave an "opensusetw" as in EFI boot name. Next, I installed Leap 15.3 in a separate partition. And that install removed the entry for "opensusetw". I then tried it the other way. I change the boot name for Leap 15.3 to "opensuselp" (using GRUB_DISTRIBUTOR). Then I booted into Tumbleweed, and set "GRUB_DISTRIBUTOR=". Using Yast bootloader to update the configuration (I change the timeout by 1 second for that) and the "opensuselp" entry was deleted. It looks as if bootloader install is removing all entries with the string "opensuse" whereas it should only remove "opensuse" and "opensuse-secureboot". To me, it seems reasonably sensible to use names like "opensusetw" and "opensuselp" as alternative names, and we should not expect those to be removed. If I use GRUB_DISTRIBUTOR=Tumbleweed and GRUB_DISTRIBUTOR="Leap 15.3" then there isn't a problem. Likewise, if I set UPDATE_NVRAM=no in "/etc/sysconfig/bootloader" then there doesn't seem to be a problem. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com