On Mon, Mar 21, 2016 at 08:42:16AM -0400, Phil Turmel wrote: > On 03/20/2016 06:37 PM, Andreas Klauer wrote: > > This is what you get when you use --create --assume-clean on disks > > that are not actually clean... or if you somehow convince md to > > integrate a disk that does not have valid data on, for example > > because you copied partition table and md metadata - but not > > everything else - using dd. > > > > Something really bad happened here and the only person who > > can explain it, is probably yourself. > > This is wrong. Your mdadm -D output clearly shows a 2014 creation date, > so you definitely hadn't done --create --assume-clean at that point. > (Don't.) It was just an example. You get a mismatch if (at least) one disk has wrong data on it; this many mismatches means there is a disk full of wrong data for some reason we do not know, hence I suggested trying to assemble it with disks missing, in the hope the data will start making sense once the bad disk(s) are gone. > Something else is wrong, quite possibly hardware. Nothing is impossible, but for a hardware error this is very unusual. > I would use an overlay for that. Use overlays, and for disks with bad sectors, make good copies of them (make sure to remember which of them were bad and where the holes in the copies are, i.e. keep the ddrescue logs). If you play around with disks that already have bad sectors, they might die completely on you. Regards Andreas Klauer -- 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
