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 c7tF7NHQc3nI for ; Mon, 18 Feb 2013 19:34:03 +0100 (CET) Received: from donkey.heisl.org (mail.heisl.org [86.59.94.243]) by mail.saout.de (Postfix) with ESMTP for ; Mon, 18 Feb 2013 19:34:02 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by donkey.heisl.org (Postfix) with ESMTP id 8E7D7285475 for ; Mon, 18 Feb 2013 19:28:51 +0100 (CET) Received: from donkey.heisl.org ([127.0.0.1]) by localhost (donkey.heisl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xf7ljBiSzd8k for ; Mon, 18 Feb 2013 19:28:51 +0100 (CET) Received: from [192.168.0.20] (chello213047090191.3.14.vie.surfer.at [213.47.90.191]) (Authenticated sender: stone@heisl.org) by donkey.heisl.org (Postfix) with ESMTPSA id 35FB5285474 for ; Mon, 18 Feb 2013 19:28:51 +0100 (CET) Message-ID: <512272D9.8090601@heisl.org> Date: Mon, 18 Feb 2013 19:28:41 +0100 From: Stone MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------070800030505000504000404" Subject: [dm-crypt] Device /dev/md2 is not a valid LUKS device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de This is a multi-part message in MIME format. --------------070800030505000504000404 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit 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. --------------070800030505000504000404 Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable 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=3D5 --raid-devices=3D4 /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.

=A0
--------------070800030505000504000404--