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?
--
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
