On Fri, 15 Feb 2013, Dragon wrote:
In my case the superblock seems to be on all disks persistant, i use the same version and chunk-size.
The problem is that you used --create which just overwrites your old superblocks. So the information on your current superblocks might very well be wrong. The order of the drives might be wrong, you might have wrong chunk size, you might have wrong data offset, you might even have wrong superblock version.
Since you didn't save the superblock information before you did --create, it's hard to give you advice on how to proceed.
If you have old log entries (syslog) from when the raid was successfully started and stopped before you ran into trouble, that might contain some information that might help.
-- 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
