From: Stone <stone@heisl.org>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Brocken Raid & LUKS
Date: Wed, 27 Feb 2013 08:26:42 +0100 [thread overview]
Message-ID: <512DB532.2080306@heisl.org> (raw)
In-Reply-To: <512BFF83.20004@turmel.org>
Am 26.02.2013 01:19, schrieb Phil Turmel:
> On 02/25/2013 03:11 PM, Stone wrote:
>
>>> i have a backup from the three devices and i switched back to partion
>>> case 1 and i fire up the fsck:
>>>
>>> fsck -y /dev/mapper/md2_nas
>>> fsck from util-linux 2.19.1
>>> e2fsck 1.41.14 (22-Dec-2010)
>>> fsck.ext4: Group descriptors look bad... trying backup blocks...
>>> The filesystem size (according to the superblock) is 1465134336 blocks
>>> The physical size of the device is 1465133568 blocks
>>> Either the superblock or the partition table is likely to be corrupt!
>>> Abort? yes
>>>
>>> thats all?
>>> is my chance on case 1 over?
>> should i try a fsck -a?
> No, go to case #2.
i dont understand anything
i have now three more disks an the mainboard for the spare copy.
here now my new systeminfo:
sda - system
sdb - new spare
sdc - new space
sdd - new space
sde - old raid
sdf - old raid
sdg - missing
sdh - old raid
i have take a copy from the sde sdf sdh to the new spare devices.
ddrescue /dev/sde /dev/sdb --force
ddrescue /dev/sdf /dev/sdc --force
ddrescue /dev/sdh /dev/sdd --force
now i would test case #2 with fsck -y and i have a look with parted over
the devices.
ALL devices (new space and old raid) have now the start sector at 34 and
not on 2048
here a example:
parted /dev/sdh unit s print
Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sdh: 3907029168s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 34s 3907029118s 3907029085s raid
i dont understand this. all devices had his start sector on 2048 also
the one i changed for the case #1 test.
how can this happend?
if i try a
mdadm --create /dev/md2 --assume-clean --chunk=512 --verbose --level=5
--raid-devices=4 /dev/sde1 /dev/sdf1 missing /dev/sdh1
cryptsetup luksOpen /dev/md2 md2_nas
i cant open luks because -> No key available with this passphrase
i dont understand this.
should i change the sector on all devices back to 2048 to check case #2?
next prev parent reply other threads:[~2013-02-27 7:26 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 16:01 Brocken Raid & LUKS stone
2013-02-19 17:57 ` Phil Turmel
[not found] ` <5123E4E9.3020609@heisl.org>
2013-02-19 21:16 ` Phil Turmel
[not found] ` <5123EF45.6080405@heisl.org>
[not found] ` <5123F7C7.7000406@turmel.org>
[not found] ` <5123FB71.3060509@heisl.org>
2013-02-20 0:31 ` Phil Turmel
2013-02-20 18:32 ` Stone
2013-02-20 18:39 ` Phil Turmel
2013-02-21 7:04 ` Stone
2013-02-21 9:42 ` stone
2013-02-21 13:29 ` Phil Turmel
2013-02-21 14:19 ` stone
2013-02-21 15:04 ` Phil Turmel
2013-02-21 15:30 ` stone
2013-02-21 15:38 ` Phil Turmel
2013-02-21 15:49 ` Phil Turmel
2013-02-21 16:32 ` Stone
2013-02-21 16:41 ` Phil Turmel
2013-02-21 16:43 ` Stone
2013-02-21 16:46 ` Phil Turmel
2013-02-21 16:51 ` Stone
2013-02-21 16:54 ` Phil Turmel
2013-02-21 17:17 ` Stone
2013-02-21 17:23 ` Stone
2013-02-21 17:36 ` Phil Turmel
2013-02-21 17:47 ` Stone
2013-02-21 18:00 ` Phil Turmel
2013-02-21 18:08 ` Stone
2013-02-21 18:11 ` Phil Turmel
2013-02-21 18:29 ` Stone
2013-02-21 18:54 ` Phil Turmel
2013-02-21 19:12 ` Stone
2013-02-21 19:17 ` Stone
2013-02-21 19:24 ` Phil Turmel
2013-02-21 19:29 ` Stone
2013-02-21 19:45 ` Phil Turmel
2013-02-21 19:46 ` Stone
[not found] ` <51269DE0.5070905@heisl.org>
2013-02-22 10:31 ` stone
2013-02-22 13:53 ` Phil Turmel
2013-02-22 14:58 ` Stone
2013-02-22 15:37 ` Phil Turmel
2013-02-22 18:17 ` Stone
2013-02-22 18:23 ` Phil Turmel
2013-02-22 20:43 ` Stone
2013-02-22 22:35 ` Phil Turmel
2013-02-22 22:42 ` Stone
2013-02-23 2:22 ` Phil Turmel
2013-02-23 3:11 ` Stone
2013-02-23 4:36 ` Phil Turmel
2013-02-23 10:19 ` Stone
2013-02-23 16:10 ` Phil Turmel
2013-02-23 22:26 ` Stone
2013-02-23 23:49 ` Phil Turmel
2013-02-24 0:13 ` Stone
2013-02-24 4:04 ` Phil Turmel
2013-02-24 7:10 ` Stone
2013-02-24 14:15 ` Phil Turmel
2013-02-24 18:22 ` Stone
2013-02-24 18:33 ` Phil Turmel
2013-02-24 19:23 ` Stone
2013-02-24 19:51 ` Phil Turmel
2013-02-24 20:15 ` Stone
2013-02-24 20:25 ` Phil Turmel
2013-02-24 20:38 ` Stone
2013-02-24 20:44 ` Phil Turmel
2013-02-24 20:47 ` Stone
2013-02-25 9:06 ` stone
2013-02-25 18:31 ` Stone
2013-02-25 20:11 ` Stone
2013-02-26 0:19 ` Phil Turmel
2013-02-27 7:26 ` Stone [this message]
2013-02-27 19:04 ` Stone
2013-02-27 19:33 ` Hans-Peter Jansen
2013-02-27 19:51 ` Stone
2013-03-02 17:13 ` Phil Turmel
[not found] ` <5127B0AB.5040108@heisl.org>
2013-02-22 18:30 ` Phil Turmel
2013-02-21 22:29 ` Chris Murphy
2013-02-21 22:34 ` Phil Turmel
2013-02-21 22:20 ` Chris Murphy
2013-02-21 22:26 ` Phil Turmel
2013-02-21 13:15 ` Phil Turmel
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=512DB532.2080306@heisl.org \
--to=stone@heisl.org \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
/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; as well as URLs for NNTP newsgroup(s).