I'm working on trying various differing work-arounds with what is there
natively.

I tried building the newest git on Grub2 2.12. Fails building at a point
which is says way fixed for the error i am getting, but still fails on
the make at the same point. (asorti ot defined)

I'm also working on another theory, recreating bpool with differing
options, on the theory that on the creation of bpool, that some on the
zpool options are causing Grub2 to fail with those added challenges.

I'll keep you up-to date how those go. Trying to balance my time between
"real life", helping the upstream Intel Graphics Support Engineers with
drivers issues with Ubuntu, and helping Users with other issues. ...All
while trying to find underlying information answers for this issue.

What get's me, it that "feature" or "ability" that this is failing on,
being able to snapshot bpool, because that is the failure point we need
to protect from, was covered by Zsys, and why Canonical came up with
that in the first place. It worked in 20.04 LTS... There was not a
problem there, with that installed. We were able to do that in that
release. Marketing-wise, it put Ubuntu ahead of things with that "need"
covered well.

Zsys was removed from being a default install (no mention why), but I
still see commits to it. The need to make snapshots of the boot related
files is still there. I wish I knew more on the why Zsys feel from
favor. I thought basically,besides some minor changes, it was a great
idea to do what it was intended to do.

Some users, have gone around this problem by using ZFS Boot Menu (ZBM).
But that is not a solution, Rather it removes the conditions, by what
they have to do in the restructure to make it work. For it, bpool cannot
exist. There cannot be a separate /boot. /boot has to be inside the root
pool, and not inside it's own ZFS dataset... If this restructure is done
this way, then those conditions do not exist. That is why is works. No
that ZBM gets around the problem itself. If you crate a dataset for
/boot itself, to make snapshots of boot related files, then ZBM does not
work, even before the snapshots are made. It simply cannot find the boot
related files, that way. (At all.) So to do a snapshot of boot related
files, after that restructure, you end up having to snapshot the whole
root pool,

No, we need to find a way to get Grub2 and ZFS to play together nicely,
and be stable.

-- 
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

Reply via email to