Bug#462835: Debian bug #462835

[Bharath Ramesh]

On Wed, Aug 20, 2008 at 11:03 AM, Felix Zielcke <fzielcke at z-51.de> wrote:
> tag 462835 - moreinfo
> retitle 462835 GRUB fails to grub> prompt with LVM instead of showing the menu
> thanks
>
> Am Mittwoch, den 20.08.2008, 09:36 -0400 schrieb Bharath Ramesh:
>
>> bah, I am dumb. I always thought something was wrong. I was under the impression
>> postinst script would run grub-install for me when it updated grub2.
>
> As I wrote my last mail I had it now in mind that there was recently a
> bug on grub-legacy about this, but I hadn't looked it up:
> http://bugs.debian.org/451701
> Though the explanation is missing:
> We can't assume that (hd0) in device.map is always the disk you want to
> have GRUB in your MBR.
> Now with Robert's cross install UUID patch recently, you could say that
> it's now officially supported to have MBR + /boot + / on totally
> different disks.
>

Its not a problem for me now that I know postinst does not run
grub-install. Till
that time I will manually run grub-install myself. It sounds a bit dumb that
update-grub really only updates the config file. IMO it should be
renamed probably
as update-grub-config as in reality it never updates grub.

>
>> It shows the message "Welcome to Grub"
>>
>> It flickers some message for an instant I am unable to read it and lands
>> me into the grub command prompt.
>
> I should have waited before I retitle'd the bugreport, but as I always
> I'm a bit impatitant.
>
>> I just need to type linux /boot/vmlinuz root=/dev/mapper/lvm-root ro vga=795
>> followed by intird = /boot/initrd and lastly issue boot.
>
> So it's `grub>' and not `rescue>'
> That's a bit weird that the `normal.mod' is loaded but it fails to load
> the configfile or at least to show the menuentry.
> I don't have really a clue what the problem could be.
> Hopefully Robert has an idea.

yes its 'grub>' and not 'rescue>'

I am not sure if its the same issue that I had earlier, could it be that
gfxterm is still broken. I remember that a when I moved to grub2 that issue
of gfxterm not being able to be loaded when /usr was in lvm would cause
this scenario.

>
> With `set' command you can see `root' and `prefix' setting.
> `help' shows you the list of commands.
> `ls -l' shows every device GRUB can see, so your harddisks, partitions
> and LVMs.
>

I dont have physical access to my laptop at the moment. I will check
this and let
you know what the output of the above are when I run them in the 'grub>' prompt.