I had no idea about this particular configuration requirement. None of my reading mentioned setting the partition type. I originally created the array 1/2003 and don't remember having to set it. So, yes, more debugging info in dmesg would have saved me days of resyncing/tweak/reboot/resync cycles. (I'm not complaining, just very relieved to up and running again). On Fri, 2006-05-26 at 09:57 +0200, Mikael Abrahamsson wrote: > On Thu, 25 May 2006, Craig Hollabaugh wrote: > > > That did it! I set the partition FS Types from 'Linux' to 'Linux raid > > autodetect' after my last re-sync completed. Manually stopped and > > started the array. Things looked good, so I crossed my fingers and > > rebooted. The kernel found all the drives and all is happy here in > > Colorado. > > Would it make sense for the raid code to somehow warn in the log when a > device in a raid set doesn't have "Linux raid autodetect" partition type? > If this was in "dmesg", would you have spotted the problem before? > -- ------------------------------------------------------------ Dr. Craig Hollabaugh, craig@xxxxxxxxxxxxxx, 970 240 0509 Author of Embedded Linux: Hardware, Software and Interfacing www.embeddedlinuxinterfacing.com - 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
