Where is zfs.ko




















In this situation, modules loaded and system started to work. I think thats another bug. Results doesnt change when using virtual machine or real hardware. I also tried the same things on buster, but it didnt work at all, no matter using dracut or initramfs-tools as initramfs system or which kernel you installed. When using a normal linux flesystem such as ext4, boot process finishes with no problem. I saw this , but it didnt help me.

I did some tests and realized that by installing cryptsetup-initramfs package, system recognizes modules signatures and inserts the zfs module and starts to boot. I was using initramfs-tools as my initramfs system, the default initramfs system of debian. It seems that cryptsetup-initramfs package adds some hooks to the initramfs, so system can recognize modules signatures before even mounting the root filesystem.

I think this is a workaround for this problem, changing the dependencies of zfs-initramfs package, so cryptsetup-initramfs package also installs when installing zfs-initramfs package. I have zfs encrypted rpool on Debian sid dual boot witn Win10 and regularly do apt full-upgrade. I'm a step away from enabling SecureBoot, but upon seeing this issues report, haven't enabled it yet. Have been keeping an eye on this issue. As you've highlighted, I'm also missing the link between zfs modules and cryptsetup-initramfs.

Sign in to your account. With every upgrade of zfs through the official repo on Fedora all zfs devices disappear. Here is the specific series of events that lead to this issue:. The text was updated successfully, but these errors were encountered:. Same thing happened to me. My dkms configuration was corrupted during the zfs update, which in turn broke my nvidia drivers, which then took out my plasma desktop.

Took hours to recover. Thanks for your help above, I was able to manually work through the issues and get up and running again. Sorry, something went wrong. This way however presents new problems as well. When you have more than one kernel installed the issue is that there is a format exec error on zfs which is cause by a mismatch of the zfs module and zfs dependency module version built for each kernel. As show above the vermagic is different from the kernel version, similar for other kernels as well except the actual kernel the zfs module was built against.

I've seen this happen for every new zfs version on Fedora. The quick fix for me has been:. This messes up dkms and it is unable to do anything.

I'm guessing the fix is to delete that old symlink as part of a post install script but I'm not that familiar with rpm packaging. Some evidence towards this idea:. Although the rpm package scripts call dkms to build and deploy zfs kernel modules at installation time, they don't or incorrectly call dkms at rpm removal time. This issue is slightly complicated with the overlap of a different issue: a new zfs kernel module version could possibly be incompatible with an older installed kernel version.

In such a case the removal of older kernel modules would result in older kernel versions no longer work with zfs. I am not sure if that ever happened or can reasonably expected to happen, but a computer system would require both the zfs-version-x and zfs-version-y installed at the same time. For the sake of expedient resolution of this very real upgrade problem I would recommend setting this possible complication aside.

I was recently added as maintainer of dkms in Fedora, and just pushed an update for f31 other versions are still in the pipeline - I don't think that update will do anything to help this, though. I was just ponted here; I'll read up on this and hopefully comment more later.

I too have seen this. As others have pointed out "dkms status" will show incomplete output if there is a problem. I think it would be best to leave the old version of the compiled module around as a fall-back.

I ran into this again during the 0. In case anyone else wants to try this, first clone the repo and apply the patch on top of 0. It sounds like a good idea. It looks like there may be a problem getting it to automatically include the updated kernel module in the initramfs on upgrade though because, at least on my fedora 31 system, akmodsposttrans. Hmm, that's a good point. I hadn't personally run into that because I don't boot from zfs. My initramfs with dkms didn't have the zfs modules either.

The if statement should be true, but ends up being false. When I run the command manually before upgrading , I get the following:. After a slight modification to show all matches, it becomes clear that a bad match is to blame:.

I should have a fix shortly. Unfortunately, this fix changes the uninstall script, so it will not be available until you upgrade from the next release of the RPM.

Distributions can make this happen sooner by incrementing the Release field and releasing an update to the RPM spec only. The problem still occurs. I ran "dnf update" on a Fedora system with kernel That appeared to work: I didn't check, but I was able to reboot the system. I was getting complaisant. Star 7. New issue. Jump to bottom. GPL-incompatible module zfs. Labels Type: Building. Type: Building. Linked pull requests.

Copy link. It isn't a bug if it isn't supposed to work imho. Fixes the issue reported in openzfs comment. Sign up for free to join this conversation on GitHub.



0コメント

  • 1000 / 1000