On 10/27/2017 04:45 AM, Wols Lists wrote: > You say you ran "mdadm --create" over the array? Oh dear oh dear oh > dear! :-( Yes, that's what I fear... If mdadm wasn't so darn reliable, I'd have to mess with it more than I do :) > > If the array was originally 1.0, and the re-create created it as 1.2, it > just stomped all over your data. > That explains it nicely. > And now it's probably having problems re-assembling because it's finding > two superblocks and doesn't know what to do with them. > > Bottom line, yes I suspect your array is recoverable. But your > filesystem is ALSO damaged, and trying to fix two problems has probably > squared the workload ... :-( > > The only good news I can see is it's a mirror. Your best bet is probably > to destroy both superblocks, and try and mount the partition directly > not as a mirror. That way, your only problem will be a damaged > filesystem. Don't try this until you've had better advice than mine, though! > Then the best bet is probably to just get rid of this array and wait until I get it installed back in the box with the good disk, leave this unplugged, boot in degraded mode on the good disk and re-add this one and let it re-sync. (I suppose?) How best to clear this array completely so that it doesn't cause mdadm any problem on the rebuild from the good array? > Cheers, > Wol (the bringer of bad news :-( Oh, the irony... -- David C. Rankin, J.D.,P.E. -- 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
