On Tue, Aug 16, 2016 at 12:59 PM, <linux@xxxxxxxxxxxxxxx> wrote: > I tried to assemble the raid array again. If that doesn't explain it, then I > don't know. Why would trying to assemble the raid change anything? The array is assembling correctly per the metadata on those two drives. That there's no ext4 signature on that array, the date of creation of the array is 10 days ago, all suggests that the original array used metadata version other than 1.2, putting the ext4 superblock in the location where 10 days ago mdadm --create obliterated that ext4 superblock with an mdadm 1.2 superblock. There are a lot of "fix me" guides out there that suggest doing mdadm --create and it's 99% of the time really horrifically bad advice that causes data loss that looks awfully lot like what's going on here. >The two drives that make up the array haven't been > touched/modified. Obviously that's not true. The only possible chance to recover this is if you have an exact sequence of events modifying the drive, so that they can maybe be reversed. Without that, any change will do more damage and decrease the chance of recovery. But seeing as this is a raid0 I suspect you have a complete backup of the drive anyway so you're probably better off just starting over with it. -- Chris Murphy -- 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
