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: Sun, 24 Feb 2013 08:10:04 +0100 [thread overview]
Message-ID: <5129BCCC.7090202@heisl.org> (raw)
In-Reply-To: <51299135.1000206@turmel.org>
Am 24.02.2013 05:04, schrieb Phil Turmel:
> On 02/23/2013 07:13 PM, Stone wrote:
>> Am 24.02.2013 00:49, schrieb Phil Turmel:
>>>>> 1) The partition doesn't go far enough to the end of the disk,
>>> For this, repartition /dev/sdc to start at sector 2048 and end at
>>> 3907029118. Then re-create the array, open luks, and do "fsck -n" and
>>> show the results.
>> roger that.
>> i would do this:
>> parted /dev/sdc
>> unit s
>> resize 1 2048 3907029118
>> parted /dev/sdc unit s print -> to check my new settings
>> recreate the md2 device with chunk 512 and the order we find out.
>> open luks
>> check it with fsck -n and report you my (errors) result.
> Do not use "resize". (And it doesn't exist in current versions of
> parted anyways.) Use rm then mkpart.
>
> Otherwise, Yes.
frist try:
parted /dev/sdc unit s print
Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sdc: 3907029168s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 2048s 3907029118s 3907027071s primary
One or more block group descriptor checksums are invalid. Fix? no
Group descriptor 0 checksum is invalid. IGNORED.
Group descriptor 1 checksum is invalid. IGNORED.
Group descriptor 2 checksum is invalid. IGNORED.
Group descriptor 3 checksum is invalid. IGNORED. -> Up to 44712
...
...
Inode 12130 has a extra size (40545) which is invalid
Fix? no
Inode 12131 is in use, but has dtime set. Fix? no
Inode 12131 has a extra size (60293) which is invalid
Fix? no
Inode 12131, i_size is 10232047334267190319, should be 0. Fix? no
Inode 12131, i_blocks is 205664983023728, should be 0. Fix? no
Inode 12132 is in use, but has dtime set. Fix? no
Inode 12132 has a extra size (15477) which is invalid
Fix? no
...
...
and on the end
Suppress messages? no
Illegal block #1020 (3776472337) in inode 11884. IGNORED.
Illegal block #1023 (4146244532) in inode 11884. IGNORED.
Illegal block #1026 (3701080588) in inode 11884. IGNORED.
Illegal block #1028 (3560657754) in inode 11884. IGNORED.
Illegal block #1029 (3846570075) in inode 11884. IGNORED.
Illegal block #1030 (2560600395) in inode 11884. IGNORED.
Illegal block #1031 (2695974737) in inode 11884. IGNORED.
Illegal block #1034 (3747644559) in inode 11884. IGNORED.
Illegal block #1035 (3005116177) in inode 11884. IGNORED.
Illegal indirect block (3855214404) in inode 11884. IGNORED.
Error while iterating over blocks in inode 11884: Illegal indirect block
found
e2fsck: aborted
the output have 711mb..
do you ned more examples?
what do you say to case1?
>
>>>>> 2) The partition starts too far into the disk (move start sector to 34
>>>>> like sdb and sde).
>>>>>
>>>>> For this, repartition /dev/sdc to start at 34 and end at 3907029118.
>>>>> This makes it match sdb and sde. Then re-create the array, open luks,
>>>>> and do "fsck -n" and show the results.
>> this is the next step if you say step one is the wrong one.
>> parted /dev/sdc
>> unit s
>> resize 1 34 3907029118
>> parted /dev/sdc1 unit s print -> to check my new settings
>> recreate the md2 device with chunk 512 and the order we find out.
>> open luks
>> check it with fsck -n and report you again my (errors) result.
> Same here. Delete the partition with rm, then create it at the new
> location and size.
>
> Phil
next prev parent reply other threads:[~2013-02-24 7:10 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 [this message]
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
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=5129BCCC.7090202@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).