On Thu, 24 Oct 2013, yuji_touya@xxxxxxxxxxxxxxxxxxxx wrote:
Here's syslog entries about raid10 and smartctl output. sdb seems to have too many bad blocks. Is that the reason why sdb was kicked out?
Most likely.
I'm going to copy files from /dev/md0 to anywhere else as soon as possible. Should I repair filesystem before copying? (like xfs_repair /dev/md0)
What you need to do now is to use dd_rescue or equivalent to copy the data off of sdb to a good drive. Stop the array first. This means you'll lose data on the bad blocks. After this is done, and you have assembled the array with the good drive with (most of) the data from sdb, start the array, then hot-add in sdc and let things sync up. You should now have redundancy.
Also check why you didn't get notification that sdc wasn't part of the array, usually mdmon or equivalent will send email about these events.
-- 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
