ping Goh Lip - grub2 specialist

[Tom H]

On Tue, Sep 21, 2010 at 11:12 PM, Christopher Chan
<christopher.chan at bradbury.edu.hk> wrote:
> On Wednesday, September 22, 2010 10:57 AM, Tom H wrote:
>> On Tue, Sep 21, 2010 at 10:51 PM, Christopher Chan
>> <christopher.chan at bradbury.edu.hk>  wrote:
>>> On Wednesday, September 22, 2010 10:29 AM, Tom H wrote:
>>>> On Tue, Sep 21, 2010 at 8:06 PM, Christopher Chan
>>>> <christopher.chan at bradbury.edu.hk> wrote:
>>>>>
>>>>> Know anything about the lousy grub-pc package in Hardy?
>>>>>
>>>>> Got two disks, sda and sdb. Two primary partitions on each (1,2) with
>>>>> the 1 partitions going to md0 for raid1, ext2 and the 2 partitions going
>>>>> to md1 for raid1, pv.
>>>>>
>>>>> grub-install will complain about "unknown device" if I feed it /dev/sda
>>>>> or dev/sdb or '(hd0)' but will complain about "Can't embed core.img blah
>>>>> blah" if I feed it /dev/md0. Rather, grub-setup will complain after
>>>>> grub-install passes the flags onto grub-setup.
>>>>
>>>> I would avoid grub2 pre-Lucid...
>>>
>>> Oh...so I guess I better hold off any attempt to upgrade from Hardy to
>>> Lucid for the server then. grub it is.
>>
>> Does "grub it is" mean that you aren't upgrading or that you're
>> upgrading to grub2 after the upgrade to Lucid (the proper way, :) )?
>
> It means that I am going to install grub on the Hardy box (it currently
> has lilo thanks to the d-i installer) and I am staying put on the server
> until I try out an upgrade of my Hardy desktop to Lucid.

OK. Good luck.

For the record, I should've written "I would avoid grub2 pre-Lucid
with /boot on mdraid".

There was an update to grub-probe pre-Lucid-launch (that I'm not sure
was also made to Karmic) that is needed for proper detection of /boot
on mdraid with 0.90 metadata. There was a further update to grub-probe
for proper detection of /boot on mdraid with 1.0, 1.1, 1.2 metadata
post-Lucid-launch (that I'm not sure was made to either Lucid or
Maverick).