From owner-freebsd-fs@freebsd.org Sun Mar 27 14:37:15 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B102ADF6C0 for ; Sun, 27 Mar 2016 14:37:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2BBB310F4 for ; Sun, 27 Mar 2016 14:37:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2REbDOr063075 for ; Sun, 27 Mar 2016 14:37:15 GMT (envelope-from bugzilla-noreply@freebsd.org) 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 Date: Sun, 27 Mar 2016 14:37:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fk@fabiankeil.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2016 14:37:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206521 Fabian Keil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |allanjude@FreeBSD.org, | |fk@fabiankeil.de --- Comment #2 from Fabian Keil --- 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.=