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 12:18:57 UTC 2011
On 30.03.2011 14:04, Daniel Huhardeaux wrote:
> Le 30/03/2011 13:20, Vladimir 'φ-coder/phcoder' Serbinenko a écrit :
>> usertag 611537 not-upstream
>> thanks
>> On 30.01.2011 15:29, Daniel Huhardeaux wrote:
>>> * grub-pc/install_devices: (hd0)
>> This is the problem. Automatic update reinstalls GRUB only to one of the
>> devices. Use "sudo dpkg-reconfigure grub-pc" to make it install on both
>> sda and sdb
> It was done like you say, that's not the problem. Grub is installed on
> both disks.
Yes but only one of the two installed core.img matches the modules.
> If you read carefully my message, the problem appears *ONLY* when grub
> graphical terminal is activated.
>
mismatch of core.img and modules can manifest in variety of ways,
usually crashes when you try to use a function that was modified. In
this case it's something gettext of gfxterm-related.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
More information about the Pkg-grub-devel
mailing list