> Anyways, so I pulled /dev/sdb and replaced it with a new disk, which I
> then partitioned to match /dev/sda. Made sure to set the part type to
> "fd" where appropriate.
>
> The system boots up fine off of /dev/sda, but won't start re-mirroring to
> /dev/sdb. The RAID HOWTO indicates it should "like magic".
It's not quite "like magic". You need to raidhotadd each partition on sdb to the
appropriate md device. e.g. "raidhotadd /dev/md0 /dev/sdb1". I think you are
referring to the situation where disks are not in sync, from, for example, an
unclean shutdown.
Cheers,
Bruno Prior [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron D. Turner
> Sent: 29 September 1999 17:05
> To: Linux Raid Mail List
> Subject: putting failed disk back in array
>
>
>
> I've got two identical systems each with two disks, which I'm intending to
> do root RAID1. I've got one system all configured (took a while). So I
> figured, hey, why not just swap disks in the systems and let RAID deal
> with recontructing the other disk. Figured it would save me a few hours
> building the second system...
>
> Anyways, so I pulled /dev/sdb and replaced it with a new disk, which I
> then partitioned to match /dev/sda. Made sure to set the part type to
> "fd" where appropriate.
>
> The system boots up fine off of /dev/sda, but won't start re-mirroring to
> /dev/sdb. The RAID HOWTO indicates it should "like magic".
>
> I'm Confused...
>
> --
> Aaron Turner | Either which way, one half dozen or another.
> [EMAIL PROTECTED] | http://www.pobox.com/~aturner/
>
> "There is no worse tyranny than to make a man pay for something he does
> not want merely because you think it would be good for him."
> -Benjamin Franklin
