To test CentOS 5, I loaded from DVD adding it to a system at home running Fedora Core 7 T2.
Partition Layout is: /dev/hda1 - / for the RH7T2 system /dev/hda2 - /home /dev/hda3 - swap /dev/hda4 - extended /dev/hda5 - / for CentOS 5
The system loaded cleanly and gave me the opportunity to tell grub about the other system. CentOS boots fine. Grub Stage 2 will show me both systems.
However, If I choose the FC7T2 system I get the following output: --------------------------------------------------------- Booting 'FC7T2'
rootnoverify(hd0,0) chainloader +1
Error 13: Invalid or unsupported executable format --------------------------------------------------------- The CentOS grub.conf on /dev/hda5 looks like:
#: 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 do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,4) # kernel /boot/vmlinuz-version ro root=/dev/hda5 # initrd /boot/initrd-version.img #boot=/dev/hda default=0 timeout=10 splashimage=(hd0,4)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-1.2747.el5) root (hd0,4) kernel /boot/vmlinuz-2.6.18-1.2747.el5 ro root=LABEL=/1 quiet crashkernel=64M@16M initrd /boot/initrd-2.6.18-1.2747.el5.img title FC7T2 rootnoverify (hd0,0) chainloader +1
--------------------------------------------------------- Any clues on how to fix this? Note, I am posting to both groups since I follow both and cannot figure out which is the better choice.
Seems the grub that centos-5 installed didn't quite manage to get your fc7t2 boot option right, see details inline below.
On Thursday 15 March 2007, Styma, Robert E (Robert) wrote:
To test CentOS 5, I loaded from DVD adding it to a system at home running Fedora Core 7 T2.
Partition Layout is: /dev/hda1 - / for the RH7T2 system /dev/hda2 - /home /dev/hda3 - swap /dev/hda4 - extended /dev/hda5 - / for CentOS 5
...
The CentOS grub.conf on /dev/hda5 looks like:
...
title FC7T2 rootnoverify (hd0,0) chainloader +1
This piece of grub config is not right for your FC7T2 install. It assumes that there is a 2nd boot-loader living on /dev/hda1 (hd0,0 in grub speak). Change it to something more like (you'll have to find the exact names and paths yourself):
title FC7T2 root (hd0,0) kernel /boot/vmlinux...fc7 ro root= ... initrd /boot/initrd-...img
good luck, Peter
Styma, Robert E (Robert) wrote:
To test CentOS 5, I loaded from DVD adding it to a system at home running Fedora Core 7 T2.
Partition Layout is: /dev/hda1 - / for the RH7T2 system /dev/hda2 - /home /dev/hda3 - swap /dev/hda4 - extended /dev/hda5 - / for CentOS 5
The system loaded cleanly and gave me the opportunity to tell grub about the other system. CentOS boots fine. Grub Stage 2 will show me both systems.
Each system should have its own grub. You cannot properly install new kernels and have the grub menu updated properly otherwise.
At one time I had, on one box, RHEL5 beta1 client and server, SLED, OpenSUSE, maybe something else. One grub menu would have bene horrendous.
The guys on the Fedora list had good suggestions. One pointed me to the correct documentation:
http://www.gnu.org/software/grub/manual/grub.html section 14.3 for the error message
For the record, the solution I got to work was to boot the system and at the grub stage2 countdown to boot press enter. I pressed 'c' to get the grub prompt. Then I entered the commands root (hd0,0) setup (hd0,0)
This installed the boot loader in the /dev/hda1 partition. Note that the partition numbers in grub are zero based while in /dev they are 1 based.
I can now boot both systems. I have them sharing the same /home and swap directories.
Bob Styma
-
John Summerfield -
Peter Kjellstrom -
Styma, Robert E (Robert)