On 04/29/2009 08:00 PM, Phil Schaffner wrote: > JohnS wrote: > ... > >> I wonder also why ?? >> > > Then you should read Ned's earlier reply to the same message this one is > in reply to, or have a careful look at the current version of the page. > > http://wiki.centos.org/HowTos/SoftwareRAIDonCentOS5 On my systems I also create a second entry in grub.conf, configured for booting from the second disk. [root at xenh2 ~]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/md0 # initrd /initrd-version.img #boot=/dev/sda default=0 fallback=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu title CentOS (2.6.18-128.1.6.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-128.1.6.el5 module /vmlinuz-2.6.18-128.1.6.el5xen ro root=/dev/md0 panic=45 module /initrd-2.6.18-128.1.6.el5xen.img title CentOS (2.6.18-128.1.6.el5xen disc2) root (hd1,0) kernel /xen.gz-2.6.18-128.1.6.el5 module /vmlinuz-2.6.18-128.1.6.el5xen ro root=/dev/md0 panic=45 module /initrd-2.6.18-128.1.6.el5xen.img [root at xenh2 ~]# cat /boot/grub/device.map # this device map was generated by anaconda (hd0) /dev/sda (hd1) /dev/sdb
