On Thursday March 9, sandro@xxxxxxxx wrote: > Yersterday i toubled with system crash due to an md device that stopped due > to an error on a single block (sata controller). That shouldn't cause a system crash. Do you have any kernel logs showing exactly what happened (what the single-block error was etc)? > > Starting from a live rescue cd to analize the situation I found that the > array thought the good disk was the one had the block failure, so > that reconstruction arrived at 75% and then restarted (I saw that > happending). That is very strange. Again, logs would be helpful. > > I eliminated the bad disk and the other couldn't start complaining it was a > spare one (but no one was configured as spare...) so that there where no > good disk. I had to turn it into a normal /dev/sda disk to be able to start > the system. > > My question is if there is a way to convince a device that it is the good > device w/o destroying the array and how it can happen that an array > component turns into a spare one. You can always re-create the array e.g. mdadm -C /dev/md -l1 -n2 /dev/sda missing This does not destroy data. > > What should I have one? Provided more details in logs :-) NeilBrown - 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
