-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZFS 2.1.5_1 breaks boot on non zfs-on-root systems #37667
Comments
Digging around, the issue seems to be in zfs-lib.sh overwriting I hacked up the following patch which fixes the issue for me:
|
If you don't have root-on-ZFS, there's no need for
What kernel commandline do you boot your system with? |
The real question is why this never bit you before. This doesn't really seem to be a bug; I suspect you aren't specifying any Also, as zdykstra mentioned, you shouldn't put the ZFS dracut module in your initramfs if you aren't booting a ZFS root. |
No, i have
Well, both systems are a pretty vanilla void installation - just with the ZFS package installed (because my /home is on ZFS). I don't think it is expected that i'd have to blocklist ZFS in dracut in such a configuration.
The problem here is that dracut already changed this value before: So my system sets
Once this has run, Now later (after parse-block.sh but before the rootfs mount)
which will reset (Also see here for the rd.debug output on how |
Thanks for the clarification. This is most definitely a bug and should be fixed upstream (see openzfs/zfs#13589 for my proposal). Once we have some feedback from upstream, we can pull a patch back here. In the meantime, disabling the ZFS dracut module will get you what you need. Also, cc: @Vaelatern |
It wasn't there on an earlier release. |
My approach ^ |
Should be fixed by d6d1cc4, sorry we didn't catch this before the update. |
Thanks! I can confirm that the updated package fixes the issue |
I got hit by that bug, and now my system doesn't boot anymore because of that, and drops to dracut shell. |
@aaFn You should be able to run |
Hello @RunningDroid , that worked, thank you (I was not aware that exiting the shell was continuing the process after that .. I learnt something today). |
Is this a new report?
Yes
System Info
Void 5.18.4_1 x86_64 GenuineIntel uptodate rFFF
Package(s) Affected
zfs-2.1.5_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
The system boots
Actual behaviour
After upgrading 2 systems from ZFS 2.1.4 to 2.1.5, both systems fail to boot as dracut complains about not being able to mount the rootfs.
Note that ZFS is not used as rootfs: one system uses ext4, the other btrfs.
Steps to reproduce
The text was updated successfully, but these errors were encountered: