On Wednesday April 16, neilb@cse.unsw.edu.au wrote: > > Ok, this is wrong. Bigtime. > The spare has taken up postion 0 instead of 2. > > I cannot immediately see what would be causing this. The code looks > right, but obviously isn't. I'll try to see if I can reproduce it > tomorrow. > I haven't managed to reproduce it, but I'm faily sure that I know what was happening. I'll try to figure out the best way to fix it. In the mean time, you can avoid the problem by not using raidstart at all. Reboot your machine, with raidstart disabled (e.g. move /etc/raidtab out of the way) and then us mdadm to start the array. I think you will need "mdadm --assemble --force" to start it. That didn't work before because raidstart had already tried to started it and failed and the array have been left in an inconsistant start. I suggest the reboot to make sure the array is not in an inconsistant state. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
