Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

The never-ending upgrade: RAID problem/question



discuss-bounces at blu.org wrote:
> You need to manually re-add the (new/replacement) drive back into
> the raid set.  Effectively you need to hotadd the new partitions.
> man raidhotadd
>
> -derek
>
I figured I'd need to do something like that - but raidhotadd doesn't exist
on this machine anymore.  The old configuration was under Fedora 2, and the
new is Fedora 4 (FC2 had it).  I've seen the following, though:

	mdadm /dev/md0 )B?add /dev/hdb1

Any reason why this is a bad idea?  By the way, here's the /etc/mdadm.conf
file:

# mdadm.conf written out by anaconda
DEVICE partitions
MAILADDR root
ARRAY /dev/md3 level=raid1 num-devices=2
uuid=1d85d30a:0e76aa12:3d0f1ebd:1df6ad15
ARRAY /dev/md2 level=raid1 num-devices=2
uuid=89ab5084:b8d7c8e6:a7d80406:ebcc7482
ARRAY /dev/md4 level=raid1 num-devices=2
uuid=9057f97a:b9502b33:79662356:951c6033
ARRAY /dev/md5 level=raid1 num-devices=2
uuid=7d7e06d3:95dd40a2:ff4a20d4:6ffedb48
ARRAY /dev/md1 super-minor=1
ARRAY /dev/md0 super-minor=0
ARRAY /dev/md6 level=raid1 num-devices=2
uuid=5d252297:7c1a6bbe:03a8a685:59d3af95

Note that the two lines for the original RAID don't seem to hold the correct
config information.  Is this something I could manually edit (minus the
uuid), or will mdadm -add do it for me?

 -Don




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org