Am Samstag, 7. Januar 2012, 13:27:04 schrieb Jeff Cranmer: > > > I tried changing the type of each array element in fdisk to fd (linux > > > raid autodetect. > > > > > > The array is still not being recognised at boot, with the same 'cannot > > > read superblock' error. > > > > > > I also tried re-running mdadm --create /dev/md0 --level=5 > > > --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1 > > > I get the error > > > mdadm: device /dev/sdb1 not suitable for any style of array. > > > > > > What is going on here? > > > > I am thinking ;) > > LOL! > > Me too. > > mdadm --detail /dev/md0 thinks that /dev/sdc1 is faulty. > I'm not sure whether it's really faulty, or just that my setup for RAID > is screwed up. > > How do I get rid of an existing /dev/md0?
you stop it. Override the superblock with dd.. and lose all data on the disks. > > I'm thinking that I can try creating a RAID1 array using the two > allegedly good disks and see if I can make that work. yeah > > If that works, I'll get rid of it and try recreating the RAID1 with one > good disk and the one that mdadm thinks is faulty. > you don't have to. You can migrate a 2 disk raid1 to a 3 disk raid5. Howtos are availble via google. just saying - box in suspend to ram. I change the cable (and connector on mobo) on a disk with two raid 1 partitions on it. One came back after starting the box. The other? Nothing I tried worked. At the end I dd'ed the partition.. and did a complete 'faulty disk/replacement' resync.... argl. -- #163933
