1. Doing 2.12 backports to Jammy will happen, but it's not an overnight process. The delta from 2.06 to 2.12 is large, and even though it might work on your and my machine. We are hoping that the 2.12 release to Debian testing now, upload to Debian -backports later, and release to Noble in April will give us more time to see the effect in the field.
Some minor breakage on old and odd machines will happen, I know that, as we have changed the entire kernel loading mechanism going from 2.12 -> 2.06, but hopefully it can be kept as minimal as possible. I am already in the process of integrating patches for issues reported in reaction to the Debian testing roll-out. 2. The PPA breaking Jammy has an additional very different reason to not doing 2.12 backports right now, it's because of the wrong build OS being used, basically: If you only install grub-efi-* from the PPA it's less likely to break, but the problem is `grub*-common` is linked against user-space shlibs from Noble which can and will be newer than Jammy's, and ABI backwards compatibility isn't exactly always a guarantee. The correct solution for Jammy would be to upload the same package with a slightly different version number and `jammy` as the series in d/changelog to a PPA, and then have "deb [trusted=yes] https://ppa.launchpadcontent.net/your_user_here/ppa_here/ubuntu/ jammy main" in sources. If you want a GRUB 2.12 build for Jammy right now, I can upload that to a PPA in my namespace. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397&highlight=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
