2010/12/19 Mikael Abrahamsson <swmike@xxxxxxxxx>: > On Sun, 19 Dec 2010, Bjørn Eikeland wrote: > >> Hope you guys can help me out with some input here! > > What mdadm and kernel version are you using? > > If you're not using the latest mdadm version (3.1.4 afaik) then try > --assemble --force with that one first. It does a better job than most of > the versions that come with most distributions today. > > Recreating the array is highly dangerous and it's definitely a last resort. > > -- > Mikael Abrahamsson email: swmike@xxxxxxxxx $ uname -a Linux filebear 2.6.32-26-generic #48-Ubuntu SMP Wed Nov 24 09:00:03 UTC 2010 i686 GNU/Linux $ mdadm -V mdadm - v3.1.4 - 31st August 2010 $ sudo mdadm --assemble --force /dev/md6 mdadm: /dev/md6 assembled from 2 drives and 2 spares - not enough to start the array. $ cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md6 : inactive sdc1[0](S) sdd1[6](S) sdh1[5](S) sda1[3](S) 3906236416 blocks unused devices: <none> mdadm was older, but same behavior with 3.1.14. It was a new ubuntu install a few days ago so didn't think of updating mdadm, kernel is fairly recent at least. -- 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