#ZFS doesn't seem to work on securecore-zfs-main-userns-hardened

1 messages Ā· Page 1 of 1 (latest)

glad spindle
#

Describe the bug
Attempting to create a zpool with:
zpool create -o ashift=12 -O compression=zstd POOLNAME raidz /dev/DEVICE1 /dev/DEVICE2 /dev/DEVICE3

doesn't seem to work and results in an error:

The ZFS modules cannot be auto-loaded.
Try running 'modprobe zfs' as root to manually load them.

Running modprobe zfs gives the error:
modprobe: FATAL: Module zfs not found in directory /lib/modules/6.11.8-300.fc41.x86_64

To Reproduce
Steps to reproduce the behavior:

  1. try to create a zfs pool
  2. run modprobe zfs

Expected behavior
I am able to create a zfs pool

Actual behavior
Attempting to create a zfs pool fails

Your current image
rpm-ostree status

State: idle

AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot

Deployments:
ā— ostree-image-signed:docker://ghcr.io/secureblue/securecore-zfs-main-userns-hardened:latest
Digest: sha256:00f90098629bb1a02b275e24d4107d01b7d77211ceddde43e1efb8e2b00bb28c
Version: 41.20241122.2.0 (2024-11-30T09:28:49Z)
Initramfs: regenerate

ostree-image-signed:docker://ghcr.io/secureblue/securecore-zfs-main-userns-hardened:latest
Digest: sha256:00f90098629bb1a02b275e24d4107d01b7d77211ceddde43e1efb8e2b00bb28c
Version: 41.20241122.2.0 (2024-11-30T09:28:49Z)

I feel like there is something easy that I'm missing so I am just asking here before I escalate further. Any ideas? Your help is appreciated, thanks.

glad spindle
#

Ok, so when I look at the openzfs github releases, it says that the current openzfs version zfs-2.2.6 supports 4.18 - 6.10 kernels and the zfs-2.3.0 prerelease supports 4.18 - 6.11 kernels. When I use uname -r it reports my kernel version is 6.11.8-300.fc41.x86_64 and when I use zfs --version it reports that the version is zfs-2.2.6-1.

Is there a mismatch between the kernels that openzfs supports and the kernel that secureblue ships? If that is the case, wouldn't it be assumed that the zfs images of secureblue would break frequently through continued kernel updates?

timid umbra
# 
/tmp/rpms/kmods/zfs/kmod-zfs-6.11.8-300.fc41.x86_64-2.2.6-1.fc41.x86_64.rpm
#

seems fine.

#

fixing it now

#

thanks for catching this

glad spindle
#

@timid umbra Yeah, no problem. Thanks for fixing it so fast!

glad spindle
#

So apologies for my naivety and unfamiliarity of software development, but is this something that will be fixed within a couple of days after the pull request is merged and I just need to rpm-ostree update, or will I need to wait a much longer amount of time for the next version of secureblue to release to contain these fixes? If that is the case, would it be best to rebase to the ucore versions that contain zfs and then later rebase back again to secureblue when the fixes are merged? I'm only asking because I have my family waiting on me to fix our home server haha. Thanks once again!

timid umbra
#

i need two approvers šŸ™‚

#

technically i could go disable all our security checks and minder autoremediation

#

but these checks are there for a reason

#

I shouldn't have carte blanche access to stuff even though I'm the project owner šŸ™‚

glad spindle
#

Awesome, thanks for the quick response.

timid umbra
#

let me know if it's not fixed after rpm-ostree upgrade

glad spindle
#

I took 2 seconds to make a dumb meme to celebrate. Seems to be working now, thanks!

dumbmeme.png