Bug report filed: https://bugzilla.suse.com/show_bug.cgi?id=1205772 On Thu, Nov 24, 2022 at 7:09 PM Michael Chang <mchang@suse.com> wrote:
On Thu, Nov 24, 2022 at 11:24:55AM -0800, Fritz Hudnut wrote:
Packages changed: SDL2 (2.24.2 -> 2.26.0) grub2 lsof mariadb (10.9.3 -> 10.10.2) nfs-utils orc (0.4.32 -> 0.4.33) python-anyio (3.5.0 -> 3.6.2) sudo (1.9.12 -> 1.9.12p1) virtualbox (6.1.40 -> 7.0.4) virtualbox-kmp (6.1.40_k6.0.8_1 -> 7.0.4_k6.0.8_1)
Dear factory people:
Yesterday was "TW" day, so I did system maintenance and ran a zypper . . . prior to seeing this email from Dominique, sent today . . . . I saw the "grub2" listed in the upgrades and thought for a second . . . "abort" . . . but TW was previously my grub menu controller so I thought, "OK, we'll go back to TW instead of Leap 15.5 as the master grub controller" and ran it through. Shut the machine down to go to work.
This morning I boot the machine and grub menu loads . . . ONE system, just TW--rather than 7 or 8!!??? Everybody else was wiped from the list . . . ran a few commands to "restore" os-prober & shut down . . . and on cold boot . . . nothing, no grub for even TW.
Got the Super Grub2 disk out and booted into Leap 15.5 . . . ran the grub2-mkconfig command and upgraded a few packages via zypper . . . shut down. On cold boot, nothing again . . . just the black grub error window . . . .
Installed Gparted and checked for what was showing as booted and now it appears that Leap is booting from another drive rather than the one I installed it in . . . ???
Checking /etc/fstab and it appears that UUIDs have been changed . . . as well???
Giving thanks for the wonderful new grub2 package . . . seems like it's the same package that ubuntu is using?? Because about a year back ubuntu did the same thinig where it assumes to be the only system that needs booting, and messed about with the UUIDs and /etc/fstab settings of the other distros . . . now if only I could remember how I fixed it back then.
The grub change in latest snapshot seemed not to be relevant to multiple OS boot and also os-prober had not been updated for a while. This regression came as a surprise to me. Would you please open a ticket in bugzilla to follow up the issue ?
Thanks, Michael
Giving Thanks . . . . : - 0
F multi-boot guy . . . now busted down to using SuperGrub2 disk to boot a system