>I tried that also. In fact, I tried all combinations, sorry I wasn't
>explicit about that. I get an error that /dev/sdb4 is not in the array,
>and /dev/sda4 is busy.
>
>I'm not even sure which one is the good one! I'm assuming that since
>/proc/mdstat tells me the second on is bad, and that /dev/sdb4 is the
>*second* defined drive for md2 in /etc/raidtab, that /dev/sdb4 is the
>faulty one (the log messages also point to this).
From your boot messages, sdb4 is the one with the older index and therefore
was kicked out. cat /proc/mdstat should prove this. sdb4 is not part
of the running
raid.
If this is the case, then sda4 holds the most recent data as part of
the raid. If the
data on your raid is okay you will probably have no problem (as said
before, I am new to
this and did not have a failure like this, but I had a similar
situation shortly after installing)
When hotadding the device back to the raid as pointed out in the
previous post, the data
will be synched from the newest drive, that is the one with the
highest index. From what I see,
you will be okay if you raidhotadd /dev/md2 /dev/sdb4 - as long as
sdb4 is working at all. the
data should not be so much apart, as the index is just one number
short at the moment.
Regards
Jochen
