Date: Sun, 27 Mar 2016 14:37:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 206521] Can't decrypt disks on ZFS+Geli installation after order of devices changed Message-ID: <bug-206521-3630-bboZsXDf3Y@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206521-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-206521-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206521 Fabian Keil <fk@fabiankeil.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |allanjude@FreeBSD.org, | |fk@fabiankeil.de --- Comment #2 from Fabian Keil <fk@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=3D"YES" geli_gpt_rpool-ada0_keyfile0_type=3D"gpt/rpool-ada0:geli_keyfile0" geli_gpt_rpool-ada0_keyfile0_name=3D"/boot/rpool.key" [...] geli_gpt_rpool-ada3_keyfile0_load=3D"YES" geli_gpt_rpool-ada3_keyfile0_type=3D"gpt/rpool-ada3:geli_keyfile0" geli_gpt_rpool-ada3_keyfile0_name=3D"/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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206521-3630-bboZsXDf3Y>