| 1 |
Hi all, |
| 2 |
|
| 3 |
after a reboot (my machine was up for more than 6 months) I saw my raid |
| 4 |
with only one of two devices used, and I had to read the second |
| 5 |
partioition: |
| 6 |
|
| 7 |
#mdadm --manage /dev/md1 --add /dev/hda1 |
| 8 |
mdadm: re-added /dev/hda1 |
| 9 |
|
| 10 |
# cat /proc/mdstat |
| 11 |
Personalities : [raid1] [multipath] [faulty] |
| 12 |
md1 : active raid1 hda1[2] hdc1[1] |
| 13 |
29302464 blocks [2/1] [_U] |
| 14 |
[>....................] recovery = 2.8% (846976/29302464) finish=19.9min speed=23731K/sec |
| 15 |
|
| 16 |
|
| 17 |
Looking at dmes I saw this message: |
| 18 |
|
| 19 |
|
| 20 |
raid1: raid set md2 active with 1 out of 2 mirrors |
| 21 |
md: considering hdc1 ... |
| 22 |
md: adding hdc1 ... |
| 23 |
md: adding hda1 ... |
| 24 |
md: created md1 |
| 25 |
md: bind<hda1> |
| 26 |
md: bind<hdc1> |
| 27 |
md: running: <hdc1><hda1> |
| 28 |
md: kicking non-fresh hda1 from array! |
| 29 |
md: unbind<hda1> |
| 30 |
md: export_rdev(hda1) |
| 31 |
raid1: raid set md1 active with 1 out of 2 mirrors |
| 32 |
md: ... autorun DONE. |
| 33 |
|
| 34 |
so, seems that hda1 was out of sync... is this the meaning? |
| 35 |
How could it happen? cause mdadm did not send any email about my raid |
| 36 |
status.... |
| 37 |
|
| 38 |
TIA, |
| 39 |
|
| 40 |
-- |
| 41 |
Arnau Bria |
| 42 |
http://blog.emergetux.net |
| 43 |
Bombing for peace is like fucking for virginity |
Archives