I am doing software raid on Redhat AS4 with SATA drives. I am using GRUB Both disks are bootable i checked it out one by one n system boots from any one installed disk. Prb is when i add new disk and run this script
#!/bin/bash
echo Please, new Drive for Drive 1 enter /dev/sda and for 2 Drive enter /dev/sdb
read DRIVE
echo "Drive is $DRIVE"
if [ $DRIVE = "/dev/sdb" ];then
{/sbin/sfdisk -d /dev/sda > $DRIVE.out
/sbin/sfdisk $DRIVE < $DRIVE.out}
else
{/sbin/sfdisk -d /dev/sdb > $DRIVE.out
/sbin/sfdisk $DRIVE < $DRIVE.out}
fi
/sbin/mdadm /dev/md0 --add ${DRIVE}6
/sbin/mdadm /dev/md1 --add ${DRIVE}2
/sbin/mdadm /dev/md2 --add ${DRIVE}8
/sbin/mdadm /dev/md3 --add ${DRIVE}5
/sbin/mdadm /dev/md4 --add ${DRIVE}3
/sbin/mdadm /dev/md5 --add ${DRIVE}7
/sbin/mdadm /dev/md6 --add ${DRIVE}1
it add the second disk in my case and add all the new disk with same partitions as we have with old raid and Raid is then resync too. i make /boot as raid , / , /usr , swap all are raid md's . Now when i boot from 2 disk it wont boot . what to do any idea . iTs really urgrent to do . Your help is highly appriciated.
Regards
On 4/15/06, Dan Carpenter <error27@xxxxxxxxx> wrote:
On 4/14/06, Koree A. Smith <koreesmith@xxxxxxxxx> wrote:
> Hmm. I helped create a rather large system that does completely
> automated and unattended installs without rebuilding anaconda. What
> does one gain from doing so?
>
> Koree
>
You're right of course. The network route is the correct way to go in
many cases.
My way is still kind of useful if you need a network driver disk and
so you can't get it over the network... Etc. I have a bunch of
configs like that so I eventually end up patching anaconda for each
new redhat release.
Plus the subject was about putting the drivers in the initrd and I was
trying to spread some anaconda-recompiling-joy. ;P
regards,
dan carpenter
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
