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 >