To My Saviors...
Whenever I have had problems in the past they have been solved here. Hopefully, this will not be the exception. On with the story...
After Fedora Core 2 (FC2) install, the GRUB boot loader does not come up after system reboot. Instead, all I get is a black screen with the word 'GRUB' in the upper left corner, along with a blinking cursor that is non-responsive. The only key sequence that works is ctrl+alt+del, which allows me to reboot but has the same result. Note: there were absolutely NO warning/error messages during the FC2 installation.
I have a Dell PC with Windows XP installed on /dev/hda. I would like to run a dual boot system with Fedora Core 2 (FC2) installed on a separate harddrive. I installed an 80GB Maxtor as a slave drive. Mounted it in one of the 5.25" media bays and hooked it up with the IDE connector in between the mother board and my CD+RW drive. Booted into XP to ensure that the new drive was recognized...it was.
I have a 100MB Zip drive connected via IDE (same ribbon as XP hard drive), the XP drive connected via IDE, a CD+RW drive connected via IDE (same ribbon as FC2 drive), and the newest FC2 drive on an IDE cable.
Begin FC2 Install:
Shut the system down and booted from FC2 disk 1 to start the installation on the new harddrive. Anaconda started, went through the introductory steps about language and whatnot. When it came to the partitioning options, I chose to let FC2 partition the new drive on its own but opted to verify the partitions in Disk Druid. Anaconda correctly identified my XP drive as /dev/hda (I chose to leave it alone since it is already a working install) and the new 80GB drive as /dev/hdd. I suppose it chose /hdd instead of /hdb because I have two other IDE drives installed in addition to the /hda for XP?
FC2 partitioned the new hard drive (and left /hda alone....thank goodness!) in the following manner:
/hdd1 /boot ext3 100MB
/hdd2 / ext3 77.8GB
/hdd3 swap 1024MB
I chose to use the GRUB boot loader offered by FC2 simply because I use it on my dual boot systems at work and am very comfortable with it. The GRUB configuration detected/listed both drives as:
Fedora Core 2 /dev/hdd
and I opted to use FC2 as the default.
Fedora Core 2 ran through all 4 disks with absolutely no error/warning messages and prompted me to remove all media and reboot the system. Upon reboot, however, the GRUB boot loader interface does not appear. Instead, I get a blank screen that just says 'GRUB' along with a blinking cursor that is non-responsive.
Okay, so somewhere in my two-hour Google search last night I stumbled upon some guidance that suggested I install GRUB on the MBR (master boot record). Here's the link if anyone is interested:
Installing GRUB on the MBR
I rebooted my machine with the FC2 disk and entered the 'linux rescue' mode. I followed the steps outlined in the link above:
> chroot /mnt/sysimage
...Brings up GRUB
grub> find /boot/grub/stage1
Uh-oh...there is no stage1 in /boot/grub. It looks like GRUB didn't properly install itself?
There is, also, another problem that I see in the grub.conf file: under the Fedora Core entry, it has the following line: root (hd1,0). If FC2 recognizes the new harddrive as /hdd and the /boot partition was mounted to /hdd1, then this entry should be changed to read: root (hd3,0)...correct??? This could be a problem but more than likely is not causing the boot loader malfunction...correct???
My only option is to get the GRUB boot loader to work. Any ideas???
P.S. Sorry about the lengthy post, but I know how people like specifics. If I had access to the current grub.conf or menu.lst files, I would have posted them as well.