[Bug 1127481] New: Upgrade to 15.1 tries to install grub-efi even though my bootloader is Legacy BIOS and fails to install packages
http://bugzilla.suse.com/show_bug.cgi?id=1127481 Bug ID: 1127481 Summary: Upgrade to 15.1 tries to install grub-efi even though my bootloader is Legacy BIOS and fails to install packages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: ktsamis@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 798527 --> http://bugzilla.suse.com/attachment.cgi?id=798527&action=edit logs Using the DVD I chose Upgrade and I saw the error in the Overview section at the end that it can't detect the efi partition so it might make my system unbootable and I should open a bug. The problem is after the upgrade was finished I didn't have a y2log but only y2log-1 and y2log-2. And I couldn't find the error in those. After reboot I do a zypper up and there are like 800 packages to be updated, all of them cached already. So that means it cached all the packages instead of installing and I had to do it again. After installing all of them I see the similar error here: Executing %posttrans script 'kernel-firmware-20190118-lp151.1.3.noarch.rpm' <3%>================================================================================================================================[\] Output of kernel-firmware-20190118-lp151.1.3.noarch.rpm %posttrans script: Creating initrd: /boot/initrd-4.12.14-lp150.12.48-default dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.12.14-lp150.12.48-default 4.12.14-lp150.12.48-default dracut: *** Including module: bash *** dracut: *** Including module: systemd *** dracut: *** Including module: warpclock *** dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: *** Including module: drm *** dracut: *** Including module: plymouth *** dracut: *** Including module: crypt *** dracut: *** Including module: dm *** dracut: Skipping udev rule: 64-device-mapper.rules dracut: Skipping udev rule: 60-persistent-storage-dm.rules dracut: Skipping udev rule: 55-dm.rules dracut: *** Including module: kernel-modules *** dracut: *** Including module: lvm *** dracut: Skipping udev rule: 64-device-mapper.rules dracut: Skipping udev rule: 56-lvm.rules dracut: Skipping udev rule: 60-persistent-storage-lvm.rules dracut: *** Including module: resume *** dracut: *** Including module: rootfs-block *** dracut: *** Including module: suse-btrfs *** dracut-install: ERROR: installing '/usr/share/doc/btrfsprogs/dracut-fsck-help.txt' to '/usr/share/fsck/fsck_help_btrfs.txt' dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.GR4CZA/initramfs /usr/share/doc/btrfsprogs/dracut-fsck-help.txt /usr/share/fsck/fsck_help_btrfs.txt dracut: *** Including module: suse-xfs *** dracut: *** Including module: terminfo *** dracut: *** Including module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut: *** Including module: dracut-systemd *** dracut: *** Including module: haveged *** dracut: *** Including module: usrmount *** dracut: *** Including module: base *** dracut: *** Including module: fs-lib *** dracut: *** Including module: shutdown *** dracut: *** Including module: suse *** dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies and firmware *** dracut: *** Installing kernel module dependencies and firmware done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done*** dracut: *** Hardlinking files *** dracut: *** Hardlinking files done *** dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing GenuineIntel.bin **** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: rd.luks.uuid=luks-3ca9e321-7a76-4dc6-9a46-8c11ac70b25e dracut: rd.lvm.lv=LVM_group/root dracut: resume=UUID=874f7a4f-4f84-4c92-a971-280b933bfea6 dracut: root=/dev/mapper/LVM_group-root rootfstype=xfs rootflags=rw,relatime,attr2,inode64,noquota dracut: *** Creating image file '/boot/initrd-4.12.14-lp151.21-default' *** dracut: *** Creating initramfs image file '/boot/initrd-4.12.14-lp151.21-default' done *** Executing %posttrans script 'grub2-i386-pc-2.02-lp151.19.2.noarch.rpm' .........................................................................<57%>===========================================================[|] Output of grub2-i386-pc-2.02-lp151.19.2.noarch.rpm %posttrans script: update-bootloader: 2019-02-27 13:20:09 <3> update-bootloader-2225 run_command.294: '/usr/lib/bootloader/grub2-efi/install' failed with exit code 1, output: <<<<<<<<<<<<<<<< target = x86_64-efi ls: cannot access '/sys/firmware/efi/efivars': No such file or directory + /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg --no-nvram --removable No valid EFI partition >>>>>>>>>>>>>>>> Executing %posttrans scripts ................................................................................................................................................................................[done] There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run 'zypper ps -s' to list these programs. Core libraries or services have been updated. Reboot is required to ensure that your system benefits from these updates. The logs are a bit of a mess for some reason after the installation, I also unpacked some tarballs trying to find the error but no luck. Maybe someone else can have better luck. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1127481 http://bugzilla.suse.com/show_bug.cgi?id=1127481#c1 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com, | |schubi@suse.com Flags| |needinfo?(jreidinger@suse.c | |om) --- Comment #1 from Stefan Schubert <schubi@suse.com> --- While calling 2019-02-27 05:12:44 <1> install(3493) [Ruby] lib/cheetah.rb:158 Executing "/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg". there are some errors around: 2019-02-27 05:12:47 <1> install(3493) [Ruby] lib/cheetah.rb:158 Executing "/usr/sbin/shim-install --config-file\=/boot/grub2/grub.cfg". 2019-02-27 05:12:47 <3> install(3493) [Ruby] lib/cheetah.rb:206 Error output: No valid EFI partition 2019-02-27 05:12:47 <3> install(3493) [Ruby] lib/cheetah.rb:178 Status: 1 2019-02-27 05:12:47 <3> install(3493) [Ruby] yast2/execute.rb:232 Execution of command "[["/usr/sbin/shim-install", "--config-file=/boot/grub2/grub.cfg"]]" failed. Exit code: 1 Error output: No valid EFI partition Josef, could you please check it ? Thanks ! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1127481 http://bugzilla.suse.com/show_bug.cgi?id=1127481#c2 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jreidinger@suse.c | |om) | --- Comment #2 from Josef Reidinger <jreidinger@suse.com> --- Konstantinos - can you please describe what you exactly did? I see in logs some failures in bootloader proposal. Do you try to edit configuration on upgrade proposal screen? ( clicking on booting headline )? What exactly you were doing during upgrade beside common clicking on next? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1127481 http://bugzilla.suse.com/show_bug.cgi?id=1127481#c3 --- Comment #3 from Konstantinos Tsamis <ktsamis@suse.com> --- (In reply to Josef Reidinger from comment #2)
Konstantinos - can you please describe what you exactly did? I see in logs some failures in bootloader proposal. Do you try to edit configuration on upgrade proposal screen? ( clicking on booting headline )? What exactly you were doing during upgrade beside common clicking on next?
No I had Legacy BIOS before and just chose upgrade and then next next. In the summary screen it showed the error that it couldn't find the right partition but I thought it would be written as well in the logs. It was basically something like: Error output: No valid EFI partition and then please report the bug with logs etc etc. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1127481 http://bugzilla.suse.com/show_bug.cgi?id=1127481#c4 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jreidinger@suse.c | |om) --- Comment #4 from Stefan Schubert <schubi@suse.com> --- So, Josef could you please check it again ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1127481 http://bugzilla.suse.com/show_bug.cgi?id=1127481#c5 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jreidinger@suse.c | |om) | --- Comment #5 from Josef Reidinger <jreidinger@suse.com> --- Well, it looks like DVD is boot with EFI. And bootloader prints warning about it, at least it is what I see in logs: proposal returns warning with level warning and msg Cannot upgrade the bootloader because of a mismatch of the boot technology. The upgraded system uses <i>Legacy BIOS boot</i> while the installation medium has been booted using <i>EFI boot</i>.<br><br>This scenario is not supported, the upgraded system may not boot or the upgrade process can fail later. So from my POV it works as expected. It should print warning on proposal screen ( I need to test if it print also additional confirmation during upgrade confirmation ). So looks like DVD is accidentally booted via EFI and not legacy ( or kernel wrongly report it as EFI ). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1127481 http://bugzilla.suse.com/show_bug.cgi?id=1127481#c6 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Basesystem Assignee|yast2-maintainers@suse.de |bnc-team-screening@forge.pr | |ovo.novell.com QA Contact|jsrain@suse.com |qa-bugs@suse.de --- Comment #6 from Stefan Schubert <schubi@suse.com> --- (In reply to Josef Reidinger from comment #5)
Well, it looks like DVD is boot with EFI. And bootloader prints warning about it, at least it is what I see in logs:
proposal returns warning with level warning and msg Cannot upgrade the bootloader because of a mismatch of the boot technology. The upgraded system uses <i>Legacy BIOS boot</i> while the installation medium has been booted using <i>EFI boot</i>.<br><br>This scenario is not supported, the upgraded system may not boot or the upgrade process can fail later.
So from my POV it works as expected. It should print warning on proposal screen ( I need to test if it print also additional confirmation during upgrade confirmation ). So looks like DVD is accidentally booted via EFI and not legacy ( or kernel wrongly report it as EFI ).
Ok, thanks. Perhaps the kernel guys can help here in order to find out why it is booted via EFI. Feel free to reassign it back, if have the opinion that it is still an YaST issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1127481 Jiachen Zhang <jiachen.zhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |mchang@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1127481 http://bugzilla.suse.com/show_bug.cgi?id=1127481#c7 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mchang@suse.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #7 from Michael Chang <mchang@suse.com> --- According to comment#6, reassign to kernel maintainers. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1127481 http://bugzilla.suse.com/show_bug.cgi?id=1127481#c11 --- Comment #11 from Josef Reidinger <jreidinger@suse.com> --- (In reply to Neil Rickert from comment #10)
I'll try this again. My first attempt to comment was botched (bad gateway message).
Comment #6 >Perhaps the kernel guys can help here in order to find out why it is booted via EFI.
This is a mistake. The kernel is not involved. Whether the DVD is booted with UEFI or legacy booting is between the user and the BIOS settings. By the time the boot menu (for the DVD) is showing, it has already been determined whether to use UEFI or legacy booting. And the kernel has not yet been loaded at that stage.
If you find yourself in this situation, go into bootloader settings (during the install), and change the bootloader from "grub2-efi" to "grub2". Then legacy booting will be used.
Perhaps there could be an option screen for this. When the update finds that it is updating a legacy-boot system, but the DVD (or USB) was booted with UEFI, maybe it could prompt the user to choose between legacy booting (as previously used) and UEFI booting (as the installer was booted).
Yeah, but only this way should be possible, as other case when originally EFI is used and now DVD booted with legacy is not possible due to missing EFI firmware variables. In general this case is quite corner case which usually does not happen. It really has nothing to do with kernel, as it is up to machine firmware if legacy or EFI boot is used. YaST can only react on it. So in case of legacy system and EFI booted medium it can allow user to force install of legacy grub and it should work. In other case we have problem and probably force user to boot properly DVD. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1127481 Matthias Brugger <mbrugger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-maintainers@forge.pr |kernel-bugs@opensuse.org |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1127481 Michal Suchanek <msuchanek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek@suse.com Component|Basesystem |Upgrade Problems Assignee|kernel-bugs@opensuse.org |autoyast-maintainers@suse.d | |e QA Contact|qa-bugs@suse.de |jsrain@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1127481 Michal Suchanek <msuchanek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|autoyast-maintainers@suse.d |yast2-maintainers@suse.de |e | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1127481 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED URL| |https://trello.com/c/HI7uPX | |fN Assignee|yast2-maintainers@suse.de |yast-internal@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1127481 https://bugzilla.suse.com/show_bug.cgi?id=1127481#c12 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #12 from Stefan Hundhammer <shundhammer@suse.com> --- This is now 4 years old, and AFAICS it was an extreme corner case to begin with. There was no action during all those years. That means that nobody found this important enough during all that time to invest any development resources. Realistically, this will not change for the forseeable future. Closing. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com