2007-07-06 06:40 am (UTC)
mdadm -A --force /dev/md0
Will sync the superblocks. Assuming thats whats wrong. Dont hate me for hosing your array if this fails.
2007-07-06 06:41 am (UTC)
You get the idea.
Grass Valley is in Nevada County, which is shaped like a revolver pointed at Nevada because those bastards ripped off their name.
2007-07-06 04:04 pm (UTC)
Re: fun fact
no, drunk people don't pull shit like that. i'm an expert on the subject.
hypothetically I'd be looking for a place to dispose of said drunk girl's body.
I was going to say that "Hypothetically, I'd have lost myself a party guest for the future." Your solution is slightly more dramatic.
If only there was someone who was both a body disposal expert and a Linux filesystem guru!
That was the funniest blog comment I've read in 2007. Genius!
2007-07-09 07:29 pm (UTC)
Hypothetically my first question would be the best way to dispose of a body followed up by a question about RAID repair.
2007-07-06 03:14 pm (UTC)
The howto makes sense, but I'd make one small change since this is a cascade failure and not simultaneous. I'd look at syslog to find which drive went offline first. Take the rest of the drives and force them back into a broken array with mdadm --assemble --force.
In theory this will put your array back to the state before the 2nd drive was yanked and your data will still be there (since the array stops once you lose 2 disks)
After that, add the last disk back in as a spare and rebuild.
the raid was in the garage? seems like the heat would get to it?
2007-07-06 04:05 pm (UTC)
a) it's SF... brrr
just wrap that sucker in thermite cord and keep one ear to the scanner, all they'll get is a pile of molten metal. fuckin pigs!
I think you have just sold me on getting lockable trays. This is the second time I've heard about this routine.
2007-07-08 06:57 am (UTC)
ive seen her before, shes hot. party time!
Some people, when they have a complex technical problem to solve, think "I know, I'll ask for advice on LiveJournal!"
Now they have two problems.
2007-07-09 07:30 pm (UTC)
Hah. nice jwz quote variant.
My wife and I say that a lot when people talk about relationship problems, since asking for advice on LiveJournal (or rather, the internet) rarely leads to real solutions so much as it more often leads to HILARIOUS drama. It is slightly more useful for technical advice.
mdadm -E /dev/sd... is your friend. Go through each drive and you can figure out when they were "lost". This will be helpful. Watch out for drives that have been out for much longer than the rest.
Avoid having it rebuild.
Make sure you have a recent-ish mdadm and kernel - this stuff gets "I can't believe it worked before" fixes and improvements a lot.
Either force assemble (I think that might make it rebuild the last one) or you can _create the md device again!_ (as long as you keep the options the same). This sounds (and might be) crazy scary, but I've done it a few times to force it to go when I had one raid-5 failure and Linux decided that a second drive maybe was tired too. Yes, I rarely use raid-5 now.