On Fri, 11 Feb 2011 16:13:53 -0500 Christian <cjs703@xxxxxxxxx> wrote: > On Fri, Feb 11, 2011 at 3:49 PM, NeilBrown <neilb@xxxxxxx> wrote: > > On Fri, 11 Feb 2011 11:48:41 -0500 Christian <cjs703@xxxxxxxxx> wrote: > > > >> Hello, > >> > >> I have a 10 disk RAID6 array. I had an issue with a molex connector > >> that caused drives to drop from a 5in3 SATA backplane. There wasn't > >> any activity occurring on the array during the time, so I think the > >> filesystem should be in tact. The issue now is the event counts are > >> out of sync, along with the state of each drive. > >> > >> # mdadm -A /dev/md1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdk1 /dev/sdl1 > >> /dev/sdm1 /dev/sdq1 /dev/sdr1 /dev/sds1 /dev/sdt1 > >> mdadm: /dev/md1 assembled from 8 drives - not enough to start the > >> array while not clean - consider --force. > >> > >> # cat /proc/mdstat > >> Personalities : [raid6] [raid5] [raid4] > >> md1 : inactive sdt1[1](S) sde1[9](S) sdl1[8](S) sdg1[7](S) sdf1[6](S) > >> sdk1[5](S) sdq1[4](S) sds1[3](S) sdr1[2](S) sdm1[0](S) > >> 19535134720 blocks > >> > >> > >> # mdadm -Af /dev/md1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdk1 /dev/sdl1 > >> /dev/sdm1 /dev/sdq1 /dev/sdr1 /dev/sds1 /dev/sdt1 > >> mdadm: failed to RUN_ARRAY /dev/md1: Input/output error > > > > The array is already in a partially-assembled state. > > > > mdadm -S /dev/md1 > > > > before trying to assemble again with -f. > > > > NeilBrown > > I should have probably included it but I did stop the array with -S > before running -Af. True. Ok, being sure that the array is stopped first, try the "-Af" command again, but an a -v. Then post the results together with any kernel messages (dmesg | tail -50 maybe) 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
