Есть сервак с 4 винтами и несколькими рейдами. Упал один из рейдов. На нем важные данные. Не могу восстановить. Итак имеем.
Centos 6.5
cat /proc/mdstat
Personalities : [raid1] [raid10] [raid0]
md3 : active raid10 sdd5[3] sdc5[2] sdb5[1] sda5[0]
199973888 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
ФС ext4.
Пробовал
mdadm --stop /dev/md3
mdadm --create /dev/md3 -v --assume-clean --level=10 --raid-devices=4 /dev/sda5 /dev/sdb5 /dev/sdc5 /dev/sdd5
Потом пытаюсь монтировать и получаю
mount -a
mount: wrong fs type, bad option, bad superblock on /dev/md3,
missing codepage or helper program, or other error
tail -n 5 /var/log/messages
Aug 24 11:39:53 virtual kernel: [36729.899447] md/raid10:md3: active with 4 out of 4 devices
Aug 24 11:39:53 virtual kernel: [36729.899469] md3: detected capacity change from 0 to 204773261312
Aug 24 11:39:53 virtual kernel: [36729.899556] md3: unknown partition table
Aug 24 11:41:59 virtual kernel: [36855.542547] EXT4-fs (md3): VFS: Can't find ext4 filesystem
Aug 24 11:53:45 virtual kernel: [37562.178259] EXT4-fs (md3): VFS: Can't find ext4 filesystem
Пытаюсь запустить проверку
fsck /dev/md3
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/md3
Ладно. смотрим номер блоков
mke2fs -n /dev/md3
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=128 blocks, Stripe width=256 blocks
12500992 inodes, 49993472 blocks
2499673 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
1526 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
e2fsck -b 32768 /dev/md3
e2fsck 1.41.12 (17-May-2010)
e2fsck: Bad magic number in super-block while trying to open /dev/md3
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
И так с любым блоком. Дальше у меня идею уже закончились. Есть идеи?
