sylvain> Happy New Year and received all my best wishes for 2015. i'm sylvain> back to home. Me too, but heading to bed soon, been a busy day here. sylvain> Now, the failed raid is at 700km (~400 miles) :-( I should sylvain> work only by phone and ssh to repair the Raid. It sucks having to work at a distance like this. sylvain> We have changed the right disk and the raid is rebuilding. I sylvain> wille write you when it's finished. Many many thank's for sylvain> your help and your patience. My real suggestion to you is to now collect all the information you can on the system, including drive serial numbers, and how they map to each device and member of the RAID array. Sometimes when a system reboots, or you add new disks, things get re-arranged and you don't notice at first. And that leads you down the wrong path quite quickly. sylvain> I have a question to migrate Raid 5 to Raid 6 : sylvain> This site sylvain> http://www.ewams.net/?date=2013/05/02&view=Converting_RAID5_to_RAID6_in_mdadm sylvain> describe the right cookbook? I don't want re-do this bad sylvain> Story. It looks right to me. But I would also suggest that you look through the archives of this list, and make sure you have a newer version of the mdadm tool before you try to do this. I would also suggest that you add two new disks, one to be used as a hot spare, and the other used to grow the array into a RAID6. Then go through and make sure that all your drive timeouts are set properly on system boot, so that if a disk hangs when trying to re-read a bad block, it won't cause it to be kicked out of the array too quickly. Again, check the recent archives (last three months of 2014) of the list for examples and discussions of this issue. Good luck! John -- 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
