neil wrote > 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. > okay, its solved at my end (as i jst informed the list and yourself) but would rather no one else is 'bitten' by this. again, it could be purely a semantical error or display problem and there wasnt a 'real' error, but, i am skeptical of that (no offense meant) > 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. > funnily enough, this is -exactly- what i did, i threw away /etc/raidtab and even went so far as to mv the raid* binaries into a directory under root ( go_away i called it ;), once i jst stuck with using mdadm, the actual operation was almost laughably easy. so, mea culpa :) thanks and best wishes Stef Telford <stef@chronozon.artofdns.com> - 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
