From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhogomchungu@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 9aV8H0D1Ipqi for <dm-crypt@saout.de>;
 Thu, 18 Jul 2013 07:56:07 +0200 (CEST)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com
 [IPv6:2607:f8b0:400e:c01::22f])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 18 Jul 2013 07:56:07 +0200 (CEST)
Received: by mail-pb0-f47.google.com with SMTP id rr13so2749664pbb.6
 for <dm-crypt@saout.de>; Wed, 17 Jul 2013 22:56:05 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <9A629FEC462BD94990DA2D70E6C94E8B193B3283@SUEX10-mbx-01.ad.syr.edu>
References: <9A629FEC462BD94990DA2D70E6C94E8B193B3283@SUEX10-mbx-01.ad.syr.edu>
From: ".. ink .." <mhogomchungu@gmail.com>
Date: Thu, 18 Jul 2013 01:55:45 -0400
Message-ID: <CAFnMBaR0Dj0qdyz8fEN6GGRBpxAi3vdpqt+JKwyBzHyuvq=VRA@mail.gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc7738ab95c604e1c2dda2
Subject: Re: [dm-crypt] Trying to mount pre-Luks encrypted external disks,
 suse 12.3
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: James Pacey Bennett <jbennett@maxwell.syr.edu>
Cc: "dm-crypt@saout.de" <dm-crypt@saout.de>

--047d7bdc7738ab95c604e1c2dda2
Content-Type: text/plain; charset=ISO-8859-1

> So I try a 'legacy' approach per the cryptosetup wiki:
>
> linux-p22i /root# cryptsetup create back5 /dev/sdi1
> Enter passphrase:
> (which I did; just got newline)
>
> linux-p22i /root# cryptsetup status back5
> /dev/mapper/back5 is active.
>   type:    PLAIN
>   cipher:  aes-cbc-essiv:sha256
>   keysize: 256 bits
>   device:  /dev/sdi1
>   offset:  0 sectors
>   size:    976768002 sectors
>   mode:    read/write
>
> ***which seems correct to me***
>
> linux-p22i /root# l /dev/mapper/
> back5@
> cr_ata-WDC_WD1002FAEX-00Z3A0_WD-WCATRC268610-part1@
> control%                                            main@
>
> Now. How do I or what do I mount?  I can't use /dev/mapper directly.
> I have no success trying to mkfs /dev/back5.
>
> This must be a common problem but I don't find
> it addressed in the opensuse forums.
>
>
The mapper path created is "/dev/mapper/back5".This is the plain text path
you use to access stuff stored in the encrypted volume.

Just to be safe the default options of cryptsetup are the same as the ones
you used when you were using losetup,run the following commands to see if
they will recognize the file system on the volume.

blkid /dev/mapper/back5

what seem correct to you may not be.With slightly different encryption
options,its even possible for blkid among other tools to see valid file
system giving you more hope you have used correct options and you could end
up corrupting your data if you write to them.

I think the safety thing to do is to go back to an old system where the
volumes worked,copy the data off of them and then create a new cryptsetup
volume on the device and then move back your data.

--047d7bdc7738ab95c604e1c2dda2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><div>=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v><div style=3D"direction:ltr;font-size:10pt;font-family:Tahoma">
So I try a &#39;legacy&#39; approach per the cryptosetup wiki:<br>
<br>
linux-p22i /root# cryptsetup create back5 /dev/sdi1<br>
Enter passphrase:<br>
(which I did; just got newline)<br>
<br>
linux-p22i /root# cryptsetup status back5<br>
/dev/mapper/back5 is active.<br>
=A0 type:=A0=A0=A0 PLAIN<br>
=A0 cipher:=A0 aes-cbc-essiv:sha256<br>
=A0 keysize: 256 bits<br>
=A0 device:=A0 /dev/sdi1<br>
=A0 offset:=A0 0 sectors<br>
=A0 size:=A0=A0=A0 976768002 sectors<br>
=A0 mode:=A0=A0=A0 read/write<br>
<br>
***which seems correct to me***<br>
<br>
linux-p22i /root# l /dev/mapper/<br>
back5@=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr_ata-W=
DC_WD1002FAEX-00Z3A0_WD-WCATRC268610-part1@<br>
control%=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 main@<br>
<br>
Now. How do I or what do I mount?=A0 I can&#39;t use /dev/mapper directly.<=
br>
I have no success trying to mkfs /dev/back5.<br>
<br>
This must be a common problem but I don&#39;t find<br>
it addressed in the opensuse forums.<br>
<br></div></div></blockquote><div>=A0<br>The mapper path created is &quot;/=
dev/mapper/back5&quot;.This is the plain text path you use to access stuff =
stored in the encrypted volume.<br><br>Just to be safe the default options =
of cryptsetup are the same as the ones you used when you were using losetup=
,run the following commands to see if they will recognize the file system o=
n the volume.<br>

<br>blkid /dev/mapper/back5<br></div></div><br>what seem correct to you may=
 not be.With slightly different encryption options,its even possible for bl=
kid among other tools to see valid file system giving you more hope you hav=
e used correct options and you could end up corrupting your data if you wri=
te to them.<br>

<br>I think the safety thing to do is to go back to an old system where=20
the volumes worked,copy the data off of them and then create a new=20
cryptsetup volume on the device and then move back your data.<br><br>

--047d7bdc7738ab95c604e1c2dda2--