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

wrong order of luks and start_volumes in linuxrc #25

Open
dmatetelki opened this issue Feb 19, 2015 · 0 comments
Open

wrong order of luks and start_volumes in linuxrc #25

dmatetelki opened this issue Feb 19, 2015 · 0 comments

Comments

@dmatetelki
Copy link

initramfs opens LUKS encrypted dev without a problem,
but then fails with ZFS:

ZFS pool system already imported.
LUKS detected. Reimporting system
cannot import 'system': no such pool available
Working on device /dev/sdb1...
Using key device /dev/sda2.
Removable device /dev/sda2 mounted.
luks-key.gpg on device /dev/sda2 found
Enter passphrase:
LUKS device /dev/sdb1 opened
Initializing root device...
cannot open 'system/root': dataset does not exist

Logging into shell & mounting zpool & exit leads to a normal boot.

I've copied the error texts from here:
https://forums.gentoo.org/viewtopic-p-7705230.html?sid=78ce44381b0a9e9e55094538773260c5
I got the same with different dev and pool names.

Changing the scrip order in default/linuxrc from:
start_volumes
zfs_start_volumes
setup_keymap
is_livecd || start_luks

to
setup_keymap
is_livecd || start_luks
start_volumes
zfs_start_volumes

solved this issue.
Is there a reasion not to have luks before start_volumes?

alinefr added a commit to alinefr/genkernel-next that referenced this issue Feb 28, 2016
alinefr added a commit to alinefr/genkernel-next that referenced this issue Mar 5, 2016
alinefr added a commit to alinefr/genkernel-next that referenced this issue Mar 6, 2016
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

1 participant