Hello. To advance this problem, I decided to redo a brand new installation without using encryption.
I can also boot several times without any difficulty. With another O.S. in version 22.04 installed in an EXT4 partition, I launched the script to access this ZFS partition. The problem is reproduced in a simpler way. The boot does not finish despite waiting about an hour. I took a screenshot which I am attaching. I know the problem is systematic. Using the quoted script, I can access the log. But I see that the log has not yet been created. I am only allowed to boot into recovery mode. It's a little better. The boot hangs less I am attaching the errors encountered and the entire trace of the log. All this is obtained by the aforementioned script. I'm willing to admit that my script isn't up to snuff. however this should absolutely not prevent ZFS from booting. I don't know whether to do another bug report or if it can stay in this one. Good research and good editing. ** Attachment added: "photograph of unencrypted ZFS boot hang" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+attachment/5563868/+files/boot.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
