[Please reply-to-all rather than replying through bugzilla so that people on cc list get to see replies... I hope bugzilla can pick the Bug number out of the middle of the subject line....]
On Tuesday May 1, [EMAIL PROTECTED] wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=8412 > > Summary: CONFIG_MOUSE_PS2 makes RAID detection fail Based on subsequent comments, I think you got that backwards - absense of CONFIG_MOUSE_PS2 makes RAID detection fail, but no matter.. > Kernel Version: 2.6.21 > Status: NEW > Severity: low > Owner: [EMAIL PROTECTED] > Submitter: [EMAIL PROTECTED] > > Problem Description: If a kernel without CONFIG_MOUSE_PS2 enabled is used, the > kernel won't detect my RAID1 array, but the hard drives it consits of are > properly detected and the partition type reads "FD - Linux Raid Autodetect" > as well. > No /dev/md0 is created while booting the kernel. > I built 2.6.21 with the same .config except for CONFIG_MOUSE_PS2 twice for > testing purposes and discovered this weird thing. > I'm going to attach the .config (without CONFIG_MOUSE_PS2), the dmesg of this > kernel as well as the CONFIG_MOUSE_PS2-enabled kernels dmesg. In the failure case, the SCSI drives (sdb, sdc) on which your raid resides are not getting detected until after md initialisation has decided that there is nothing to assemble. My first thought was that the new threaded device discovery was allowing md init to happen before scsi discovery was complete. Maybe the presence of CONFIG_MOUSE_PS2 makes some bit go faster... However # CONFIG_SCSI_SCAN_ASYNC is not set so maybe not... Greg (or anyone else reading): you know about this threaded discovery.. could it allow some discovery to complete after userspace has started, and does CONFIG_SCSI_SCAN_ASYNC affect it? I think you best bet is to not depend on raid-auto-detect but to run mdadm to assemble your arrays instead. As your root isn't on md/raid, that should be trivial to arrange. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
