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.
I'm trying to configure a dual-boot machine, 2 SATA drives. Sda contains WindowsXP. Sdb has Centos. The bios has boot option where one can boot from either hard drive.
The computer folks here really like XP, and have the ability to push out new XP images at any time. Therefore, Linux must be on sdb, and the bootloader for linux must also reside on the same drive (or when they push out a new XP image, they'll reformat sda, and destroy the linux bootloader there).
Ok, so I think I've explained why I need the bootloader on sdb.
So here's what's going on. Grub won't show it's menu. When I select to boot drive 2, it simply takes me to the grub command line. From there, I can type in the following:
You might notice that I'm using hd0, when Linux resides on sdb. When I try to tell grub to use (hd1,0) , it complains about the partition type. It appears that grub(or the bios) is perhaps switching hd0/hd1? However, it is still referred to as /dev/sdbX correctly.
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 (hd1,0)
# kernel /vmlinuz-version ro root=/dev/sdb2
# initrd /initrd-version.img
#boot=/dev/sdb1
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,641
Rep:
I had the same problem with my Linux partitions on sda and two IDE harddisks set prior in boot order by the BIOS. I have to admit I didn't try too long, but I didn't get it to work. It seemed that GRUB indeed saw my sda (put first in boot order) as hd(0) when booting but after booting as hd(2).
There might be a way by changing /boot/grub/devices.map but I did not want to try it and ended up with restoring the "original" boot sequence and install the GRUB loader to hda. If you had the possibility to boot from floppy or even better an USB stick that might make it much easier I guess.
Oh, and sometimes, the splashimage causes problems. try commenting it out
I added the boot lines, commented out the splashimage, and added the map command...and the menu still does not show up. It only takes me to the grub command prompt.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.