Hi Turbo, Thank you so much for looking into this. Apologies for no replying sooner, apparently I do not get e-mail from the debian bug tracker (no, it's not in my spambox either). Perhaps best to Cc me explicitly if you need a quick reaction.
On 2025‒12‒04 16:31:54+0000, Turbo Fredriksson wrote:
After spending almost a day setting up Trixie to have a ZFS root and then almost two days trying to reproduce the problem, I have failed to do so!
Not to be outdone in terms of expended effort, I've put up a more-or-less self-contained installation script at https://www.fruit.je/y/zfs-initramfs-1110397/install which should have everything you need to reproduce the issue. I've also captured the output (see the links below) so that hopefully you don't have to. ;) But even if you don't actually run it, you can at least see the exact steps that lead to the issue.
Wessel, I need you to add the `zfsdebug=yes` on the kernel command line and try to see where this is happening. Is it indeed in the initrd or once the zfs mount happens??
You can see the output of it at: https://www.fruit.je/y/zfs-initramfs-1110397/reboot-log
If you could give me the output from the following commands, I’d also appreciate it. I have no idea what I’m looking at, but at least then I can start to compare it with what I have.. * zpool get bootfs <pool> * zfs list -o name,canmount,encryption,mounted,mountpoint
You'll find this output at the bottom of https://www.fruit.je/y/zfs-initramfs-1110397/install-log Please note that the bootfs property is not used by grub.
The important thing I need to know, is it *really* the initrd that is at fault here??! I’m not so sure it is..
I'm pretty sure it is! This patch: https://www.fruit.je/y/zfs-initramfs-1110397/patch resolves the issue completely (it's basically a more explicit rendering of what I wrote in the original report). Kind regards, -- Wessel Dankers <[email protected]>
signature.asc
Description: PGP signature
