TW snapshot 20230901: grub2-2.12 not really ready?
Hi there, On Sun, 03 Sep 2023, 01:00:46 +0200, Dominique Leuenberger wrote:
[...] grub2 (2.06 -> 2.12~rc1)
is anybody else having trouble with this update? Two of my systems don't boot anymore after dup'ing to this snapshot. Both end up at the grub2 rescue prompt. One is complaining about not being able to load "normal.mod", while the other one moans about "cryptotab.mod". Both systems don't use LVM, root file system in XFS, none of the file systems are encrypted, UEFI BIOSes are up2date. I have reverted to the last snapshot which still works: 20230828 May I ask why an upgrade to a "release candidate" has been chosen? I think the boot loader is such an important piece that even on Tumbleweed we should not jump onto such versions (found several e-mails which indicate that it's not ready for prime time yet)? TIA, cheers. l8er manfred
Hi Manfred, Am Sonntag, 3. September 2023, 19:22:04 BST schrieb Manfred Hollstein:
On Sun, 03 Sep 2023, 01:00:46 +0200, Dominique Leuenberger wrote:
[...] grub2 (2.06 -> 2.12~rc1)
is anybody else having trouble with this update?
No - just updated and everything works as it should Cheers Axel
On Sun, Sep 03, 2023 at 08:22:04PM +0200, Manfred Hollstein wrote:
Hi there,
Hi Manfred,
On Sun, 03 Sep 2023, 01:00:46 +0200, Dominique Leuenberger wrote:
[...] grub2 (2.06 -> 2.12~rc1)
is anybody else having trouble with this update? Two of my systems don't boot anymore after dup'ing to this snapshot. Both end up at the grub2 rescue prompt. One is complaining about not being able to load "normal.mod", while the other one moans about "cryptotab.mod".
Both systems don't use LVM, root file system in XFS, none of the file systems are encrypted, UEFI BIOSes are up2date.
Works for me -- updated ('dup'-ed) a system today. (but its with BTRFS and full disk encryption)
I have reverted to the last snapshot which still works:
20230828
May I ask why an upgrade to a "release candidate" has been chosen? I think the boot loader is such an important piece that even on Tumbleweed we should not jump onto such versions (found several e-mails which indicate that it's not ready for prime time yet)?
TIA, cheers.
l8er manfred
-- Regards, Andreas SUSE Software Solutions Germany GmbH Frankenstrasse 146, 90461 Nürnberg, Germany GF: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)
Hi Axel & Andreas, On Mon, 04 Sep 2023, 11:37:18 +0200, Andreas Herrmann wrote:
On Sun, Sep 03, 2023 at 08:22:04PM +0200, Manfred Hollstein wrote:
Hi there,
Hi Manfred,
On Sun, 03 Sep 2023, 01:00:46 +0200, Dominique Leuenberger wrote:
[...] grub2 (2.06 -> 2.12~rc1)
is anybody else having trouble with this update? Two of my systems don't boot anymore after dup'ing to this snapshot. Both end up at the grub2 rescue prompt. One is complaining about not being able to load "normal.mod", while the other one moans about "cryptotab.mod".
Both systems don't use LVM, root file system in XFS, none of the file systems are encrypted, UEFI BIOSes are up2date.
Works for me -- updated ('dup'-ed) a system today. (but its with BTRFS and full disk encryption)
thanks for your feedback!
I have reverted to the last snapshot which still works:
20230828
After the revert I locked the grub2* packages and dup'ed to 20230902 today. No issues at all. When there is a new update for grub2, I maybe try again...
May I ask why an upgrade to a "release candidate" has been chosen? I think the boot loader is such an important piece that even on Tumbleweed we should not jump onto such versions (found several e-mails which indicate that it's not ready for prime time yet)?
Any answer, e.g. Dominique? TIA, cheers. l8er manfred
Am 04.09.23 um 17:31 schrieb Manfred Hollstein:
May I ask why an upgrade to a "release candidate" has been chosen? I think the boot loader is such an important piece that even on Tumbleweed we should not jump onto such versions (found several e-mails which indicate that it's not ready for prime time yet)?
Any answer, e.g. Dominique?
The request is <https://build.opensuse.org/request/show/1105405> and you could ask the maintainers (which you can find under <https://build.opensuse.org/package/users/Base:System/grub2>). This has nothing to do with factory-maintainers, they're just packaging stewards and don't decide which versions are ready for Tumbleweed. Apart from that, this sounds like it should be a bug report. The warning on the ML is appreciated, but you're probably not going to reach the people that can fix the bug this way. Aaron
On Mon, Sep 04, 2023 at 05:31:11PM +0200, Manfred Hollstein wrote:
Hi Axel & Andreas,
On Mon, 04 Sep 2023, 11:37:18 +0200, Andreas Herrmann wrote:
On Sun, Sep 03, 2023 at 08:22:04PM +0200, Manfred Hollstein wrote:
Hi there,
Hi Manfred,
On Sun, 03 Sep 2023, 01:00:46 +0200, Dominique Leuenberger wrote:
[...] grub2 (2.06 -> 2.12~rc1)
is anybody else having trouble with this update? Two of my systems don't boot anymore after dup'ing to this snapshot. Both end up at the grub2 rescue prompt. One is complaining about not being able to load "normal.mod", while the other one moans about "cryptotab.mod".
Would you please open a bug report and attach the full error message along with the log so that we can look into it ? efibootmgr -v tree /boot/efi And the `set' command output from grub rescue shell. grub> set Both modules were present in former builds, not new in new upstream version, and I didn't remove any of them in this update so this appears to me an issue related to setup of boot entries in that there might be old grub running and in case of trying to load new grub modules would result in abi mismatch error.
Both systems don't use LVM, root file system in XFS, none of the file systems are encrypted, UEFI BIOSes are up2date.
Works for me -- updated ('dup'-ed) a system today. (but its with BTRFS and full disk encryption)
thanks for your feedback!
I have reverted to the last snapshot which still works:
20230828
After the revert I locked the grub2* packages and dup'ed to 20230902 today. No issues at all. When there is a new update for grub2, I maybe try again...
May I ask why an upgrade to a "release candidate" has been chosen? I think the boot loader is such an important piece that even on Tumbleweed we should not jump onto such versions (found several e-mails which indicate that it's not ready for prime time yet)?
It is the long overdue offical 2.12 release since 2.06 got released two years ago. The schedule was planned to be in mid of this year before they decided to go with a release candidate first. I wouldn't consider it unstable, given we have backport most prominent bleed-edge improvment from 2.11 to 2.06 over the course of time to tumbleweed (security fixes, memory manager, luks2 encryption, tpm and more) so they were tested more or less before we really go package this new version. AFAIK Debian and Arch are also updated to this version. Thanks, Michael
Any answer, e.g. Dominique?
TIA, cheers.
l8er manfred
Hi Michael, On Tue, 05 Sep 2023, 03:44:51 +0200, Michael Chang via openSUSE Factory wrote:
On Mon, Sep 04, 2023 at 05:31:11PM +0200, Manfred Hollstein wrote:
Hi Axel & Andreas,
On Mon, 04 Sep 2023, 11:37:18 +0200, Andreas Herrmann wrote:
On Sun, Sep 03, 2023 at 08:22:04PM +0200, Manfred Hollstein wrote:
Hi there,
Hi Manfred,
On Sun, 03 Sep 2023, 01:00:46 +0200, Dominique Leuenberger wrote:
[...] grub2 (2.06 -> 2.12~rc1)
is anybody else having trouble with this update? Two of my systems don't boot anymore after dup'ing to this snapshot. Both end up at the grub2 rescue prompt. One is complaining about not being able to load "normal.mod", while the other one moans about "cryptotab.mod".
Would you please open a bug report and attach the full error message along with the log so that we can look into it ?
I just manually updated the grub2-*.rpm packages from the 20230902 snapshot and rebooted. Guess what, I did not have any problems, so I cannot reproduce this anymore. Will check on all the other systems, too. When they are all OK, I don't know what went wrong when I ran "zypper dup" the other day. Otherwise I'll open a bug report with the logs you requested.
efibootmgr -v tree /boot/efi
And the `set' command output from grub rescue shell.
grub> set
Both modules were present in former builds, not new in new upstream version, and I didn't remove any of them in this update so this appears to me an issue related to setup of boot entries in that there might be old grub running and in case of trying to load new grub modules would result in abi mismatch error.
I ran "ls" at the grub rescue prompt on the broken system, which then showed all the found partitions properly, but accessing them to find modules did not work. My guess is that it had trouble with the XFS root file system. Luckily/funnily this works again after I manually installed the new grub2*2.12* packages - see above.
Both systems don't use LVM, root file system in XFS, none of the file systems are encrypted, UEFI BIOSes are up2date.
Works for me -- updated ('dup'-ed) a system today. (but its with BTRFS and full disk encryption)
thanks for your feedback!
I have reverted to the last snapshot which still works:
20230828
After the revert I locked the grub2* packages and dup'ed to 20230902 today. No issues at all. When there is a new update for grub2, I maybe try again...
May I ask why an upgrade to a "release candidate" has been chosen? I think the boot loader is such an important piece that even on Tumbleweed we should not jump onto such versions (found several e-mails which indicate that it's not ready for prime time yet)?
It is the long overdue offical 2.12 release since 2.06 got released two years ago. The schedule was planned to be in mid of this year before they decided to go with a release candidate first. I wouldn't consider it unstable, given we have backport most prominent bleed-edge improvment from 2.11 to 2.06 over the course of time to tumbleweed (security fixes, memory manager, luks2 encryption, tpm and more) so they were tested more or less before we really go package this new version.
AFAIK Debian and Arch are also updated to this version.
Thanks, Michael
Cheers. l8er manfred
participants (5)
-
Aaron Puchert -
Andreas Herrmann -
Axel Braun -
Manfred Hollstein -
Michael Chang