Grub install broken after kernel update

[Pierrette Barbaresco]

Hello,

We updated smp kernel on a Sun V20Z AMD Opteron Scsi device.
After installation we tried grub-install /dev/sda and we got

/sbin/grub-install: line 475: 4041 Segmentation fault

[root@cict-009 ~]# uname -a
Linux cict-009.toulouse.grid5000.fr 2.6.10-1.741_FC3smp #1 SMP Thu Jan 13 16:58:29 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
[root@cict-009 ~]# grub-install /dev/sda
/sbin/grub-install: line 475:  4041 Segmentation fault      $grub_shell --batch $no_floppy --device-map=$device_map  >$log_file <<EOF
root $root_drive
setup $force_lba --stage2=$grubdir/stage2 --prefix=$grub_prefix $install_drive
quit
EOF

Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

# this device map was generated by anaconda
(fd0)     /dev/fd0
(hd0)     /dev/sda

Any idea.

Regards

[Jonathan Berry]

On Fri, 28 Jan 2005 18:21:44 +0100 (MET), Pierrette Barbaresco
 wrote:
> Hello,
>
> We updated smp kernel on a Sun V20Z AMD Opteron Scsi device.
> After installation we tried grub-install /dev/sda and we got
>
> /sbin/grub-install: line 475: 4041 Segmentation fault
>
> [root@cict-009 ~]# uname -a
> Linux cict-009.toulouse.grid5000.fr 2.6.10-1.741_FC3smp #1 SMP Thu Jan 13 16:58:29 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
> [root@cict-009 ~]# grub-install /dev/sda
> /sbin/grub-install: line 475:  4041 Segmentation fault      $grub_shell --batch $no_floppy --device-map=$device_map  >$log_file <<EOF
> root $root_drive
> setup $force_lba --stage2=$grubdir/stage2 --prefix=$grub_prefix $install_drive
> quit
> EOF
>
> Installation finished. No error reported.
> This is the contents of the device map /boot/grub/device.map.
> Check if this is correct or not. If any of the lines is incorrect,
> fix it and re-run the script `grub-install'.
>
> # this device map was generated by anaconda
> (fd0)     /dev/fd0
> (hd0)     /dev/sda
>
> Any idea.

No, not really.  But why are you running grub-install?  You do not
have to re-install GRUB after every kernel update like you do for
LILO.  The configuration file only needs to be updated, which is done
automatically by rpm when you install a kernel.  You should only run
grub-install again if somehow your MBR gets corrupted and your machine
won't boot (you have to boot with the recovery CD).
Back to your question, you can always try running the grub shell and
typing in the commands and see what happens.  Of course, you'll have
to figure out what each of the variables would be.  You can also check
the log file; look for it under /tmp/

Jonathan

[Phil Schaffner]

On Fri, 2005-01-28 at 18:21 +0100, Pierrette Barbaresco wrote:
> Hello,
>
> We updated smp kernel on a Sun V20Z AMD Opteron Scsi device.
> After installation we tried grub-install /dev/sda and we got
>
> /sbin/grub-install: line 475: 4041 Segmentation fault
>
> [root@cict-009 ~]# uname -a
> Linux cict-009.toulouse.grid5000.fr 2.6.10-1.741_FC3smp #1 SMP Thu Jan 13 16:58:29 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
> [root@cict-009 ~]# grub-install /dev/sda
> /sbin/grub-install: line 475:  4041 Segmentation fault      $grub_shell --batch $no_floppy --device-map=$device_map  >$log_file <<EOF
> root $root_drive
> setup $force_lba --stage2=$grubdir/stage2 --prefix=$grub_prefix $install_drive
> quit
> EOF
>
> Installation finished. No error reported.
> This is the contents of the device map /boot/grub/device.map.
> Check if this is correct or not. If any of the lines is incorrect,
> fix it and re-run the script `grub-install'.
>
> # this device map was generated by anaconda
> (fd0)     /dev/fd0
> (hd0)     /dev/sda
>
> Any idea.

Ran into the same problem. Installed a new SATA disk on an x86_64
system, copied/configured/booted FC3 installation, and attempted to
reconfigure grub to use the new /boot partition.  Attempting to run grub
or grub-install to update boot record results in "Segmentation fault".
The old MBR is not changed.  Not sure what kernel update may have to do
with it.  Behavior is the same for at least the last 3 kernels tried.

See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=147600

Phil

[Guy Fraser]

On Wed, 2005-09-02 at 13:00 -0500, Phil Schaffner wrote:
> On Fri, 2005-01-28 at 18:21 +0100, Pierrette Barbaresco wrote:
> > Hello,
> >
> > We updated smp kernel on a Sun V20Z AMD Opteron Scsi device.
> > After installation we tried grub-install /dev/sda and we got
> >
> > /sbin/grub-install: line 475: 4041 Segmentation fault
> >
> > [root@cict-009 ~]# uname -a
> > Linux cict-009.toulouse.grid5000.fr 2.6.10-1.741_FC3smp #1 SMP Thu Jan 13 16:58:29 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
> > [root@cict-009 ~]# grub-install /dev/sda
> > /sbin/grub-install: line 475:  4041 Segmentation fault      $grub_shell --batch $no_floppy --device-map=$device_map  >$log_file <<EOF
> > root $root_drive
> > setup $force_lba --stage2=$grubdir/stage2 --prefix=$grub_prefix $install_drive
> > quit
> > EOF
> >
> > Installation finished. No error reported.
> > This is the contents of the device map /boot/grub/device.map.
> > Check if this is correct or not. If any of the lines is incorrect,
> > fix it and re-run the script `grub-install'.
> >
> > # this device map was generated by anaconda
> > (fd0)     /dev/fd0
> > (hd0)     /dev/sda
> >
> > Any idea.
>
> Ran into the same problem. Installed a new SATA disk on an x86_64
> system, copied/configured/booted FC3 installation, and attempted to
> reconfigure grub to use the new /boot partition.  Attempting to run grub
> or grub-install to update boot record results in "Segmentation fault".
> The old MBR is not changed.  Not sure what kernel update may have to do
> with it.  Behavior is the same for at least the last 3 kernels tried.
>
> See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=147600
>
> Phil

Yup, Grub sucks.

I just installed a third SATA drive and can now only get into my 
machine with a rescue disk.

I have read and tried a dozen 'fixes', but now the best I can get 
is "Read Error".

Every time a new PATA or SATA drive is changed, grub breaks and 
the only way I have ever been able to get it going again is to 
reinstall, changing the drive order in the advanced section of 
boot setup.

Many variations of these methods have been tried :

###Initial device.map ###
(fd0) /dev/fd0
(hd0) /dev/hde
(hd1) /dev/hdg
(hd2) /dev/hdh
(hd3) /dev/sda
(hd4) /dev/sdb
(hd5) /dev/sdc
###

Change device.map :
###
(fd0) /dev/fd0
(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/sdc
(hd3) /dev/hde
(hd4) /dev/hdg
(hd5) /dev/hdh
###

Now /boot/grub/grub.conf matches the device list again.

--
# grub-install /dev/sda

Result = Grub all over the screen until crash.

--
# grub-install --recheck /dev/sda

Result = Resets device map to initial map, and machine 
does not even enter grub after reboot.

--
Edit /boot/grub/grub.conf to match device map.

# grub-install /dev/sda

Result = Read Error

--
Once in rescue mode, enter grub:

# root (hd3,0)
# setup (hd3)
# quit

Result = Read Error

--

I tried many different variants of editing device.map 
and grub.conf, using grub-install and grub console 
without success. I have made sure (hd3) was the correct 
by using the auto completion feature of the device 
command to see the partition list of the device.

What is the install wizard doing to make the system 
work in the first place?

I have already backed up my up2date, etc and data 
directories and will probably just reinstall wiping out 
the base system and redo the updates.

Syslinux and LILO may be feature poor, but they were 
easy to use and reliable.

Any chance FC4 will reinstate LILO as an optional boot 
loader?

If I can't figure it out, this will be the third time 
I will have had to reinstall after changing drives in 
FC3.

[Rahul Sundaram]

HI
> Syslinux and LILO may be feature poor, but they were
> easy to use and reliable.

grub has no reliability concerns really. your problem may not been
even related to it. if you think its a grub bug then file a bug
report.
> Any chance FC4 will reinstate LILO as an optional boot
> loader?

no

Regards,
Rahul Sundaram

On Sat, Feb 12, 2005 at 06:55:18PM +0530, Rahul Sundaram wrote:
> HI
> > Syslinux and LILO may be feature poor, but they were
> > easy to use and reliable.
>
> grub has no reliability concerns really. your problem may not been
> even related to it. if you think its a grub bug then file a bug
> report.
> > Any chance FC4 will reinstate LILO as an optional boot
> > loader?

I missed the original question but if you are having a problem with
grub-install (although I am not sure why you ned to do that after
installing a new kernel ) ttry this instead of grub install:
grub
grub> root (hd0,0)
grub> setup (hd0)
grub> quit

Of course change the hd0 clauses as needed.

[Guy Fraser]

On Sat, 2005-12-02 at 08:22 -0600, [e-mail] wrote:
> On Sat, Feb 12, 2005 at 06:55:18PM +0530, Rahul Sundaram wrote:
> > HI
> > > Syslinux and LILO may be feature poor, but they were
> > > easy to use and reliable.
> >
> > grub has no reliability concerns really. your problem may not been
> > even related to it. if you think its a grub bug then file a bug
> > report.
> > > Any chance FC4 will reinstate LILO as an optional boot
> > > loader?
>
> I missed the original question but if you are having a problem with
> grub-install (although I am not sure why you ned to do that after
> installing a new kernel ) ttry this instead of grub install:
> grub
> grub> root (hd0,0)
> grub> setup (hd0)
> grub> quit
> Of course change the hd0 clauses as needed.
>
> =======================================================================
> "You who hate the Jews so, why did you adopt their religion?"
> -- Friedrich Nietzsche, addressing anti-semitic Christians
>
> Aaron Konstam
> Computer Science
> Trinity University
> One Trinity Place.
> San Antonio, TX 78212-7200
>
> telephone: [phone]
> email:[e-mail]

Yes I did that, and dozens of other things.

[Guy Fraser]

On Sat, 2005-12-02 at 18:55 +0530, Rahul Sundaram wrote:
> HI
> > Syslinux and LILO may be feature poor, but they were
> > easy to use and reliable.
>
> grub has no reliability concerns really. your problem may not been
> even related to it. if you think its a grub bug then file a bug
> report.
> > Any chance FC4 will reinstate LILO as an optional boot
> > loader?
>
> no
>
> Regards,
> Rahul Sundaram

All I did was add a drive, and grub would not work any more.
Saying grub has nothing to do with it is complete BULL SHIT.

The sheer volume of people that are having problems with 
grub, should be an indicator that it is not making life 
easier for the Fedora community.

I ended up having to re-install on a PATA drive to get 
FC3 working again.

Rahul : If you don't have something that can help me, then 
do not respond. I have probably been using Linux longer than 
you, until grub and SATA drives came out I never had problems 
I could not fix. If you are a Red Hat developer then, I 
certainly hope the other developers are reading your idiotic 
remarks and have you removed.

Regards,
Guy Fraser

[Rahul Sundaram]

Hi
> All I did was add a drive, and grub would not work any more.
> Saying grub has nothing to do with it is complete BULL SHIT.

i said it might not be related.
> The sheer volume of people that are having problems with
> grub, should be an indicator that it is not making life
> easier for the Fedora community.

i dont agree with this
> Rahul : If you don't have something that can help me, then
> do not respond. I have probably been using Linux longer than
> you, until grub and SATA drives came out I never had problems
> I could not fix. If you are a Red Hat developer then, I
> certainly hope the other developers are reading your idiotic
> remarks and have you removed.

name calling wont help you. if I get removed for suggesting you file
bug reports against grub instead of ranting here then that would be
very ironic

[Guy Fraser]

On Tue, 2005-15-02 at 00:31 +0530, Rahul Sundaram wrote:
> Hi
> > All I did was add a drive, and grub would not work any more.
> > Saying grub has nothing to do with it is complete BULL SHIT.
>
> i said it might not be related.

Actually you said :
<QUOTE>
> grub has no reliability concerns really. your problem may not been
> even related to it. if you think its a grub bug then file a bug
> report.

</QUOTE>

Since it is difficult to figure out exactly what you were trying 
to say, I could only guess that the message appeared to say grub is 
not the problem.
> > The sheer volume of people that are having problems with
> > grub, should be an indicator that it is not making life
> > easier for the Fedora community.
>
> i dont agree with this

Whether you agree or not, many people are having trouble with 
the way grub handles drive assignments, and is one of the 
main reasons for attrition from FC.
> > Rahul : If you don't have something that can help me, then
> > do not respond. I have probably been using Linux longer than
> > you, until grub and SATA drives came out I never had problems
> > I could not fix. If you are a Red Hat developer then, I
> > certainly hope the other developers are reading your idiotic
> > remarks and have you removed.
>
> name calling wont help you. if I get removed for suggesting you file
> bug reports against grub instead of ranting here then that would be
> very ironic

Did I hurt your feelings?
I'm so sorry.

There are dozens of bug reports, for exactly the same problem, none 
of them have answers, and many appeared to have been closed.

I booted off the rescue disk, then shuffled around my data so I 
could boot off a PATA drive, then reinstalled onto that drive.

I can now run FC3 again, and will not attempt to install onto a SATA 
drive again until I hear a bunch of success stories. Grub doesn't 
seem to be able to handle a mixture of drive types, and until it 
can there should be an alternate boot loader.
> -- 
> Regards,
> Rahul Sundaram

Guy Fraser

[Rahul Sundaram]

Hi
> Actually you said :
>
> <QUOTE>
> >
> > grub has no reliability concerns really. your problem may not been
> > even related to it. if you think its a grub bug then file a bug
> > report.
> </QUOTE>
>
> Since it is difficult to figure out exactly what you were trying
> to say, I could only guess that the message appeared to say grub is
> not the problem.

I meant exactly what I said. grub may not be related. there are other
issues like bios settings and numbering
> Whether you agree or not, many people are having trouble with
> the way grub handles drive assignments, and is one of the
> main reasons for attrition from FC.

this list presents a skewed view since people usually only post to
talk about issues. everything will seem like a pile of bugs usually
> >
>
> Did I hurt your feelings?
> I'm so sorry.

well calling my comments idiotic and then making a statement that I
should be removed is bound to do that. doesnt it?
> There are dozens of bug reports, for exactly the same problem, none
> of them have answers, and many appeared to have been closed.

you can post with the bugzilla numbers to the fedora devel list and
try engaging the developers in a discussion with your suggestions for
improvement. moving back to LILO is not really going to happen

[Jeff Vian]

On Mon, 2005-02-14 at 14:56 -0700, Guy Fraser wrote:
> On Tue, 2005-15-02 at 00:31 +0530, Rahul Sundaram wrote:
> > Hi
> > > All I did was add a drive, and grub would not work any more.
> > > Saying grub has nothing to do with it is complete BULL SHIT.
> >
> > i said it might not be related.
>
> Actually you said :
>
> <QUOTE>
> > 
> > grub has no reliability concerns really. your problem may not been
> > even related to it. if you think its a grub bug then file a bug
> > report.
> </QUOTE>
>
> Since it is difficult to figure out exactly what you were trying 
> to say, I could only guess that the message appeared to say grub is 
> not the problem.
> > > The sheer volume of people that are having problems with
> > > grub, should be an indicator that it is not making life
> > > easier for the Fedora community.
> >
> > i dont agree with this
>
> Whether you agree or not, many people are having trouble with 
> the way grub handles drive assignments, and is one of the 
> main reasons for attrition from FC.

Please provide facts/numbers/statistics before you make such a blanket
statement.  Many people are having trouble, they do not understand
labels-vs-device names but they are hardly the majority of users and I
would wager a very small minority.  To say it is one of the main reasons
for attrition from FC does require a few facts in support.
> > > Rahul : If you don't have something that can help me, then
> > > do not respond. I have probably been using Linux longer than
> > > you, until grub and SATA drives came out I never had problems
> > > I could not fix. If you are a Red Hat developer then, I
> > > certainly hope the other developers are reading your idiotic
> > > remarks and have you removed.
> >
> > name calling wont help you. if I get removed for suggesting you file
> > bug reports against grub instead of ranting here then that would be
> > very ironic
>
> Did I hurt your feelings?
> I'm so sorry.

Guy,

That is hardly the way to provide good will or encourage people in the
community to _want_ to provide aid.  Have you not heard the phrase "You
catch more files with sugar than with vinegar??
> There are dozens of bug reports, for exactly the same problem, none 
> of them have answers, and many appeared to have been closed.
>
> I booted off the rescue disk, then shuffled around my data so I 
> could boot off a PATA drive, then reinstalled onto that drive.
>
> I can now run FC3 again, and will not attempt to install onto a SATA 
> drive again until I hear a bunch of success stories. Grub doesn't 
> seem to be able to handle a mixture of drive types, and until it 
> can there should be an alternate boot loader.
> > -- 
> > Regards,
> > Rahul Sundaram
>
> Guy Fraser

[Les Mikesell]

On Mon, 2005-02-14 at 12:00, Guy Fraser wrote:
> All I did was add a drive, and grub would not work any more.
> Saying grub has nothing to do with it is complete BULL SHIT.

Grub has to use bios for the first stage of the boot.  If adding
a drive changed your bios' concept of which was your 1st and 2nd
(bootable) drives, then grub really doesn't have anything to do
with it.  You need to install a boot loader on the drive that
bios will boot.

If bios is still booting the initial grub loader, then it is
a grub issue, but just involves setting the configuration to
find where your /boot partition now using grub's non-Linux
oriented device names.
> I ended up having to re-install on a PATA drive to get 
> FC3 working again.

That should only be necessary if your bios won't boot the
SATA.

[Guy Fraser]

On Mon, 2005-14-02 at 15:39 -0600, Les Mikesell wrote:
> On Mon, 2005-02-14 at 12:00, Guy Fraser wrote:
> > All I did was add a drive, and grub would not work any more.
> > Saying grub has nothing to do with it is complete BULL SHIT.
>
> Grub has to use bios for the first stage of the boot.  If adding
> a drive changed your bios' concept of which was your 1st and 2nd
> (bootable) drives, then grub really doesn't have anything to do
> with it.  You need to install a boot loader on the drive that
> bios will boot.
>
> If bios is still booting the initial grub loader, then it is
> a grub issue, but just involves setting the configuration to
> find where your /boot partition now using grub's non-Linux
> oriented device names.

I am using an ASUS P4PE and it has good support for many 
different boot scenarios. My machine was happily booting 
from the Promise TX2 PCI card until I added another drive.
> > I ended up having to re-install on a PATA drive to get 
> > FC3 working again.
>
> That should only be necessary if your bios won't boot the
> SATA.

I agree, but I read all the grub {grub legacy} documentation
and tried many things. The documentation does not have a lot 
of troubleshooting information, and grub has very poor error 
reporting. I would be more helpful if it mentioned which file
or partition could not be found rather than just; Error 15 or
Error 22.

I was able to use grub-install without errors and many times 
used :

# grub
> root (hd4,0)
> find /grub/stage1

(hd4,0)
> setup (hd4)

...
> quit

I changed bios settings and moved the drive around, put it 
on different controllers, changed the device.map and menu.lst 
settings. All I ever got was screens full of grub, error 15 
and error 22. After spending all weekend, I gave up and 
reconfigured to boot from a PATA drive then re-installed onto 
that drive.

Maybe the new version of grub will be better, I don't know 
and to be completely honest I don't care. I have wasted too 
much time with this version. Insolent remarks from certain 
people and the lack of any new suggestions leave me with 
no more stomach for grub. If I wanted a belly full of grub 
I would go on fear factor, but alas I don't, I just want a 
FC3 machine that works when I want to use it.
> -- 
>   Les Mikesell
>    [e-mail]

Have a nice day.

[Jeff Vian]

On Mon, 2005-02-14 at 15:49 -0700, Guy Fraser wrote:
> On Mon, 2005-14-02 at 15:39 -0600, Les Mikesell wrote:
> > On Mon, 2005-02-14 at 12:00, Guy Fraser wrote:
> > > All I did was add a drive, and grub would not work any more.
> > > Saying grub has nothing to do with it is complete BULL SHIT.
> >
> > Grub has to use bios for the first stage of the boot.  If adding
> > a drive changed your bios' concept of which was your 1st and 2nd
> > (bootable) drives, then grub really doesn't have anything to do
> > with it.  You need to install a boot loader on the drive that
> > bios will boot.
> >
> > If bios is still booting the initial grub loader, then it is
> > a grub issue, but just involves setting the configuration to
> > find where your /boot partition now using grub's non-Linux
> > oriented device names.
>
> I am using an ASUS P4PE and it has good support for many 
> different boot scenarios. My machine was happily booting 
> from the Promise TX2 PCI card until I added another drive.
> > > I ended up having to re-install on a PATA drive to get 
> > > FC3 working again.
> >
> > That should only be necessary if your bios won't boot the
> > SATA.
>
> I agree, but I read all the grub {grub legacy} documentation
> and tried many things. The documentation does not have a lot 
> of troubleshooting information, and grub has very poor error 
> reporting. I would be more helpful if it mentioned which file
> or partition could not be found rather than just; Error 15 or
> Error 22.
>
> I was able to use grub-install without errors and many times 
> used :
>
> # grub
> > root (hd4,0)
> > find /grub/stage1
>
> (hd4,0)
> > setup (hd4)
>
> ...
> > quit
>
> I changed bios settings and moved the drive around, put it 
> on different controllers, changed the device.map and menu.lst 
> settings. All I ever got was screens full of grub, error 15 
> and error 22. After spending all weekend, I gave up and 
> reconfigured to boot from a PATA drive then re-installed onto 
> that drive.

If you had both PATA and SATA drives, it may be that the MBR was on the
PATA drive and changing the device locations on the SATA bus would be a
problem.

Don't blame grub, blame your changing hardware config.
> Maybe the new version of grub will be better, I don't know 
> and to be completely honest I don't care. I have wasted too 
> much time with this version. Insolent remarks from certain 
> people and the lack of any new suggestions leave me with 
> no more stomach for grub. If I wanted a belly full of grub 
> I would go on fear factor, but alas I don't, I just want a 
> FC3 machine that works when I want to use it.
> > -- 
> >   Les Mikesell
> >    [e-mail]
>
> Have a nice day.

[Guy Fraser]

On Mon, 2005-14-02 at 18:07 -0600, Jeff Vian wrote:
> On Mon, 2005-02-14 at 15:49 -0700, Guy Fraser wrote:
> > On Mon, 2005-14-02 at 15:39 -0600, Les Mikesell wrote:
> > > On Mon, 2005-02-14 at 12:00, Guy Fraser wrote:
> > > > All I did was add a drive, and grub would not work any more.
> > > > Saying grub has nothing to do with it is complete BULL SHIT.
> > >
> > > Grub has to use bios for the first stage of the boot.  If adding
> > > a drive changed your bios' concept of which was your 1st and 2nd
> > > (bootable) drives, then grub really doesn't have anything to do
> > > with it.  You need to install a boot loader on the drive that
> > > bios will boot.
> > >
> > > If bios is still booting the initial grub loader, then it is
> > > a grub issue, but just involves setting the configuration to
> > > find where your /boot partition now using grub's non-Linux
> > > oriented device names.
> >
> > I am using an ASUS P4PE and it has good support for many 
> > different boot scenarios. My machine was happily booting 
> > from the Promise TX2 PCI card until I added another drive.
> > > > I ended up having to re-install on a PATA drive to get 
> > > > FC3 working again.
> > >
> > > That should only be necessary if your bios won't boot the
> > > SATA.
> >
> > I agree, but I read all the grub {grub legacy} documentation
> > and tried many things. The documentation does not have a lot 
> > of troubleshooting information, and grub has very poor error 
> > reporting. I would be more helpful if it mentioned which file
> > or partition could not be found rather than just; Error 15 or
> > Error 22.
> >
> > I was able to use grub-install without errors and many times 
> > used :
> >
> > # grub
> > > root (hd4,0)
> > > find /grub/stage1
> >
> > (hd4,0)
> > > setup (hd4)
> >
> > ...
> > > quit
> >
> > I changed bios settings and moved the drive around, put it 
> > on different controllers, changed the device.map and menu.lst 
> > settings. All I ever got was screens full of grub, error 15 
> > and error 22. After spending all weekend, I gave up and 
> > reconfigured to boot from a PATA drive then re-installed onto 
> > that drive.
>
> If you had both PATA and SATA drives, it may be that the MBR was on the
> PATA drive and changing the device locations on the SATA bus would be a
> problem.
>
> Don't blame grub, blame your changing hardware config.

I zeroed out all the other MBR's to make sure that wasn't the case
while testing. There wasn't an MBR on anything but the first SATA 
drive until I put in an old 80GB drive and re-installed FC3 on it.

The machine was configured correctly, otherwise it would not have 
even found grub, since I only had one "bootable" drive.
> > Maybe the new version of grub will be better, I don't know 
> > and to be completely honest I don't care. I have wasted too 
> > much time with this version. Insolent remarks from certain 
> > people and the lack of any new suggestions leave me with 
> > no more stomach for grub. If I wanted a belly full of grub 
> > I would go on fear factor, but alas I don't, I just want a 
> > FC3 machine that works when I want to use it.
> > > -- 
> > >   Les Mikesell
> > >    [e-mail]
> >
> > Have a nice day.

[James Wilkinson]

Guy Fraser wrote:
> I agree, but I read all the grub {grub legacy} documentation
> and tried many things. The documentation does not have a lot 
> of troubleshooting information, and grub has very poor error 
> reporting. I would be more helpful if it mentioned which file
> or partition could not be found rather than just; Error 15 or
> Error 22.

Try info grub (or you might find pinfo grub easier. Or try one of the
graphical interfaces) and follow Troubleshooting.

# 15 : File not found
#      This error is returned if the specified file name cannot be found,
#      but everything else (like the disk/partition info) is OK.
(OK: it could say *which* file wasn't found...)
# 22 : No such partition
#      This error is returned if a partition is requested in the device
#      part of a device- or full file name which isn't on the selected
#      disk.

Hope this helps,

James.

[Guy Fraser]

On Tue, 2005-15-02 at 23:42 +0000, James Wilkinson wrote:
> Guy Fraser wrote:
> > I agree, but I read all the grub {grub legacy} documentation
> > and tried many things. The documentation does not have a lot 
> > of troubleshooting information, and grub has very poor error 
> > reporting. I would be more helpful if it mentioned which file
> > or partition could not be found rather than just; Error 15 or
> > Error 22.
>
> Try info grub (or you might find pinfo grub easier. Or try one of the
> graphical interfaces) and follow Troubleshooting.
>
> # 15 : File not found
> #      This error is returned if the specified file name cannot be found,
> #      but everything else (like the disk/partition info) is OK.
> (OK: it could say *which* file wasn't found...)
> # 22 : No such partition
> #      This error is returned if a partition is requested in the device
> #      part of a device- or full file name which isn't on the selected
> #      disk.
>
> Hope this helps,
>
> James.

Thank you, but I already got that information from the HTML manual.

Since it doesn't say what file or partition can't be found, there is 
no way of fixing the problem.

I started with the rescue CD and entered the grub console, then 
proceeded to check the devices and partitions. After I was verifying 
that I had setup the correct devices, I entered the "root" command 
and used the "find" command to verify that I could find "stage1" 
"menu.lst" and a kernel. I did not get any errors.

After about 16 hours of researching all the related issues and 
trying every solution I could find, I gave up.