[Bug 1218789] New: bad os launched
https://bugzilla.suse.com/show_bug.cgi?id=1218789 Bug ID: 1218789 Summary: bad os launched Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs@suse.de Reporter: epistemepromeneur@free.fr QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- I get two OS (Tumbleweed) in two different disks in my PC. Each time some boot settings are modified (grub, systemd, uefi, other ?) by updating the software then in the bios boot disk order is inverted then the wrong os is lauched. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1218789 https://bugzilla.suse.com/show_bug.cgi?id=1218789#c1 --- Comment #1 from hui <sturm-fr@web.de> --- Sounds like a Bios problem... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1218789 https://bugzilla.suse.com/show_bug.cgi?id=1218789#c4 --- Comment #4 from hui <sturm-fr@web.de> --- You pointed out in the first post that the boot order in the Bios get changed, not in grub2. You also mention that you use two Tumblewed installations. Do you have proper settings in /etc/default/grub for "GRUB_DISTRIBUTOR=xxxxx"? Set two different names to diferentiate both Tumbleweed installations.... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1218789 https://bugzilla.suse.com/show_bug.cgi?id=1218789#c7 --- Comment #7 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- I found this : If I use the command grub2-mkconfig then the order of the list of boot disks is inverted in the bios. hypothesis : each time there is an update of the grub packages, then this command is used. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1218789 https://bugzilla.suse.com/show_bug.cgi?id=1218789#c8 --- Comment #8 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- I forgot some information about the problem. The default OS uses a NVMe storage. The alternative OS uses an HD storage. Perhaps this is a parameter of the problem. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1218789 https://bugzilla.suse.com/show_bug.cgi?id=1218789#c9 Neil Rickert <nwr10cst-oslnx@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx@yahoo.com --- Comment #9 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- What you are describing actually sounds normal for UEFI systems. That is to say, it isn't really a bug. It happens here. Since you have the default GRUB_DISTRIBUTOR on both systems, they share the same UEFI boot entries (unless you have separate EFI partitions on each). When there is a grub2 update, that updates the files in "/boot/efi/EFI/opensuse", and the most recently updated will be selected for booting. I manage this by manually updating files in "/boot/efi/EFI/opensuse". As an alternative, in the Tumbleweed system that you do not want to control the boot, you can edit "/etc/sysconfig/bootloader" and change the "LOADER_TYPE" line to: LOADER_TYPE="" That should prevent updating grub2 on that system, so that it does not take over control of booting. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1218789 https://bugzilla.suse.com/show_bug.cgi?id=1218789#c11 --- Comment #11 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- (In reply to Episteme PROMENEUR from comment #10)
Each one gets an EFI partition.
Okay. Since each system has its own EFI partition, this is easy to fix. Use Yast boot loader. Uncheck the box "Update NVRAM Entry" Click Ok to save that change. You only need to do this on the system that you do not want to control booting. You can do it on both systems if you wish. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1218789 https://bugzilla.suse.com/show_bug.cgi?id=1218789#c12 --- Comment #12 from Episteme PROMENEUR <epistemepromeneur@free.fr> ---
Uncheck the box "Update NVRAM Entry"
This does not fix the problem. The folowing packages has been updated. grub2 grub2 i386 pc grub2 x86_64 efi grub2 snapper plugin grub2 snapper i386 pc extras grub2 x86_64 efi extras grub2 systemd sleep -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1218789 https://bugzilla.suse.com/show_bug.cgi?id=1218789#c13 Episteme PROMENEUR <epistemepromeneur@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #13 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- The problem is fixed. @Neil Rickert Many thanks -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com