mdadm question

[Andreas John <lists@aj.net-lab.net>]

Hello!

I have a question about mdadm usage. One of me customers killed a 
raid5+1 by accidently removing an ide bus with two disk on it (dont't 
ask, I know ;-))

Assuming that the data is on the disks I'm looking for a way to convince 
  linux to mark the superblocks (of the missing disk only?) as "not 
failed" so that the raid comes up again. mdadm seems to have what I am 
looking for, like "madm --assemble --update=? --force" can write the 
superblocks freshly without destorying the data on it? Do I have to use 
--update=super‐minor or --update=super‐minor on ia32?
Or is there an recovery tool for such a case (i.e. mddump?)?

If this does not work, can anyone point me out where I can find an 
overview about the structure of a superblock, so that I may fix the 
problem via hex-editor (my skills point back to C64 times ... :-))
I've seen the source but some kind of overview/scheme would be nice.

I'm scared. :)

Rgds,
Andreas


-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html