| 1 |
Hi, |
| 2 |
|
| 3 |
I woke up this morning to see the dreaded email from mdadm telling me |
| 4 |
one of my drives failed overnight, while I was happily dreaming about |
| 5 |
cute puppies and kittens installing a rainbow-colored roof on my |
| 6 |
house. The array is a RAID6 (two parity drives) and this is the |
| 7 |
current state: |
| 8 |
|
| 9 |
md0 : active raid6 sdd1[5] sdg1[4] sde1[3](F) sdh1[2] sdf1[1] sdi1[0] |
| 10 |
11720009728 blocks super 1.2 level 6, 512k chunk, algorithm 2 |
| 11 |
[6/5] [UUU_UU] |
| 12 |
|
| 13 |
I've been using RAID in Linux for years, but this is actually the |
| 14 |
first time I've had a disk fail in one. |
| 15 |
|
| 16 |
If I remember correctly, the process should be as simple as: |
| 17 |
|
| 18 |
#remove the failed disk from the array: |
| 19 |
mdadm /dev/md0 -r /dev/sde1 |
| 20 |
|
| 21 |
#pull the drive, replace with new one, partition it, then add it to the array: |
| 22 |
mdadm /dev/md0 -a /dev/sde1 |
| 23 |
|
| 24 |
and sit back and eat popcorn while I enjoy the blinkenlights for the |
| 25 |
next several hours/days? :) Any advice/suggestions for managing this |
| 26 |
process any differently? |
| 27 |
|
| 28 |
For now I have unmounted the filesystem that sits atop it, to prevent |
| 29 |
any more writes from occurring, just in case... |
| 30 |
|
| 31 |
Thanks, |
| 32 |
Paul |
Archives