Bug#495049: grub-pc: does not boot because module "normal" is not loaded

[Felix Zielcke]

Am Mittwoch, den 13.08.2008, 19:13 -0700 schrieb Ian Bruce:

> 
> I installed grub because lilo wouldn't boot any more.
> My root fs is on lvm; I don't know if this is related.
> 
> After running "grub-install" and rebooting, grub drops into the
> "grub rescue>" prompt. The "pc", "lvm", and "ext2" modules are loaded,
> "ls" finds the root volume, and the variable "root" is set 
> appropriately.

Only the variable root or the prefix too?

> Investigation shows that if the following commands are issued:
> 
>     insmod normal
>     normal
> 
>  -- then the boot menu specified by "grub.cfg" appears, and the system
> boots properly. It turns out that the file "core.img" does not contain
> the string "normal".
> It seems like this problem should be easy to fix.

Are sure that if you boot you only type

insmod normal
normal

and then the menu shows? i.e. nothing before like set prefix or set
root?

That would be very weird if GRUB set it's variables right, but still
fails to load grub.cfg by it's own.


fz at fz:~$ strings /boot/grub/core.img|grep normal
fz at fz:~$ 

I think that core.img doestn't contain the string `normal' is just well
normal, grub2 works fine for me, but I don't have LVM or RAID ;)