Dang, that's an awfully old thread that you linked.
I've lost half of a mirrored array and simply failed the bad drive and proceeded as you indicated, but in that case I knew exactly which drive was bad.
I never did a dd, just reinitialized the bad one put it in as a spare, and got the hell out of mdadm's way while it rebuilt the array. Took quite a while.
Most of the details are lost to the fog of time.
"David C. Rankin"
On 12/06/2013 02:23 PM, David C. Rankin wrote:
The big question is how to approach data recovery? Favorite links or tools? I have a write-up or two squirreled away somewhere from years past about dd/dd_rescue for copying the partitions, but I haven't done this on a md array before. Any help, or suggestions will be much appreciated.
It appears I'm not alone with this type of raid failure:
http://forums.opensuse.org/english/get-technical-help-here/install-boot-logi...
Apparently, for reasons unknown, temporary errors in writing data to one drive will cause the drives to fall out of sync. In this case, mdraid cannot re-sync or rebuild because it doesn't know which is the complete drive. The approach seems to be the same as a failed drive. Try and determine which is the good drive with mdadm (-E|-D), pick one, fail it, remove it, try booting on the remaining good drive, then zero-superblock on the removed drive, re-add the drive to the array and it should re-sync.
If anyone has any other thoughts on the matter, let me know. Thanks.
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org