From: Stone <stone@heisl.org>
To: dm-crypt@saout.de
Subject: [dm-crypt] Device /dev/md2 is not a valid LUKS device
Date: Mon, 18 Feb 2013 19:28:41 +0100 [thread overview]
Message-ID: <512272D9.8090601@heisl.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
hi guy's.
i new in your mailing list and i have a problem with my setup.
today my raid5 degraded totaly and i can fix it with a command to re-created
/mdadm --create /dev/md2 --assume-clean --verbose --level=5
--raid-devices=4 /dev/sdc1 /dev/sdd1 missing /dev/sdf1/
After this i add my /dev/sde1 also to my /dev/md2 device.
My problem is now the i cannot open my crypt device
/cryptsetup luksOpen /dev/md2 md2_nas//
//Device /dev/md2 is not a valid LUKS device./
Befor one year i has the device created with this command:
/luksformat -t ext4 /dev/md0/
A dont have a backup of the header.
Is the filesystem broken?
/fsck /dev/md2//
//fsck from util-linux 2.20.1//
//e2fsck 1.42 (29-Nov-2011)//
//fsck.ext2: Superblock invalid, trying backup blocks...//
//fsck.ext2: Bad magic number in super-block while trying to open /dev/md2/
Is there a chance to get my data from the device?
Thank you.
[-- Attachment #2: Type: text/html, Size: 1443 bytes --]
next reply other threads:[~2013-02-18 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 18:28 Stone [this message]
2013-02-18 20:13 ` [dm-crypt] Device /dev/md2 is not a valid LUKS device 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=512272D9.8090601@heisl.org \
--to=stone@heisl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox