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

Daniel Huhardeaux devel at tootai.net
Wed Mar 30 13:23:23 UTC 2011


Le 30/03/2011 14:18, Vladimir 'φ-coder/phcoder' Serbinenko a écrit :
> 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.
> [...]

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?

-- 
Daniel





More information about the Pkg-grub-devel mailing list