[Wolves] Software RAID reconstruction

[David Goodwin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

<snip>

Shouldn't you really have forced sdc1 to be the array 'source' and
failed sdd1?


Considering it's all handled at the bit level, it's possible that you
could reconstruct the array from sdc1.

I think the bit about sdc1 being out of date is a red herring - after
all sdd1 has failed (for whatever reason), so it can hardly be judged to
be an authority!


I'd be tempted to:

a) Take a dd disk image of sdc1 (unless you have backups you can use?)

b) Recreate the array with sdc1 being the only device present, and see
if you can access it... if so, is the data valid?  This should end up
causing the raid superblock to alter, but not the filesystem table - so
you should still be able to access the data etc.

sdc1 should still be a valid disk - as even though it's partially
resynced, the order of the data should be maintained and it should be
writing the same content to the blocks as was there previously.

(At least that's my understanding of how it works...)

(I'm no expert... [insert disclaimer here])

David.

- --
David Goodwin

[ david at codepoets dot co dot uk ]
[ http://www.codepoets.co.uk       ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIs9X3/ISo3RF5V6YRAjwHAKCAAWGO1MdCvkVxpXBLj7JgJjrm8ACgkJA+
/xb0npfUL55Zubtaeq3yg6w=
=T3Yd
-----END PGP SIGNATURE-----