Re: Brocken Raid & LUKS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux