Skip to content
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

Importing multiple encrypted pools at boot #237

Open
zejar opened this issue Jun 19, 2021 · 3 comments
Open

Importing multiple encrypted pools at boot #237

zejar opened this issue Jun 19, 2021 · 3 comments

Comments

@zejar
Copy link

zejar commented Jun 19, 2021

Running a system with root on an encrypted ZFS pool as guided by https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/Debian%20Buster%20Root%20on%20ZFS.html.
The root pool gets imported correctly during boot and is able to be decrypted with the zfsunlock script. An additional encrypted pool does get mounted, but only gets mounted and unlocked (by requesting the key on the console) after the zfsunlock utility terminates and the dropbear initramfs session terminates.
When manually importing the extra zpool beforehand the key gets requested by zfsunlock, so I'm guessing it has to do with the issue listed in #236. Since that issue hasn't been resolved yet, would there be another way to import zpools at boot before the Dropbear session starts in initramfs?

ZFS version: zfs-2.0.3-1~bpo10+1.
Both pools are encrypted with a passphrase which has to be manually be put in via the Dropbear session.

@lifo9
Copy link

lifo9 commented Aug 31, 2023

Bump, this is still an issue :(

@darrenfreeman
Copy link

Bump, still an issue.

@darrenfreeman
Copy link

The workaround is to manually enter:

zpool import other-pool
zfs load-key other-pool
zfsunlock

Simply using zpool import -l other-pool will result in many of the datasets being automatically mounted too early, and then hidden by the true root filesystem. They can't be mounted, because they are already mounted, yet they are not visible. And they can't be unmounted, either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants