Quoting "Mikael Abrahamsson" <swmike@xxxxxxxxx>: > On Tue, 11 Dec 2012, Andris Berzins wrote: > >> I found on internet that this can be fixed if I re-create raid with the same >> configuration, but with dead drive set as 'missing'. > > This is extremely dangerous. You would have been better off by first > trying --assemble --force. > >> However, I can not mount md1 and looks like it contains random data. The >> order is correct. However, I noticed that new raid device size is >> different from old one. > > Your data offset is different, most likely you're not using the same mdadm > version as was initially used to create the raid. Mdadm defaults have > changed over time regarding chink size, data offset and others. Thank you! I did not notice that. Looks that I will have to try downgrade kernel: http://serverfault.com/questions/427683/what-parameters-to-mdadm-to-re-create-md-device-with-payload-starting-at- 0x2200 > > I don't know off the top of my head how to change the mdadm data offset > unfortunately. > > -- > Mikael Abrahamsson email: swmike@xxxxxxxxx -- 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
