With Centos3, fedora1/2 I have been able to put /boot on a RAID1 partition and have it boot normally. Unlike earlier versions that used lilo as the default boot loader, these did not make the 2nd drive bootable but at least I was fairly confident that if the first drive failed I could use the install CD in rescue mode to fix up the 2nd one and go on. However, Centos4 won't boot at all with a similar install attempt and running grub-install in rescue mode gives an error about not being able to find the bios drives. Is there a howto somewhere to work around this problem? -- Les Mikesell les at futuresource.com
My mainboard have SATA Raid function (sata_sil). I want to create software raid on Centos 4, but I can't see mkraid packeage. How would I create software raid 0 on centos 4. Thanks.
On Tue, 05 Apr 2005 13:15:25 -0500, Les Mikesell <lesmikesell at gmail.com> wrote:> With Centos3, fedora1/2 I have been able to put /boot on a RAID1 > partition and have it boot normally. Unlike earlier versions that > used lilo as the default boot loader, these did not make the 2nd drive > bootable but at least I was fairly confident that if the first drive > failed I could use the install CD in rescue mode to fix up the 2nd one > and go on. However, Centos4 won't boot at all with a similar install > attempt and running grub-install in rescue mode gives an error about not > being able to find the bios drives. Is there a howto somewhere to work > around this problem?This is an infamous grub-on-sw-raid problem. I run this script after installing the OS on the new system (and after grub upgrades, it used to fix flipping md5sums in Tripwire reports for me): #!/bin/sh # # Update MBR on both mirror drives # (grub/swraid has problems updating the slave, # as of RHEL3) # Should be run after grub rpm updates as well # # By Alex Tkachenko <alex at ingrian.com> ADMINDIR=/root/admin BOOT_ARRAY=`df /boot | awk '/dev/{print $1}'` # Select only active disks (skip spares) DISKS=`mdadm --query --detail /dev/md0 | awk '/active sync/{print $7}'| sed ' s@/dev/@@g s/,/ /g s/[0-9]//g '` for d in $DISKS do cat <<EOF | /sbin/grub --batch device (hd0) /dev/$d root (hd0,0) setup (hd0) quit EOF # Save updated mbr dd if=/dev/$d of=$ADMINDIR/mbr.$d count=1 done Take care, Alex> > -- > Les Mikesell > les at futuresource.com > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > >
Les Mikesell wrote:> With Centos3, fedora1/2 I have been able to put /boot on a RAID1 > partition and have it boot normally. Unlike earlier versions that > used lilo as the default boot loader, these did not make the 2nd drive > bootable but at least I was fairly confident that if the first drive > failed I could use the install CD in rescue mode to fix up the 2nd one > and go on. However, Centos4 won't boot at all with a similar install > attempt and running grub-install in rescue mode gives an error about not > being able to find the bios drives. Is there a howto somewhere to work > around this problem?If you are used to LILO, it still exist in CentOS4, but isn't the default boot loader. You can specify it during the installation, or you can remove grub and install LILO later on. It handles /boot on RAID1 automatically. If you want to continue using Grub, this post from Fedora mailing list might be helpfull: https://www.redhat.com/archives/fedora-list/2005-March/msg05935.html -- Aleksandar Milivojevic <amilivojevic at pbl.ca> Pollard Banknote Limited Systems Administrator 1499 Buffalo Place Tel: (204) 474-2323 ext 276 Winnipeg, MB R3T 1L7