On September 8, skvidal@phy.duke.edu wrote: > > > Probably. What is the actual message? > > All of the output attached below: > > raid5: using function: p5_mmx (2653.200 MB/sec) > md: raid5 personality registered as nr 4 > Journalled Block Device driver loaded > md: Autodetecting RAID arrays. > [events: 00000053] > [events: 00000053] > [events: 00000053] > md: autorun ... > md: considering sdf1 ... > md: adding sdf1 ... > md: adding sde1 ... > md: adding sdc1 ... > md: created md1 > md: bind<sdc1,1> > md: bind<sde1,2> > md: bind<sdf1,3> > md: running: <sdf1><sde1><sdc1> > md: sdf1's event counter: 00000053 > md: sde1's event counter: 00000053 > md: sdc1's event counter: 00000053 > md1: former device sdb1 is unavailable, removing from array! > md1: former device sdd1 is unavailable, removing from array! > md1: former device sdg1 is unavailable, removing from array! > md1: former device sdh1 is unavailable, removing from array! Looks like sd[bdgh]1 are *not* marked as auto-detect-raid in the partition table. Use fdisk/cfdisk to check. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
