Stupid question (I'm guessing). I'm currently tri-booting (or would like to be) VectorLinux 6 Deluxe, CentOS 5.5 and an evaluation copy of Red Hat 6. I'm using CentOS's grub. VectorLinux and CentOS boot fine, but Red Hat won't load. I think I read somewhere that CentOS's grub is too old for ext3, 256 (something or others).
So, is it possible to download and install a newer version of grub for CentOS 5.5? (This has been a problem with other tri-boot attempts). If not, is their a way to boot Red Hat from the install DVD? Since it's only a 30 day evaluation, booting from DVD or CD would be fine, but I don't see the option.
Thanks for any pointers.
On 03/01/11 07:23, Ron Blizzard wrote:
You don't need to upgrade grub, I'm quite happily dual booting rhel6 GA on a CentOS-5 system (using C-5 GRUB).
Only thing I did differently is the rhel6 /boot partition is mounted on an ext3 partition whereas I _think_ the default might be ext4 which, as a wild guess, is probably unsupported by CentOS-5 GRUB ?
The rest of the system is quite happily sitting in an ext4 partition using md raid on lvm.
On Mon, Jan 3, 2011 at 4:15 AM, Ned Slider ned@unixmail.co.uk wrote:
Hi Nick,
Thanks for writing back. I'm using ext3 also. Is it possible to see your RHEL 6 grub entry? Did you install grub on the RHEL boot partition and use a chainloader, or were able to just do a normal entry?
Again,t hanks for any ponters.
On 03/01/11 10:37, Ron Blizzard wrote:
Yes, I installed rhel6's grub to the rhel6 /boot partition during the rhel6 installation and then added a chainloader entry to the end of the CentOS-5 /boot/grub/grub.conf to boot rhel6:
title RHEL6 Buildsys rootnoverify (hd0) root (hd0,1) chainloader +1
Adjust to suit your partitioning scheme :-)
On Mon, Jan 3, 2011 at 5:09 AM, Ned Slider ned@unixmail.co.uk wrote:
Thanks. I'm guessing that's my problem. Red Hat installed grub to the MBR, then I overwrote it with the CentOS grub. So there's nothing to "chainload" on the partition.
I'll fix it and report back. Again, thanks.
On Mon, Jan 3, 2011 at 5:09 AM, Ned Slider ned@unixmail.co.uk wrote:
That's all it needed. Thanks. Writing from Red Hat now. Would have been here sooner, except SELinux did a "relabel" -- whatever that is. Probably didn't like me messing with grub. I thought I could do a "normal" Linux grub entry (like CentOS) but I got an grub error number 2 when I tried that (13 with the chainloader, which makes sense since I didn't have grub there). I'll use the chainloader from now on when I tri-boot.
Thanks very much.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/03/2011 06:42 AM, Ron Blizzard wrote:
If you boot a machine with SELinux disabled and then renenable it, the init scripts will relabel the machine.