Pool Cannot Be Imported After Restart #15702
Replies: 10 comments 3 replies
-
You're running Ubuntu's builtin version of ZFS after reboot. I would assume that however you set it up, the kernel module version didn't get updated when you rebooted into a new kernel. Ubuntu ships their ZFS kernel modules in the base kernel package, so you get those without installing anything, only the userland tools are in debs. Not a bug. |
Beta Was this translation helpful? Give feedback.
-
Your zfs-utils version is mismatching the kmod version after a reboot. This is likely because the older zfs module that comes with Ubuntu is in your initrd but the new zfs module is not, so the old kmod is being loaded at boot time. Do a update-initramfs -c -k all and try rebooting again. |
Beta Was this translation helpful? Give feedback.
-
As noted before I never installed the Ubuntu ZFS packages, so how can that be? Unfortunately updating the initramfs did not improve matters. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
OK, so how do I back out of that? And moreover, would the kmod and utility mismatch produce such an error? |
Beta Was this translation helpful? Give feedback.
-
Ubuntu includes a zfs module in the standard linux-modules package. Here’s an Ubuntu 22.04 VM that I use that has no ZFS package installed (don’t use ZFS at all on this VM) but the zfs module is nonetheless there.
OK I re-read your original post and followed your link. I am not familiar with those instructions. They have you do a “make install” and I am not entirely sure what that does to the system. My recommendation would be to follow the “Custom Packages” instructions and build the .deb packages. I always use dkms. https://openzfs.github.io/openzfs-docs/Developer%20Resources/Custom%20Packages.html#dkms-1 In any case, can you do a “find /lib/modules -name zfs*” and see if a zfs module actually got installed into the kernel modules tree? |
Beta Was this translation helpful? Give feedback.
-
I'm moving this to a discussion because it's not a bug. |
Beta Was this translation helpful? Give feedback.
-
@rincebrain thank you; @dmdx86 yes your hunch is correct. I will look at the Custom Package approach as well; @rincebrain had suggested that earlier and I made one attempt at it but ran into issues which more likely the result of user error. |
Beta Was this translation helpful? Give feedback.
-
Here is how I finally got it to work, the last line being key since it is Ubuntu
Thanks to @gmelikov for that tip from an earlier post concerning the 0.8.3 release. Thanks also to @rincebrain and others for holding my hand. Now to do some proper testing. |
Beta Was this translation helpful? Give feedback.
-
System information
Describe the problem you're observing
I have an instance of Ubuntu 20.04.3 LTS Server running on Apple Silicon (as a VM) where I have performed an In-Tree Build and Install of ZFS as per the instructions provided here. None of the native distro ZFS packages were previously installed.
After installation, I successfully created my test pool as a two-way mirror. Its all good until I restart and discover that the ppol has not imported. When I manually attempt to import the pool, I receive the error that the pool is not importable due to an unsupported version or feature, despite the fact that the pool was created on the very same running instance of ZFS.
This seems like a bug to me.
Describe how to reproduce the problem
Every time I try to import the pool unsuccessfully.
Include any warning/errors/backtraces from the system logs
Beta Was this translation helpful? Give feedback.
All reactions