[GRLUG] RAID recovery
L. V. Lammert
lvl at omnitec.net
Fri Mar 7 17:13:22 EST 2014
Just had a chance to try and rebuild the array, ..
# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid0] [raid1] [raid10]
md127 : inactive sdb2[2](S) sdd2[3](S)
972580592 blocks super 1.0
md0 : active raid6 sdc2[1] sda2[0]
972580352 blocks super 1.0 level 6, 256k chunk, algorithm 2 [4/2]
[UU__]
bitmap: 2/4 pages [8KB], 65536KB chunk
Unfortunately, sdb2 can be neither failed nor removed:
# mdadm --manage /dev/md0 --fail /dev/sdb2
mdadm: set device faulty failed for /dev/sdb2: No such device
# mdadm --manage /dev/md0 --remove /dev/sdb2
mdadm: hot remove failed for /dev/sdb2: No such device or address
YET, the drive appears valid:
# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.21.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002933a
Device Boot Start End Blocks Id System
/dev/sdb1 2048 4192255 2095104 82 Linux swap /
Solaris
/dev/sdb2 4192256 976773119 486290432 fd Linux raid
autodetect
???
Thanks!
Lee
More information about the grlug
mailing list