I already tried that:
root@Torero-2:~ # cat /proc/mdstat
Personalities : [linear] [raid5]
md0 : active raid5 sdg1[6] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1] sda1[0]
1367507456 blocks level 5, 512k chunk, algorithm 2 [8/7] [UUUUUUU_]
unused devices: <none>
root@Torero-2:~ # mdadm /dev/md0 -r /dev/sdh1
mdadm: hot remove failed for /dev/sdh1: No such device or address
root@Torero-2:~ # mdadm /dev/md0 -a /dev/sdh1
mdadm: Cannot open /dev/sdh1: Device or resource busy
root@Torero-2:~ #
With no luck :(
Paco.
> -----Mensaje original-----
> De: Neil Brown [mailto:neilb@xxxxxxxxxxxxxxx]
> Enviado el: lunes, 18 de julio de 2005 0:11
> Para: Francisco Zafra
> CC: linux-raid@xxxxxxxxxxxxxxx
> Asunto: Re: Recovery raid5 after sata cable failure.
>
> On Sunday July 17, fzafra@xxxxxxxxx wrote:
> > Hi all,
> >
> > I have raid5 array working without problem for some
> months. A SATA
> > cable failed and de raid5 works fine keeping the superblock
> > persistent, but now, I can't get the old device inserted
> into the array.
> ...
> >
> > And I try to re-add the old disk in this way:
> >
> > root@Torero-2:/mnt/raid5 # mdadm /dev/md0 -a /dev/sdh1
> > mdadm: Cannot open /dev/sdh1: Device or resource busy
> >
> > What is wrong? What I am doing bad? Sdh1 is absolutely
> unused, so I
> > don't understand the error "resource busy"
>
> Well, it definitely is busy...
>
> Maybe it is still part of md0, but marked as 'faulty'.
> If so (cat /proc/mdstat would tell you) you need to remove it first.
> mdadm /dev/md0 -r /dev/sdh1
> mdadm /dev/md0 -a /dev/sdh1
>
> NeilBrown
>
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
