Multiple people have now reported this error message with 2.6.23.
Updating GRUB fixes it:
https://bugzilla.redhat.com/show_bug.cgi?id=370391
https://bugzilla.redhat.com/show_bug.cgi?id=371321
On Fri, 09 Nov 2007 11:48:20 -0500 Chuck Ebbert wrote:
> Multiple people have now reported this error message with 2.6.23.
> Updating GRUB fixes it:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=370391
> https://bugzilla.redhat.com/show_bug.cgi?id=371321
Thanks for the info.
A better fix IMHO would be if one could get lilo to work. :)
---
~Randy [who is fed up with grub]
Randy Dunlap wrote:
> On Fri, 09 Nov 2007 11:48:20 -0500 Chuck Ebbert wrote:
>
>> Multiple people have now reported this error message with 2.6.23.
>> Updating GRUB fixes it:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=370391
>> https://bugzilla.redhat.com/show_bug.cgi?id=371321
>
> Thanks for the info.
> A better fix IMHO would be if one could get lilo to work. :)
>
There is a fix in 2.6.24 series (norminated for 2.6.23.2) that makes it
work with old versions of LILO -- and unfortunately breaks old
syslinux... Either way, current versions of LILO should work just fine.
-hpa
Randy Dunlap wrote:
> On Fri, 09 Nov 2007 11:48:20 -0500 Chuck Ebbert wrote:
>
>> Multiple people have now reported this error message with 2.6.23.
>> Updating GRUB fixes it:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=370391
>> https://bugzilla.redhat.com/show_bug.cgi?id=371321
>
> Thanks for the info.
> A better fix IMHO would be if one could get lilo to work. :)
>
> ---
> ~Randy [who is fed up with grub]
BTW, I definitely can agree with your feeling about grub (which is part
of why I maintain a different boot loader suite.) However, if you know
of any LILO problems, please speak up.
-hpa
On Fri, 09 Nov 2007 10:40:54 -0800 H. Peter Anvin wrote:
> Randy Dunlap wrote:
> > On Fri, 09 Nov 2007 11:48:20 -0500 Chuck Ebbert wrote:
> >
> >> Multiple people have now reported this error message with 2.6.23.
> >> Updating GRUB fixes it:
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=370391
> >> https://bugzilla.redhat.com/show_bug.cgi?id=371321
> >
> > Thanks for the info.
> > A better fix IMHO would be if one could get lilo to work. :)
> >
> > ---
> > ~Randy [who is fed up with grub]
>
> BTW, I definitely can agree with your feeling about grub (which is part
> of why I maintain a different boot loader suite.) However, if you know
> of any LILO problems, please speak up.
I don't know of any lilo-specific problems and didn't mean to imply
that LILO is at fault.
The problems that I have seen when I have tried to switch from
grub to LILO are more like config issues:
either "can't find root device" or
"cannot open /dev/console" or other initrd/initramfs issues.
Thanks,
---
~Randy
Randy Dunlap wrote:
> On Fri, 09 Nov 2007 10:40:54 -0800 H. Peter Anvin wrote:
>
>> Randy Dunlap wrote:
>>> On Fri, 09 Nov 2007 11:48:20 -0500 Chuck Ebbert wrote:
>>>
>>>> Multiple people have now reported this error message with 2.6.23.
>>>> Updating GRUB fixes it:
>>>>
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=370391
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=371321
>>> Thanks for the info.
>>> A better fix IMHO would be if one could get lilo to work. :)
>>>
>>> ---
>>> ~Randy [who is fed up with grub]
>> BTW, I definitely can agree with your feeling about grub (which is part
>> of why I maintain a different boot loader suite.) However, if you know
>> of any LILO problems, please speak up.
>
> I don't know of any lilo-specific problems and didn't mean to imply
> that LILO is at fault.
>
> The problems that I have seen when I have tried to switch from
> grub to LILO are more like config issues:
> either "can't find root device" or
> "cannot open /dev/console" or other initrd/initramfs issues.
>
OK. I'd be interested in your experience if you'd be willing to try out
syslinux (extlinux).
-hpa
Chuck Ebbert wrote:
> Multiple people have now reported this error message with 2.6.23.
> Updating GRUB fixes it:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=370391
> https://bugzilla.redhat.com/show_bug.cgi?id=371321
This is indeed a known problem with very old versions of grub. It would
appear that Red Hat's rpms for grub don't actually update (some parts
of?) grub, so it leaves an ancient grub on the system and in use.
-hpa