Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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 have installed a a second hard drive on a PC that already has WinXP installed. I then installed Fedora Core 2 on the new hd. I want the two OSes to dual boot. I have done this before and had problems when GRUB was installed to the MBR. Windows does NOT like that situation. So, today, when the FC2 installer asked about installing a boot loader I told it not to. Later I came back and manually installed GRUB in the /boot partition (hdb1) on the Linux hd. After GRUB was installed and its menu.lst file configured (see below) I created a soft link to menu.lst named grub.conf. Then I used dd to copy the first 512 bytes of the /boot partition to a file to be used to chain the windows boot loader to GRUB. I put that file on a floppy, and rebooted to windows and copied the file into the C: directory and configured c:\boot.ini with a new entry pointing to that file.
So, I went out of my way to be nice to Windows, and Windows is happy. Boots correctly every time. But, Linux is not happy. It will only boot from either the boot floppy that I made or from the FC2 Rescue CD. It will not boot from the hard drive /boot partition. When I boot from the hard drive the Windows boot menu comes up correctly and displays the two choices for Windows XP and Linux. If I select Linux, "GRUB", without the quotes, is printed to the top of a blank screen and nothing else ever happens.
Here are the answers to the questions that I believe readers of this entry will ask.
The "fdisk -l /dev/hdb" command gives,
Disk /dev/hdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 83 Linux
/dev/hdb2 14 778 6144862+ 83 Linux
/dev/hdb3 779 3328 20482875 83 Linux
/dev/hdb4 3329 9729 51416032+ f W95 Ext'd (LBA)
/dev/hdb5 3329 4603 10241406 83 Linux
/dev/hdb6 4604 4730 1020096 83 Linux
/dev/hdb7 4731 4857 1020096 82 Linux swap
/dev/hdb8 4858 4921 514048+ 83 Linux
The "mount" command gives,
/dev/hdb2 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/hdb1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/hdb3 on /home type ext3 (rw)
/dev/hdb8 on /tmp type ext3 (rw)
/dev/hdb5 on /usr type ext3 (rw)
/dev/hdb6 on /var type ext3 (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
GRUB was installed to /boot with the command,
grub-install /dev/hdb1
The /boot/grub/grub.conf file has these contents,
# 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/hda2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd1,0)/grub/splash.xpm.gz
title Fedora Core (2.6.5-1.358)
root (hd1,0)
kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.5-1.358.img
The command used to copy the first 512 bytes of the /boot partition was,
dd if=/dev/hdb1 of=linuxbootsect bs=512 count=1
I then copied the linuxbootsect to the floppy and rebooted to Windows where linuxbootsect was copied to c:\linuxbootsect and the c:\boot.ini was modified to look like this:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
c:\linuxbootsect="Linux"
Selecting the "Microsoft Windows XP Home Edition" selection from the Windows boot menu boots Windows just fine. Selecting the "Linux" selection results in "GRUB" printed at the top of the screen and nothing further happening.
Can anyone suggest what I have forgotten to do or have done wrong.
#boot=/dev/hda
default=2
timeout=10
splashimage=(hd0,5)/boot/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-28.7smp)
root (hd0,5)
kernel /boot/vmlinuz-2.4.20-28.7smp ro root=/dev/hda6 hdb=ide-scsi
initrd /boot/initrd-2.4.20-28.7smp.img
I think but I'm not sure that root=LABEL as you have should point to your partition.
root=/dev/hda6 hdb=ide-scsi
here mine is hda6
the first entry has LABEL=/ and is the / partition.
Since my first entry and in response to readings from the GRUB info pages, I changed that line as follows:
kernel /vmlinuz-2.6.5-1.358 ro root=/dev/hdb2
which is more along the lines of your entry and uses the actual device name instead of the LABEL. This had no affect. The boot still operates the same.
This is of interest to me, because I have a problem a bit different from the previous but Grub bootloader messed up my pc or sumthin'. When I try to boot, all I get is
GRUB_
I can't type in anything, all I see is grub and a flashing line ( _ ).
Hope someone has an answer to this or a suggestion.
PEACE to all.
Yattara
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.