You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does open the disk correctly and after that booting finishes correctly.
I added some good_msg lines for debugging and found that, for every root device a new -d option would be added to cryptsetup_opts, resulting in a cryptsetup Luksopen command like:
And that fails, since cryptsetup only supports one -d option.
The patch below changes _open_luks() in defaults/initrd.d/00-crypt.sh, by clearing cryptsetup_opts for each device which fixes this issue. genkernel-next.txt
The text was updated successfully, but these errors were encountered:
alinefr
pushed a commit
to alinefr/genkernel-next
that referenced
this issue
Feb 28, 2017
When used with multiple encrypted root disks booting results in error message:
Dropping to shell and entering:
cryptsetup luksOpen -d /mnt/key/key /dev/Volume00/lv_root_2 lv_root_2
Does open the disk correctly and after that booting finishes correctly.
I added some good_msg lines for debugging and found that, for every root device a new -d option would be added to cryptsetup_opts, resulting in a cryptsetup Luksopen command like:
cryptsetup luksOpen -d /mnt/key/key -d /mnt/key/key /dev/Volume00/lv_root_2 lv_root_2
And that fails, since cryptsetup only supports one -d option.
The patch below changes _open_luks() in defaults/initrd.d/00-crypt.sh, by clearing cryptsetup_opts for each device which fixes this issue.
genkernel-next.txt
The text was updated successfully, but these errors were encountered: