On 30 October 2010 22:10, Leslie Rhorer <lrhorer@xxxxxxxxxxx> wrote: >> -----Original Message----- >> From: linux-raid-owner@xxxxxxxxxxxxxxx [mailto:linux-raid- >> owner@xxxxxxxxxxxxxxx] On Behalf Of Phil Turmel >> Sent: Saturday, October 30, 2010 10:46 AM >> To: Jon@xxxxxxxxxxxxxxx >> Cc: Jon Hardcastle; linux-raid@xxxxxxxxxxxxxxx >> Subject: Re: argh! >> >> On 10/30/2010 07:56 AM, Jon Hardcastle wrote: >> > Guys, >> > >> > a new HDD has failed on me during a scrub.... i tried to remove/fail it >> but >> > it kept saying the device was busy. so i forced a reboot. >> > >> > I have physically disconnected the drive.. >> > >> > can anyone take alook at the examine below and tell me if it is should >> > assemble ok? >> > >> > I tried >> > >> > mdadm --assemble /dev/md4 /dev/sda1 /dev/sdb1 /dev/sdd1 /dev/sde1 >> /dev/sdf1 >> > /dev/sdg1 >> >> I'd try: >> >> mdadm --assemble /dev/md4 /dev/sd{g,a,e}1 missing /dev/sd{d,b,f}1 > > > Yeah, I would, too. Also, what are the contents of > /etc/mdadm/mdadm.conf? If it is correct, then `mdadm --assemble --scan` > should work. > > Hey, yeah I am confused as drives have failed before and it has still assembled. I think it is because it is unclean.... Can I ask how did you arrive at the command list? what is wrong with dbf? also this is my mdadm.conf DEVICE /dev/sd[abcdefg]1 /dev/hd[ab]1 ARRAY /dev/md/4 metadata=0.90 UUID=7438efd1:9e6ca2b5:d6b88274:7003b1d3 ARRAY /dev/md/3 metadata=0.90 UUID=a1f24bc9:4e72a820:3a03f7dc:07f9ab98 ARRAY /dev/md/2 metadata=0.90 UUID=0642323a:938992ef:b750ab21:e5a55662 ARRAY /dev/md/1 metadata=0.90 UUID=d4eeec62:148b3425:3f5e931c:bb3ef499 -- 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
