I recently had to fix my Fedora Core 1 installation after I had reloaded an image onto the same hardware but a slightly different hard drive. The symptom of my problem: When I booted, the word GRUB would appear in the top left corner and then nothing else would occur.

I found a helpful tidbit here to fix the problem:
networking.earthweb.com/netos/article.php/3344241

So here is what I did to fix this:
1. Booted off Fedora Core 1 CD.

2. At the boot screen, chose F5 - Rescue

3. At the next prompt screen, entered:
linux rescue

4. From other googled posts, I ran this to figure out what my drive looked like.
df
I noted that boot was under /mnt/sysimage/boot as were all my other partitions except for a root.old and a root. I also noted that they were all on /dev/hda - which I think equates to hd0 in step 8 below.

5. From other googled posts, next I tried this:
chroot /mnt/sysimage
That proceeeded to give me this error:
Segmentation fault

6. So I tried this instead:
cd /mnt/sysimage/sbin

7. Then I ran GRUB interactively:
grub

8. From the link I mentioned above - How to install grub without a floppy, I typed the following:
root (hd0,0)
setup (hd0)
Grub ran an install of itself and appeared to fix the load file. It ran this command for me.
install /grub/stage1 (hd0) (hd0)1+15 p (hd0,0)/grub/stage2 /grub/grub.conf
Once that was done, I entered in the quit command.
quit

9. Then I removed the CD & exited from rescue mode, exit.
It rebooted and this time instead of seeing GRUB display in the top left corner my system rebooted into the normal login screen.

I hope this helps someone.

A monsterous gobildeegoop of horrible problems I'm glad to see that you fixed!

Handled like a true pro! Guru status awaits!

I just wanted to add,

If you have a compaq array controller, entering (hd0) in grub will give you an error as well as (ida0).

What you have to do while in grub is enter the following:

device (hd0) /dev/ida/c0d0

Grub will then map hd0 to your array controller (hopefully). You may want to look at the df output to get this exactly right for your box.

And you can go on with the procedure outlined in the previous post.

I had to spend two hours googling to find this modification so I thought I should post it


Mike

If you want to repair a system which does not work after changing the partitions and you are faced with the grub program and your system does not boot.

use

find /boot/grub/stage1

this will give you a list of disks

now finish with
root (hdx,x)
setup (hdx)

Been there, done that (with RH9 and ghostcast version 7.5)

According to symantec's web site, ghosts earlier than 8.0 or 9.0 all have this problem with linux.

Also, according to their web site, if lilo is used instead of grub, you don't have this problem.

(but that parts not true, so I'm not sure if I believe them if we upgrad eif it would work or not.)

anyhow, in a pure linux environment, wouldn't dd be the better choice?

Kyle