From owner-freebsd-fs@freebsd.org Sun Mar 27 15:15:58 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 BCA10ADF126 for ; Sun, 27 Mar 2016 15:15:58 +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 AD31F138A for ; Sun, 27 Mar 2016 15:15:58 +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 u2RFFwmY041439 for ; Sun, 27 Mar 2016 15:15:58 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 15:15:58 +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: allanjude@FreeBSD.org 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: 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 15:15:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206521 --- Comment #3 from Allan Jude --- (In reply to Fabian Keil from comment #2) The bit of this related to the GELIBoot commit, was meant to quickly be followed by a patch to the installer to create a single encrypted pool, wit= hout using key files (because they are not supported by GELIBoot yet) This change was delayed due to problems encountered, and my personal lack of time to fix them. I hope to have a patch for the installer soon that will n= ot use key files if the configuration allows a GELIBoot style install (GPT, ZF= S, single pool) The reason GPT labels were not used was: A) support for MBR B) GPT labels disappear if the disk_ident label is used first (this caused issues when GPT labels were used for swap in previous versions) --=20 You are receiving this mail because: You are the assignee for the bug.=