[SOLVED] Can't enter SolusOS 1.7 entry on CentOS 6.3 grub menu
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't enter SolusOS 1.7 entry on CentOS 6.3 grub menu
Hi guys,
Just wondering, I installed CentOS onto my desktop that originally had SolusOS (debian based distro) on it so i could dual boot between the two. However it seems CentOS's grub has missed out the entry for Solus and i can't boot into it. So i opened up the grub.conf and added a new entry for it but the problem is that i'm guessing i need to enter the kernel path for solus such as the CentOS entries above but i'm stuck on how to do this so i can boot sucessfully to both Cent and Solus.
Is there a command to probe the solus installation in hd0,2 for the info to copy into the grub.conf?
Here is the output of grub.conf and my crappy attempt to add Solus at the bottom;
Code:
# 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,5)
# kernel /boot/vmlinuz-version ro root=/dev/sdb6
# initrd /boot/initrd-[generic-]version.img
#boot=/dev/sdb
default=0
timeout=5
splashimage=(hd0,5)/boot/grub/splash.xpm.gz
#hiddenmenu
title CentOS (2.6.32-279.14.1.el6.i686)
root (hd0,5)
kernel /boot/vmlinuz-2.6.32-279.14.1.el6.i686 ro root=UUID=5fb797a4-5a54-42ad-888a-49f80300bb73 rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=uk LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_LVM rd_NO_DM rhgb quiet
initrd /boot/initramfs-2.6.32-279.14.1.el6.i686.img
title CentOS (2.6.32-279.el6.i686)
root (hd0,5)
kernel /boot/vmlinuz-2.6.32-279.el6.i686 ro root=UUID=5fb797a4-5a54-42ad-888a-49f80300bb73 rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=uk LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_LVM rd_NO_DM rhgb quiet
initrd /boot/initramfs-2.6.32-279.el6.i686.img
title SolusOS
root (hd0,2)
chainloader +1
If you are certain that you didn't install CentOS over Solus, then you should run "/usr/sbin/update-grub2 -o /boot/grub/grub.cfg" (as root, and without the quotes) to probe for bootable OSs and rewrite the grub.cfg file.
It may also work by simply running /usr/sbin/update-grub2.
Nice one i'll give that command a shot. I'm positive i haven't overwritten solus because i've got it partitioned that cent's / is hda0,5 and the /home is hda0,6 with solus and the swap etc at the beginning. I'll report back later with the results (fingers crossed)
The Grub file you posted (grub.conf) is from Grub Legacy so updating grub2 isn't going to help. The chainloader entry you have in the grub.conf for Solus should work if your Solus boot files are on the first drive, third partition. It would probably be best to boot CentOS and mount the partition(s) you think Solus boot files are on to make sure you are pointing to the correct partition/files.
I'm getting an Error13: Invalid or unsupported executable format. Googling this says it basically can't find the kernel image, is that right? Would installing grub2 fix this issue or is there a more recommended solution i could try?
Error13: Invalid or unsupported executable format.
You might have your Solus entry pointing to the swap partition, that is, if CentOS and Solus are the only operating systems you have. I would suggest going to the site below and reading the information on the bootinfoscript, downloading it and running it. It will produce a file named results.txt in your user /home directory. Review it and if you can't figure it out, post the file here.
The bootinfoscript shows Solus and its boot files are on sdc2. Grub Legacy counts drives and partitions from zero (0) while Grub2 counts drives from zero (0) and partitions fro one (1). Change the entry in the grub.conf file for Solus to:
Quote:
title SolusOS
root (hd0,1)
chainloader +1
Or you could use this:
Quote:
title SolusOS
root (hd0,1)
kernel /boot/grub/core.img
#savedefault
#boot
The savedefault and boot lines above will not be read as they have the hash mark (#), if that fails you could remove the hash mark. Some systems require them, others don't.
What I find curious about your system is that you seem to have only one drive yet it is labelled as sdc?
Did you have other drives attached during the installation?
Are you able to boot CentOS with the entry you have in its grub.conf file?
Normally, booting sdc6 would require a root entry for Grub of (hd2,5) and for Solus (hd2,1)??
title SolusOS
root (hd0,1)
kernel /boot/grub/core.img
#savedefault
#boot
worked a treat! It brought up the solus grub menu which in turn booted into SolusOS. I think the partitions where showing as sdc because i had a usb flash drive and usb hard drive plugged in and somehow labeled the system partitions up a bit. It shows as sdb when just one of them was plugged in and with none its sda.
Thanks for that by the way Yancek, you were very helpful I appreciate it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.