On Friday September 23, A.J.Dawson@xxxxxxxxxxxxxx wrote: > After a fairly long time without seeing the following message: > > "This is an automatically generated mail message from mdadm > running on servername > > A DegradedArray event had been detected on md device /dev/md0. > > Faithfully yours, etc." > > It reared its head again today. > > I've checked dmesg and /var/log/messages and the only thing I've found so > far is the following in dmesg: > > md: considering sda1 ... > md: adding sda1 ... > md: created md0 > md: bind<sda1> > md: running: <sda1> > raid1: raid set md0 active with 1 out of 2 mirrors > > md1 works fine and md sets md1 active with 2 out of 2 mirrors. > > /dev/sdb2 is the device that appears to be causing the problem, so can > anyone tell me what might be happening? Any ideas why it might not be > included in the array at boot time? (I've tried Google but found no > answers yet). > > Any help would be appreciated! Looks a lot like sdb2 (sure it isn't sdb1?) isn't type 'FD'. NeilBrown - 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
