From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 1QX-KeVcc1zg for ; Thu, 18 Jul 2013 02:28:03 +0200 (CEST) Received: from smtp2.syr.edu (smtp2.syr.edu [128.230.18.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Thu, 18 Jul 2013 02:28:02 +0200 (CEST) Received: from suex10-hub-02.ad.syr.edu ([128.230.108.125]) by smtp2.syr.edu (8.14.5/8.14.5) with ESMTP id r6HNfEpj009989 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 17 Jul 2013 19:41:14 -0400 From: James Pacey Bennett Date: Wed, 17 Jul 2013 23:41:13 +0000 Message-ID: <9A629FEC462BD94990DA2D70E6C94E8B193B3283@SUEX10-mbx-01.ad.syr.edu> Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_9A629FEC462BD94990DA2D70E6C94E8B193B3283SUEX10mbx01adsy_" MIME-Version: 1.0 Subject: [dm-crypt] Trying to mount pre-Luks encrypted external disks, suse 12.3 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "dm-crypt@saout.de" --_000_9A629FEC462BD94990DA2D70E6C94E8B193B3283SUEX10mbx01adsy_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have several external backup disks encrypted before Luks appeared. After update from 12.1 to 12.3, losetup is gone and I haven't been able to mount the encrypted disks. linux-p22i /root# uname -r 3.7.10-1.16-desktop linux-p22i /root# lsmod | grep crypt cryptoloop 12715 0 loop 27944 1 cryptoloop dm_crypt 22845 2 dm_mod 92315 4 dm_crypt linux-p22i /root# lsblk -f -l /dev/sdi1 NAME FSTYPE LABEL UUID MOUNTPOINT sdi1 ***/dev/sdi1 was previously under 12.1 mounted using losetup*** ***Because the partition isn't a Luks partition, I can't*** linux-p22i /root# cryptsetup luksOpen /dev/sdi1 back5 Device /dev/sdi1 is not a valid LUKS device. 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-0= 0Z3A0_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. Help! jim bennett --_000_9A629FEC462BD94990DA2D70E6C94E8B193B3283SUEX10mbx01adsy_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I have several external backup disks encrypted before Luks appeared.= After
update from 12.1 to 12.3, losetup is gone and I haven't been able to
mount the encrypted disks.

linux-p22i /root# uname -r
3.7.10-1.16-desktop

linux-p22i /root# lsmod | grep crypt
cryptoloop           = ; 12715 0
loop            = ;       27944 1 cryptoloop
dm_crypt           &= nbsp;   22845 2
dm_mod           &nb= sp;     92315 4 dm_crypt

linux-p22i /root# lsblk -f -l /dev/sdi1
NAME FSTYPE LABEL UUID MOUNTPOINT
sdi1

***/dev/sdi1 was previously under 12.1 mounted using losetup***

***Because the partition isn't a Luks partition, I can't***
linux-p22i /root# cryptsetup luksOpen /dev/sdi1 back5
Device /dev/sdi1 is not a valid LUKS device.

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@           &nb= sp;            =             &nb= sp;         cr_ata-WDC_WD1002FAEX-0= 0Z3A0_WD-WCATRC268610-part1@
control%           &= nbsp;           &nbs= p;            &= nbsp;       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.

Help!
jim bennett

--_000_9A629FEC462BD94990DA2D70E6C94E8B193B3283SUEX10mbx01adsy_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ; 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 ; Thu, 18 Jul 2013 07:56:07 +0200 (CEST) Received: by mail-pb0-f47.google.com with SMTP id rr13so2749664pbb.6 for ; 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 .." Date: Thu, 18 Jul 2013 01:55:45 -0400 Message-ID: Content-Type: multipart/alternative; boundary=047d7bdc7738ab95c604e1c2dda2 Subject: Re: [dm-crypt] Trying to mount pre-Luks encrypted external disks, suse 12.3 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: James Pacey Bennett Cc: "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

=A0

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.
=A0 type:=A0=A0=A0 PLAIN
=A0 cipher:=A0 aes-cbc-essiv:sha256
=A0 keysize: 256 bits
=A0 device:=A0 /dev/sdi1
=A0 offset:=A0 0 sectors
=A0 size:=A0=A0=A0 976768002 sectors
=A0 mode:=A0=A0=A0 read/write

***which seems correct to me***

linux-p22i /root# l /dev/mapper/
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@
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@

Now. How do I or what do I mount?=A0 I can't use /dev/mapper directly.<= br> 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.

=A0
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 o= n the volume.

blkid /dev/mapper/back5

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.

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.

--047d7bdc7738ab95c604e1c2dda2-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 BTVvFIBqBRLx for ; Thu, 18 Jul 2013 08:24:34 +0200 (CEST) Received: from mail-ea0-x236.google.com (mail-ea0-x236.google.com [IPv6:2a00:1450:4013:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Thu, 18 Jul 2013 08:24:34 +0200 (CEST) Received: by mail-ea0-f182.google.com with SMTP id d10so1487971eaj.27 for ; Wed, 17 Jul 2013 23:24:33 -0700 (PDT) Message-ID: <51E78A0D.5090707@gmail.com> Date: Thu, 18 Jul 2013 08:24:13 +0200 From: Milan Broz MIME-Version: 1.0 References: <9A629FEC462BD94990DA2D70E6C94E8B193B3283@SUEX10-mbx-01.ad.syr.edu> In-Reply-To: <9A629FEC462BD94990DA2D70E6C94E8B193B3283@SUEX10-mbx-01.ad.syr.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Trying to mount pre-Luks encrypted external disks, suse 12.3 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: James Pacey Bennett Cc: "dm-crypt@saout.de" Sorry for top posting, but please first read section 7.6 of FAQ losetup->cryptsetup guide or https://lkml.org/lkml/2012/11/2/162 it should help you :) I am almost sure the options you used are not valid (ESSIV was never used in cryptloop etc). You have to specify options explicitly. As mentioned in document, options cannot be detected automatically. If you cannot find solution, please post _exact_ losetup parameters you are using and exact losetup (util-linux) version from working system (very important because Suse added some patches). Milan On 18.7.2013 1:41, James Pacey Bennett wrote: > I have several external backup disks encrypted before Luks appeared. After > update from 12.1 to 12.3, losetup is gone and I haven't been able to > mount the encrypted disks. > > linux-p22i /root# uname -r > 3.7.10-1.16-desktop > > linux-p22i /root# lsmod | grep crypt > cryptoloop 12715 0 > loop 27944 1 cryptoloop > dm_crypt 22845 2 > dm_mod 92315 4 dm_crypt > > linux-p22i /root# lsblk -f -l /dev/sdi1 > NAME FSTYPE LABEL UUID MOUNTPOINT > sdi1 > > ***/dev/sdi1 was previously under 12.1 mounted using losetup*** > > ***Because the partition isn't a Luks partition, I can't*** > linux-p22i /root# cryptsetup luksOpen /dev/sdi1 back5 > Device /dev/sdi1 is not a valid LUKS device. > > 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. > > Help! > jim bennett > > > _______________________________________________ > dm-crypt mailing list > dm-crypt@saout.de > http://www.saout.de/mailman/listinfo/dm-crypt >