From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Restore a LUKS partition
Date: Thu, 21 Nov 2013 02:57:45 +0100 [thread overview]
Message-ID: <20131121015745.GA18997@tansi.org> (raw)
In-Reply-To: <528D60FC.4050008@elso.mine.nu>
On Thu, Nov 21, 2013 at 02:25:16 CET, Michael Grosseck wrote:
> Hello,
>
> I created a luks partition for a long time with Ubuntu 10.04. Most
> likely I used following command to create it.
>
> # cryptsetup -c blowfish-cbc-essiv:sha256 -y -s 256 luksFormat /dev/sda6
>
> In the meantime I changed the distro to Linux Mint 13.
> Now I tried to open it, but I get an error. Also if I try to dump
> the header information.
>
> $ sudo cryptsetup luksDump -vc blowfish-cbc-essiv:sha256 /dev/sda6
> Device /dev/sda6 is not a valid LUKS device.
> Command failed with code 22: Device /dev/sda6 is not a valid LUKS device.
Use cryptsetup -v isLuks to find whether it is a LUKS container,
no other parameters.
> I was not sure if the drive is a LUKS device at all and I have read
> in another forum I should search for LUKS, what I did.
>
> $ sudo dd if=/dev/sda6 | grep -a -b LUKS
> 0:�������?\x111�U�LUKS��\x01blowfishcbc-essiv:sha256sh
> E���\x17���֬�y[8�@��/�\x06ā\x04�]1b(�?K \x1c�uP�Xb6'\x18��C��
> 362478668:rC�+9���\\x01D�#�8*\x12tfoye�/�34ڛ�OCI\x1f[��\x19�5���E\x15!U�3_B\x02��%�\x11rLUKS�\x01$i}�H�[g>�rw̋��G�O
> �����6��>�b�\x02�s��e$�tɞV
That is not the way to search. Better post what
hd /dev/sda6 | head
gives you.
> So indeed it seems a LUKS device, but the header is somehow corrupt.
>
> Now I tried to make a plain mapping what unexpected really works.
> But the joy was short. I can not mount the mapped device.
You can always create a plain mapping, there is no error checking
as a plain device has no header.
> $ sudo cryptsetup create -c blowfish-cbc-essiv:sha256 -s 256 crypt /dev/sda6
> Enter passphrase:
> $ sudo mount /dev/mapper/crypt /home/crypt/
> mount: you must specify the filesystem type
> $ sudo mount -t ext3 /dev/mapper/crypt /home/crypt/
> mount: wrong fs type, bad option, bad superblock on /dev/mapper/crypt,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
> Now my question. Is there a little hope to restore the LUKS header
> or at least to read the content of this partition somehow?
Completely unclear at this time.
Arno
> Thanks for your help
>
> Michael
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
next prev parent reply other threads:[~2013-11-21 1:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 1:25 [dm-crypt] Restore a LUKS partition Michael Grosseck
2013-11-21 1:57 ` Arno Wagner [this message]
2013-11-21 8:11 ` Michael Grosseck
2013-11-21 15:44 ` Arno Wagner
2013-11-21 16:19 ` Robert Nichols
2013-11-21 21:53 ` Michael Grosseck
2013-11-21 22:36 ` Arno Wagner
2013-11-21 22:37 ` Arno Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131121015745.GA18997@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.