Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Jan 2011 19:28:25 +0100
From:      Rolf Nielsen <>
To:        "J. Porter Clark" <>
Subject:   Re: How to label a GELI device
Message-ID:  <>
In-Reply-To: <>
References:  <>	<>	<>	<> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
2011-01-25 19:13, J. Porter Clark skrev:
> 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.

It does not. I just tested it with a file backed md device, and 
hexdumped it after each step (creating the file, mdconfig it, label the 
md device and encrypting it).
After the first two steps, I got just zeros, after labeling it, I got 
the last sector containing the label, and after encrypting it, I got the 
second last sector (i.e. the last sector of the labeled device) 
containing the eli data and the last secor still containing the label.

If it does overwrite the label, you most likely specified the da0s1d to 
the geli init command. You need to specify label/data (replace "data" 
with the name you choose).

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.

Want to link to this message? Use this URL: <>