On Wed, Apr 18, 2012 at 10:22 AM, Tom Rini <tom.rini@xxxxxxxxx> wrote: > Hey all, > > As part of tracking down a bug in mvsas in 3.4-rc3, my raid0 array got > trashed a bit. Currently mdadm --misc /dev/.. -E gives results like > this: http://pastebin.com/X2kWmF1A is there a backup copy of the > metadata somewhere or some other way to force re-creating the array > and let e2fsck decide if there's anything salvageable? If not I can > live with re-creating it. Thanks! Please disregard. I had tried backing up the disks, passing to a VM and re-creating the raid there, with no luck. On the real HW (after backing up again to be safe), this did seem to work. -- Tom -- 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
