I've had two systems taken down by what seems to be this bug now in the
last few weeks. This, together with the mismatched kernel and userspace
version of the ZFS tooling is really, really bad.
I do get that a ZFS root and the HWE kernel together is a rather
esoteric setup but it's all out-of-the-
In the next few days, when I get some "spare" time... I will spin up a
few test Jammy VM's to capture what depends it has to pull in from other
repo's, so that the depends can be ID'ed and maybe those packages can be
added to that Jammy package in this new PPA.
Otherwise, as I just found out with
Works great. Tested, and a lot simpler, because there are builds for
Jammy, Mantic and Noble.
The command log for the updated work-around using the "Backports build PPA"
>>>
sudo su -
zpool export -a
zpool import -N -R /mnt rpool
zpool import -N -R /mnt bpool
UUID=$(zfs list | awk '/^bpool\/BOOT\/
If you're using zfs-auto-snapshot, you can tell it to ignore bpool by
setting the com.sun:auto-snapshot property to false on the bpool
dataset:
# zfs set com.sun:auto-snapshot=false bpool
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zf
Oh but please don't use `[trusted=yes]`, just add the repository with
add-apt-repository ppa:ubuntu-uefi-team/backports-build.
--
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
Ti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
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/2
Update: Instead of my name space, I have uploaded a 2.12 version to this
PPA: https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/backports-
build
If it builds correctly, it can be used on Jammy with less fear by adding:
"deb [trusted=yes]
https://ppa.launchpadcontent.net/ubuntu-uefi-team/bac
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 wi
Mike and I have posted Disclaimers to the users on Jammy **Warning of
potential breakage with the added PPA
Mike has also included some very straight forward work-around's with The
*Warning* to users on 22.04 until the fix is pushed to the users.
--
You received this bug notification because you
@mkukri ---
>>>
The question is, are we going to backport the fix to 2.06 and push that to the
updates channel, or can this wait for the 2.12 SRU sometimes after April?
>>>
What does that mean?
Option #1 -- The cherry picked Grub2 2.12 ZFS related commit code gets
applied to Grub2 2.06 as a patc
GRUB 2.12 isn't going into the updates channel anywhere at this point.
(It's going in proposed then release on Noble soon however)
The question is, are we going to backport the fix to 2.06 and push that
to the updates channel, or can this wait for the 2.12 SRU sometimes
after April?
It's good to
So yes. Grub2 2.12 with those patches fixes this issue for Jammy, Mantic
and Noble. We need to apply the fix to all these releases.
--
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/205199
The command log for the work-around for a broken jammy install:
>>>
sudo su -
zpool export -a
zpool import -N -R /mnt rpool
zpool import -N -R /mnt bpool
UUID=$(zfs list | awk '/^bpool\/BOOT\/ubuntu_/ {print $1}' | sed
's/bpool\/BOOT\/ubuntu_//g')
zfs import rpool/ROOT/ubuntu_$UUID
zfs import bpoo
@rlaager ---
When I said reconfigure, i did:
>>>
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi \
--bootloader-id=ubuntu --recheck --no-floppy
>>>
So yes, was that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-
Wahoo! Found the magic combination.
chrooted into the broken jammy system.
Add a Noble sources list.
Add the ppa. Edit the added
/etc/apt/sources.list.d/ubuntu-uefi-team-ubuntu-build-jammy.list's active line
to:
>>>
deb [trusted=yes]
https://ppa.launchpadcontent.net/ubuntu-uefi-team/build/ub
Any chance this test needs a re-run of “grub-install”, not just “update-
grub” (as you would get from a reconfigure)?
--
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:
Gr
Since it is also built for Mantic, I would expect it works for Mantic
Also. (Will confirm later.)
I spun up a Jammy ZFS image. Changed the sources list to Noble. Added
the PPA. Installed packages 'grub2 & shim'... Let it pull in the depends
it needed. Change the sources.list back to jammy. Did som
It worked:
The grub issue with a PPA solved it for NNoble
Code:
apt policy grub-common
grub-common:
Installed: 2.12-1ubuntu1~ppa1
Candidate: 2.12-1ubuntu1~ppa1
Version table:
*** 2.12-1ubuntu1~ppa1 500
500 https://ppa.launchpadcontent.net/ubuntu-uefi-team/build/ubuntu
noble/main a
I've added the PPA for Noble just now, will report after a manual bpool
snapshot
**The following packages will be upgraded:
automake autopoint ayatana-indicator-common bind9-dnsutils bind9-host
bind9-libs cpio
gcc-14-base gcc-14-base:i386 gettext gettext-base grub-common
grub-efi-amd64-
@mafoelffen You can find builds of GRUB 2.12 for Ubuntu in this PPA:
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/build
NOTE that the stuff in that PPA isn't signed, so you need to disable
UEFI secure boot to test it easily.
--
You received this bug notification because you are a memb
Forgot to mention... Those "@feature" changes, that are suspected as
being the problems when enabled... unfortunately cannot be done on an
already created bpool. Those can only be set at pool "creation time".
So I'm working on a script to recreate bpool which those specific option
settings from th
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 ano
Also affect Mantic...
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
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 up
23 matches
Mail list logo
