From owner-freebsd-questions@FreeBSD.ORG Tue Jan 25 18:13:41 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48A35106566C for ; Tue, 25 Jan 2011 18:13:41 +0000 (UTC) (envelope-from clarkjp@charter.net) Received: from mail.cluebytwelve.org (clueby12.org [198.186.190.239]) by mx1.freebsd.org (Postfix) with ESMTP id 229B38FC13 for ; Tue, 25 Jan 2011 18:13:40 +0000 (UTC) Received: from localdomain.local (24-158-157-74.dhcp.jcsn.tn.charter.com [24.158.157.74]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cluebytwelve.org (Postfix) with ESMTPSA id 62B8F1B5D9 for ; Tue, 25 Jan 2011 12:13:40 -0600 (CST) Received: by localdomain.local (Postfix, from userid 1001) id 6F43F2844E; Tue, 25 Jan 2011 12:13:39 -0600 (CST) Date: Tue, 25 Jan 2011 12:13:39 -0600 From: "J. Porter Clark" To: freebsd-questions@freebsd.org Message-ID: <20110125181339.GA21203@auricle.charter.net> References: <20110125014223.GA13385@auricle.charter.net> <4D3E8DC0.9060605@gmx.com> <20110125140705.GA20041@auricle.charter.net> <4D3EDE51.6070404@lazlarlyricon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D3EDE51.6070404@lazlarlyricon.com> Organization: http://www.angelfire.com/ego/porterclark/ User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: How to label a GELI device X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2011 18:13:41 -0000 On Tue, Jan 25, 2011 at 03:29:37PM +0100, Rolf Nielsen wrote: > > Correct me if I'm wrong anyone. > You need to first label da0s1d > > e.g. like so > > glabel label data da0s1d > > then geli init the labeled device > > e.g. like so > > geli init -l 256 -s 4096 label/data Unfortunately, this step overwrites the label. If I try to repeat the glabel command, then the geli metadata is overwritten. > That will give you a device node called /dev/label/data.eli, that you > can newfs and mount. Unfortunately, since you already encrypted da0s1d, > you may have to back it up, and restore the data after you've redone it. > I had this problem a few years ago, and I had to back up and restore, > but perhaps it's been made simpler now? Though I doubt it. I think that this is the problem. -- J. Porter Clark