Mine is a desktop with NVidia and has occurred since the update to
linux-generic-5.11.-00.34.
But the same machine works fine on Mainline 5.11.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-5.11 in Ubuntu.
This is still affected with Linux kernel 6.2.0-33-genric on this laptop.
Nothing has changed. It still will not do a "reboot" without ending up
at a BIOS Boot menu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in
I have a user that is affected by this bug. I am asking him to post here
with his info. I ask that you reopen this... For him = His is a VM in
Hyper-V.
RE: https://ubuntuforums.org/showthread.php?t=2494675
>From what I can see, there was a Kernel Bug that was patched for this
error upstream:
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.
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
@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
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]
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
Link to this bug, just for package 'nvidia-driver-390':
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/2051436, which is a duplicate of :
https://bugs.launchpad.net/ubuntu/jammy/+source/nvidia-graphics-
drivers-390/+bug/2028165
For nvidia-driver-390, there is another
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
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
@xnox --
Thank you!!!
This is what I see in Noble right now:
>>>
mafoelffen@noble-d05:~$ apt list -a zfsutils-linux
Listing... Done
zfsutils-linux/noble-proposed 2.2.2-0ubuntu1 amd64
zfsutils-linux/noble,now 2.2.1-0ubuntu1 amd64 [installed]
>>>
So it 2.2.1 got pushed to Noble main, with 2.2.2 to
@jimmymmick -- From LTS to a dev interim version? Maybe if other things
supported newer hardware, but I am on 13th Gen iCore and still doing
fine on 22.04.3. The HWE stack is the Lunar kernels (6.2.0-x). But Lunar
loses support soon any ways...
In fact if you update to Mantic (23.10) right now,
Is same with kernel 6.2.0-37-generic.
But, is resolved if I use boot parameter "reboot=acpi" in
/etc/default/grub
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2032136
I believe, as pointed out in https://bugs.launchpad.net/bugs/2032174 ,
it has to do with kernel 6.5, source package 'linux'. & source package
'linux-oem-6.5' ... This seems similar, yet a different problem.
It was there for the 6.2.0 series of kernels, but disappeared last week
when the HWE stack
** Attachment added: "zfs-make.log"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723611/+files/zfs-make.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Attachment added: "zfs-dkms-2.1.5_5.15.0-89-generic_make.log"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723604/+files/zfs-dkms-2.1.5_5.15.0-89-generic_make.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
There weer no other make logs for any other kernels present(???)
>>>
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ ls /var/lib/dkms/zfs/2.1.5/
5.15.0-89-generic source
>>>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
Public bug reported:
On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build
kernel module.
Genrated Crash report, but couldn't send it on it's own.
Error it kept throwing was:
>>>
Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ...
Loading new zfs-2.1.5 DKMS files...
Building for
** Attachment added: "zfs-dkms.0.crash"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723603/+files/zfs-dkms.0.crash
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I remember this error on zfs-dkms when the kernel ranges went from 5.19
to 6.2.0-X... With package zfs-dkms 2.1.5-1ubuntu6~22.04.1.
RE: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2030100
That was fixed a few updates after that, but now we are back to this:
>>>
*** ZFS Version:
No. Lunar upgraded fine to that package version with the same kernel.
But:
on this 22.04.3 machine now:
>>>
mafoelffen@Mikes-B460M:/data/ISO$ apt list zfs-dkms
Listing... Done
zfs-dkms/jammy-updates,jammy-updates,jammy-security,jammy-security,now
2.1.5-1ubuntu6~22.04.2 all [installed]
N: There
Attempt at remove and reinstall of package zfs-dkms failed (see
attached)
No, Crashed again on zks-dkms. Can't et past it. And only affects Jammy.
** Attachment added: "reinstall-output.txt"
Posted a warning out on the Forum:
https://ubuntuforums.org/showthread.php?t=2492886=14166863#post14166863
--
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/2044630
Title:
zfs-dkms
This is not a problem for Noble, as it uses
>>>
fs-dkms/noble,noble 2.2.0-0ubuntu3 all
>>>
Not a problem for Mantic, as it uses:
>>>
zfs-dkms/mantic,mantic 2.2.0~rc3-0ubuntu4 all
>>>
BUT-- In today's updates for Lunar:
>>>
libzfs4linux/lunar-updates,lunar-security 2.1.9-2ubuntu1.2 amd64
** Information type changed from Private Security to Public Security
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-49298
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
From what I got after that... It errors in dpkg, so it leaves the old
modules built for the kernels that it did upgrade to successfully
(there).
Mine error'ed out when it tried to upgrade from 6.2.0-36 to 6.2.0-37. If
worried me also, BUT... It did reboot.
Since linux-image-6.2.0-37-generic
@toekneefan -- Our tests of 2.2.1 from Noble Proposed showed that it was
actually "enabled" by default, instead of being disabled like they said
they did in it's release notes... So the rpool installs as "active", and
any other pools created with feature=default (or just omitted) are
created as
@seth-arnold -- Thank you for those links. Those explain a lot of what
is currently happening, and the changes coming down.
This was comforting from robn:
"If you can't get an updated ZFS (2.2.2, 2.1.14, or a patch from your vendor)
then 'dmu_offset_next_sync=0' is the next best thing."
Anyone
To install 2.2.1, i had to enable proposed in sources, then explicitly install:
>>>
sudo apt install -y zfsutils-linux=2.2.1-0ubuntu1
libnvpair3linux=2.2.1-0ubuntu1 libuutil3linux=2.2.1-0ubuntu1
libzfs4linux=2.2.1-0ubuntu1 libzpool5linux=2.2.1-0ubuntu1
zfs-dkms=2.2.1-0ubuntu1
>>>
To get all the
zfs-linux 2.2.2 released tonight...
In the changelog:
dnode_is_dirty: check dnode and its data for dirtiness #15571 #15526
Which is the above patch for CVE 2023-49298
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
That blew out the ability to boot. Ended up having to remove zfs-dkms.
Reinstalling kernel and boot.
Back up.
zfs-dkms is broken big time for 22.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
It blew 1fallen's machine out of the water.
Before doing anything, backup your bpool and rpool via rsync so you have
a fall back point.
Start a thread on UbuntuForums > Installations and Updates. I will talk
you through a work-around to uninstall zfs-dkms and everything else I
did to get around
I wondered why my old bug report has not gotten any attention. Being a
duplicate of this bug didn't help, but at least someone from the
security team marked it as a duplicate of this bug.
BUT... On Bug Reports filed against zfs-linux, there are 55 bugs, with
not one single person assigned, that
I've tested it and handed it off to Rick for him to look it over and
test (second set of eyes)...
--
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/2044630
Title:
zfs-dkms
** Description changed:
On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build
kernel module.
Genrated Crash report, but couldn't send it on it's own.
Error it kept throwing was:
>>>
Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ...
Loading new zfs-2.1.5 DKMS
<>
Rick S and I have talked a lot today... trying to remember:
I added a repo on my GitHub on: Open-ZFS-Admin > "How To Uninstall
package 'zfs-dkms' And Survive"
We had to remember:
- Why we actually started using it.
Ubuntu, in the past, did not rebuild the zfs module, so we needed zfs-
dkms
This is my merge fo a Bug Report marked as a duplicate of this one:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969
In the OpenZFS patch thread, they had said that feature@block_cloning,
because of the underlying bug, OpenZFS had said they turned that feature
off by default in
Wait... I seem to be confused by this:
>>>
mafoelffen@noble-d05:~$ apt-cache show zfsutils-linux | grep 'Package:\|Breaks:'
Package: zfsutils-linux
Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>>
2.2.2-0ubuntu1...), zfs-dkms (<< 2.2.2-0ubuntu1)
>>>
Does that mean, even
Rick and I have been testing the Proposed 2.2.2 packages in Noble since
yesterday morning. Great so far.
@fl140 --
Thanks you for the link. I'll pass that on.
Waiting to see if anything of this helps with: zfs-dkms
2.1.5-1ubuntu6~22.04.2 https://bugs.launchpad.net/ubuntu/+source/zfs-
Just passed on to me from FL140:
https://github.com/openzfs/zfs/issues/15586#issuecomment-1836806381
Is an updated script to manually build and install the OpenZFS native
deb packages, including 'zfs-dkms' 2.2.2.
** Bug watch added: github.com/openzfs/zfs/issues #15586
Seems to also affect Mantic, if it was installed as jammy, the upgraded
to Mantic. But doesn't seem to affect Mantic system if they were
installed fresh as Mantic. All Tests, so far, show it does not affect
Noble at all (either upgraded from Mantic or installed fresh).
--
You received this bug
I got tired of waiting for anyone to triage this... I removed package
zfs-dkms so I could applied my updates...
They upgraded successfully. Including building the modules for kernel
6.2.0-37-generic.
Then installed package zfs-dkms, where it failed again on building the
module for 6.2.0-37.
--
It is not just preventing upgrades, it is preventing the upgrade to Linux
kernel 6.2.0-37-generic
>>>
mafoelffen@Mikes-ThinkPad-T520:~$ modinfo zfs | grep -e '^filename\|^version'
filename: /lib/modules/6.2.0-36-generic/kernel/zfs/zfs.ko
version:2.1.9-2ubuntu1.1
Here is the link:
https://github.com/Mafoelffen1/OpenZFS-Ubuntu-Admin/blob/main/ZFS-DKMS-WORK-AROUND.md
It is tested. It is somewhat daunting... But it works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Ubfan1 and I have talking about this out on the Forum: Were we have to help
other Users with this.
RE: https://ubuntuforums.org/showthread.php?t=2494834
I think his idea on something is genius: That if the compiler version is
brought in by the kernel on kernel updates as a dependency, so that
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051457
Title:
Jammy 22.04.3 gcc compiler no longer builds
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
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
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
** Also affects: dkms (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2051457
Title:
Jammy 22.04.3 gcc compiler no longer builds
@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
52 matches
Mail list logo
