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]

On 30.03.2011 15:55, Daniel Huhardeaux wrote:
> Le 30/03/2011 15:37, Vladimir 'φ-coder/phcoder' Serbinenko a écrit :
>>> 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.
>
> This is OK: what I don't understand is that you told me to run
> dpkg-reconfigure grub-pc to avoid this and that I did it (and more
> than one)  and it change nothing.
>
You can choose which devices you want GRUB to be installed to by
"dpkg-reconfigure grub-pc". But I'm not familiar with packaging
>> 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?
>
> I will not be able to do anything as I don't get any grub cli ! Server
> just hang after the bios stuff :-(
>
I mean, set GRUB_TERMINAL=console (a config that afaiu works) and try
executing these commands to see if it triggers the bug.


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