| 1 |
On 19-Apr-12 20:20, Mike Diehl wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] |
| 5 |
> md1 : active raid1 sdb1[1] sda1[0] |
| 6 |
> 112320 blocks [2/2] [UU] |
| 7 |
> |
| 8 |
> md3 : active raid1 sdb3[2](F) sda3[0] |
| 9 |
> 308255104 blocks [2/1] [U_] |
| 10 |
> |
| 11 |
> My question is, "which one?" Usually I get a [UU] on a good RAID, and an _ |
| 12 |
> for the failed drive. That would indicate that sda3 has failed. However, |
| 13 |
> sdb3 is marked with an (F), which I've never seen before. |
| 14 |
|
| 15 |
It means you just ran out of luck. As software-raid howto says: |
| 16 |
"...if you have a failure, the failed device will be marked with (F)..." |
| 17 |
|
| 18 |
But before you start changing drives, I'd try rebuilding md3 |
| 19 |
again from scratch. Linux software-raid is very sensitive to |
| 20 |
various "out-of-sync" conditions, i.e. when one drive starts |
| 21 |
realocating weak sector, or gets switched to some energy saving |
| 22 |
mode. This problem is quite common for "non-raid" drives... |
| 23 |
|
| 24 |
Jarry |
| 25 |
|
| 26 |
-- |
| 27 |
_______________________________________________________________ |
| 28 |
This mailbox accepts e-mails only from selected mailing-lists! |
| 29 |
Everything else is considered to be spam and therefore deleted. |
Archives