|
Bugzilla – Full Text Bug Listing |
| Summary: | bad os launched | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Episteme PROMENEUR <epistemepromeneur> |
| Component: | Bootloader | Assignee: | Bootloader Maintainers <bootloader-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | nwr10cst-oslnx |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Episteme PROMENEUR
2024-01-14 08:25:13 UTC
Sounds like a Bios problem... There is a link between package kit daily updating the OS and the boot disk order. Why you think that only the bios gets a problem ? I remember in the past (~ 10 years). I get this kind of problem. Tumbleweed fixed the problem. 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.... The boot disk order in the bios changes after updating the default Tumbleweed. I rarely go to the other tumbleweed. Only if I get a problem with the default tumbleweed. I never do anything in grub settings. It is too techie for me. Default Tumbleweed grub file contents ******************************************************************************** # If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update # /boot/grub2/grub.cfg. # Uncomment to set your own custom distributor. If you leave it unset or empty, the default # policy is to determine the value from /etc/os-release GRUB_DISTRIBUTOR= GRUB_DEFAULT=saved GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=8 GRUB_CMDLINE_LINUX_DEFAULT="splash=silent resume=/dev/disk/by-uuid/7af8e1c4-71cc-4498-9b37-6e2376e0af61 quiet nosimplefb=1 psi=1 mitigations=auto" GRUB_CMDLINE_LINUX="" # Uncomment to automatically save last booted menu entry in GRUB2 environment # variable `saved_entry' # GRUB_SAVEDEFAULT="true" #Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) # GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" #Uncomment to disable graphical terminal (grub-pc only) GRUB_TERMINAL="gfxterm" # The resolution used on graphical terminal #note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' GRUB_GFXMODE="auto" # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux # GRUB_DISABLE_LINUX_UUID=true #Uncomment to disable generation of recovery mode menu entries # GRUB_DISABLE_RECOVERY="true" #Uncomment to get a beep at grub start # GRUB_INIT_TUNE="480 440 1" GRUB_BACKGROUND= GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt SUSE_BTRFS_SNAPSHOT_BOOTING="true" GRUB_USE_LINUXEFI="true" GRUB_DISABLE_OS_PROBER="false" GRUB_ENABLE_CRYPTODISK="n" GRUB_CMDLINE_XEN_DEFAULT="vga=gfx-1024x768x16" ******************************************************************************** Other Tumbleweed grub file contents ******************************************************************************** # If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update # /boot/grub2/grub.cfg. # Uncomment to set your own custom distributor. If you leave it unset or empty, the default # policy is to determine the value from /etc/os-release GRUB_DISTRIBUTOR= GRUB_DEFAULT=saved GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=8 GRUB_CMDLINE_LINUX_DEFAULT="splash=silent resume=/dev/disk/by-uuid/7af8e1c4-71cc-4498-9b37-6e2376e0af61 quiet nosimplefb=1 psi=1 mitigations=auto" GRUB_CMDLINE_LINUX="" # Uncomment to automatically save last booted menu entry in GRUB2 environment # variable `saved_entry' # GRUB_SAVEDEFAULT="true" #Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) # GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" #Uncomment to disable graphical terminal (grub-pc only) GRUB_TERMINAL="gfxterm" # The resolution used on graphical terminal #note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' GRUB_GFXMODE="auto" # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux # GRUB_DISABLE_LINUX_UUID=true #Uncomment to disable generation of recovery mode menu entries # GRUB_DISABLE_RECOVERY="true" #Uncomment to get a beep at grub start # GRUB_INIT_TUNE="480 440 1" GRUB_BACKGROUND= GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt SUSE_BTRFS_SNAPSHOT_BOOTING="true" GRUB_USE_LINUXEFI="true" GRUB_DISABLE_OS_PROBER="false" GRUB_ENABLE_CRYPTODISK="n" GRUB_CMDLINE_XEN_DEFAULT="vga=gfx-1024x768x16" ******************************************************************************** Thanks to Yast software manager and its "historical" fonction. There had a modification whose date is 2024-01-17 in grub2 mer. 17 janv. 2024 13:00:00 Michael Chang <mchang@suse.com> - Resolved XFS regression leading to the "not a correct XFS inode" error by temporarily reverting the problematic commit (bsc#1218864) * 0001-Revert-fs-xfs-Fix-XFS-directory-extent-parsing.patch Then yesterday, there was an update of all grub2 packages to 2.12-2.1. Then this morning the bad os has been launched. 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. 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. 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. Thanks
>> 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).
>> The two os are separated.
Each system was installed by disabling the disk of the other system.
Each one gets an EFI partition.
(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. >> 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
The problem is fixed. @Neil Rickert Many thanks |