On Monday March 21, Ruth.Ivimey-Cook@xxxxxxxxxx wrote: > Folks, > > I had to pull the plug on my box today, and when it rebooted got this > rather strange raid issue. The box has 5 raid1 arrays, consisting of 5 > partitions on each of 2 drives. When it rebooted, the md5 array came up > like so: > > raid1: raid set md0 active with 2 out of 2 mirrors > md: ... autorun DONE. > md: Autodetecting RAID arrays. > md: autorun ... > md: considering hda9 ... > md: adding hda9 ... ...repeated several times.... > md: export_rdev(hda9) > md: ... autorun DONE. > EXT3-fs: INFO: recovery required on readonly filesystem. > EXT3-fs: write access will be enabled during recovery. > EXT3-fs: recovery complete. > > Now this was the first time the string "md5" appears in the log. And > indeed, it appears that hda9 has been kicked out of the array: So was md5 actually running (what did /proc/mdstat show? What about mdadm -D /dev/md5?). My guess is that your startup scripts, possibly in an initrd used the RAID_AUTORUN command several times, and each time it found the drive which wasn't part of an array but couldn't be added to one. Nothing particularly interesting. If md5 hadn't actually been started, then that is interesting. 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
