[Bug 206521] Can't decrypt disks on ZFS+Geli installation after order of devices changed

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Mar 27 14:37:15 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206521

Fabian Keil <fk at fabiankeil.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |allanjude at FreeBSD.org,
                   |                            |fk at fabiankeil.de

--- Comment #2 from Fabian Keil <fk at fabiankeil.de> ---
If I don't misinterpret the code, bsdinstall puts the plain
disk name into loader.conf when specifying the keyfile.

Updating the keyfile entry/entries should solve the problem.

To prevent the issue in the first place, bsdinstall could
use GPT labels.

The ElectroBSD installer cloudiatr does this and reordering
disks doesn't seem to cause any problems.

Example:
geli_gpt_rpool-ada0_keyfile0_load="YES"
geli_gpt_rpool-ada0_keyfile0_type="gpt/rpool-ada0:geli_keyfile0"
geli_gpt_rpool-ada0_keyfile0_name="/boot/rpool.key"
[...]
geli_gpt_rpool-ada3_keyfile0_load="YES"
geli_gpt_rpool-ada3_keyfile0_type="gpt/rpool-ada3:geli_keyfile0"
geli_gpt_rpool-ada3_keyfile0_name="/boot/rpool.key"

Putting the original disk name into the label is a bit
confusing when the disk name changes, though, so I'm considering
using generic names like disk1, disk2 etc. in the future.

CC'in Alan who worked on the relevant bsdinstall code in the past.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-fs mailing list