Prev: Does anyone know how to cross compile the Linux kernel.
Next: Configuring ipmitool failing while loading modules
From: David W. Hodgins on 7 Apr 2010 18:41
On Wed, 07 Apr 2010 04:46:20 -0400, JonT <jgt(a)pobox.com> wrote:

> At boot time I get dumped into a grub shell, with no apparent error

So you are getting stage 2 loaded from one of the filesystems on the
hard drive, but for some reason, stage 2 is not finding the menu.lst.

> From the grub shell, I can manually input enough info to complete the
> boot, using the info I would expect to use, ie
> root (hd0,0)
> kernel /vmlinuz-2.6.30-2-686 root=/dev/hda2 ro
> initrd /initrd.img-2.6.30-2-686
> boot

Do you have a separate partition containing /boot, or is in the
same partition as the root filesystem, i.e. hda2?
As hd0,0 would be hda1, I gather that it's separate.

What's in /boot/grub/device.map?

I don't think it's a version problem, or I'd expect the loading
of stage 2 to fail.

Another things to try. When in the grub shell, try
find /boot/grub/menu.lst
find /grub/menu.lst

Whichever one returns a device, try
configfile (hd0,?) ?/menu.lst
(replace the ? marks based on the output of the find command).

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
From: JonT on 8 Apr 2010 06:13
On 7 Apr, 23:41, "David W. Hodgins" <dwhodg...(a)nomail.afraid.org>
wrote:
> On Wed, 07 Apr 2010 04:46:20 -0400, JonT <j...(a)pobox.com> wrote:
> > At boot time I get dumped into a grub shell, with no apparent error
>
> So you are getting stage 2 loaded from one of the filesystems on the
> hard drive, but for some reason, stage 2 is not finding the menu.lst.

That is my understanding

> > From the grub shell, I can manually input enough info to complete the
> > boot, using the info I would expect to use, ie
> > root (hd0,0)
> > kernel /vmlinuz-2.6.30-2-686 root=/dev/hda2 ro
> > initrd /initrd.img-2.6.30-2-686
> > boot
>
> Do you have a separate partition containing /boot, or is in the
> same partition as the root filesystem, i.e. hda2?
> As hd0,0 would be hda1, I gather that it's separate.

Yes, /boot is on /dev/hda1, which I originally made only 50Mb (7 years
ago I think), which is why I'm now having to clone and resize.

> What's in /boot/grub/device.map?

(hd0) /dev/hda

> I don't think it's a version problem, or I'd expect the loading
> of stage 2 to fail.

That's what I thought

> Another things to try.  When in the grub shell, try
> find /boot/grub/menu.lst
> find /grub/menu.lst
>
> Whichever one returns a device, try
> configfile (hd0,?) ?/menu.lst
> (replace the ? marks based on the output of the find command).

Thanks. I had done the above, but looking for stage1 instead, which
did return the answer (hd0,0), although I didn't know about
configfile. Anyway, I got a linux sysadmin friend to look at it, and
we got the system running as I describe above, after which grub-
install /dev/hda did the trick. What I had tried, following the grub-
install manual and info from various web pages I'd found, was grub-
install --root-directory=/dev/hda1 hda, which had failed. I don't know
why this failed, or why what we did succeeded, but it essentially side
tracked me away from finding the right answer. I think some of the
grub-install description is at best misleading, and at worst just
plain wrong.

Unfortunately this means I'm never going to get to the bottom of why
doing what I tried to do failed, unless of course I run into the same
problem again, which isn't that unlikely given that I have several
debian system with disc that are either dying or too small to be
upgraded any more.
First  |  Prev  | 
Pages: 1 2 3 4
Prev: Does anyone know how to cross compile the Linux kernel.
Next: Configuring ipmitool failing while loading modules