On 9/1/06, Richard Broersma Jr <[EMAIL PROTECTED]> wrote:
> Did you remove the faulty device first?
yup.
Personalities : [raid1] [raid10] [multipath]
md4 : active raid1 hdg1[1]
293049600 blocks [2/1] [_U]
IIRC, raid devices start
> numbering at 0, so it looks like this is trying to add a third device
> (#2), instead of replacing #0 or #1.
I am not exact sure on this point. Are you refering to the meta device?
No, I mean the device numbers. I'm now at home, so I can test a bit
with my AMD64 box. When I create a raid1 array there, /proc/mdstat
contains:
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid1 sdb2[1] sda2[0]
9775488 blocks [2/2] [UU]
[>....................] resync = 2.7% (271552/9775488)
finish=2.3min speed=67888K/sec
Notice the 2 device nodes....[1] and [0]. I think your setup is
trying to add a [2], which probably doesn't work because the array was
created with --raid-devices=2. This is only a guess though, based on
the " as 2" part of the error message.
Ok, so lets say I create an array with a missing element:
~ > mdadm --create --level=1 --raid-devices=2 /dev/md0 missing /dev/sdb2
mdadm: /dev/sdb2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sat Sep 2 02:07:13 2006
Continue creating array? yes
mdadm: array /dev/md0 started.
~ > cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid1 sdb2[1]
9775488 blocks [2/1] [_U]
unused devices: <none>
Ok, so now let me try repairing it...
~ > mdadm --add /dev/md0 /dev/sda2
mdadm: added /dev/sda2
~ > cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid1 sda2[2] sdb2[1]
9775488 blocks [2/1] [_U]
[>....................] recovery = 3.4% (340928/9775488)
finish=2.3min speed=68185K/sec
unused devices: <none>
Hmm, works fine.... :-(
Ok, maybe stupid questions time.
/dev/hdj1 does exist, right?
Is this the same drive that was once part of the array? Or a new drive?
If new, is the partition at least as large as /dev/hdg1? (double
check with fdisk output).
If the same drive, does it work if you do "mdadm --zero-superblock
/dev/hdj1" first?
What does "mdadm --examine /dev/hdj1" report? How about for /dev/hdg1?
I know that is a lot of questions to ask, but I don't see anything
obviously wrong at this point...so I am grasping at straws.
-Richard
--
gentoo-user@gentoo.org mailing list
