Bug#611537: grub-pc: In an mdadm RAID1 area GRUB2 fails to boot from second HDD (at, least in SATA environment) when graphical terminal activated

Vladimir 'φ-coder/phcoder' Serbinenko phcoder at gmail.com
Wed Mar 30 13:37:32 UTC 2011


> I don't quiet understand: I ran "sudo dpkg-reconfigure <everything
> related to grub>" to be sure that everything is fine, this include
> grub-pc as you point it. Nothing helped till I removed the graphical
> terminal.
>
> I installed few other servers with Debian stable after this, always
> removed the graphical terminal W/O reconfiguring grub related stuff
> and all went smooth. So how can the core.img differe from one disk to
> the other?
>
Consider following scenario:
You install GRUB to both sda and sdb.
Then you do a sudo aptitude upgrade or equivalent. It finds a new GRUB
version and installs it, updating core.img on sda and modules. So
core.img from sda and modules are in sync. But the core.img on sdb isn't
updated and so it gets out of sync with modules.
Another possible reason for such a failure is a mdraid array desync.
Yet, there was a similar report affecting some other users to warant
further investigation. Could you try to do in GRUB shell:
insmod gettext
lang=fr
and tell the result?


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko







More information about the Pkg-grub-devel mailing list