CentOS - Sep 2008 - Illegal opp code

Hi,


HP DL 385 G2.
CentOS 5.1
Kernel 2.6.18-92.1.10.el5

I have a newly installed server that was running x. It told me there
were updates to install. I accepted that all, except sysreport as I
always seem to have problems installing. I rebooted, having set the
default run level to 3. I then got a red screen with an "illegal
OpCode" error message.

I have used my CD to boot into rescue more. My old system is mounted under /mnt.

I would also like to get my system back up and running. I have put a
fair bit of time into loading libraries and software.

I have tried editing the grub.conf and commenting out the
2.6.18-92.1.10.el5 kernel so it used a previous kernel but I can not
get past this error. There is no message from grub. The system comes
straight from the BIOS messages into this red screen.

Is there any other ways to determine what the problem is? The error
messages says nothing more that a few lines of hex which don't look
useful to me.

Any thoughts would be appreciated. TIA.
Dp.

2008/9/12 Dermot <paikkos@>:
> HP DL 385 G2.
> CentOS 5.1
> Kernel 2.6.18-92.1.10.el5
>
> I have a newly installed server that was running x. It told me there
> were updates to install. I accepted that all, except sysreport as I
> always seem to have problems installing. I rebooted, having set the
> default run level to 3. I then got a red screen with an "illegal
> OpCode" error message.
>
> I have used my CD to boot into rescue more. My old system is mounted under
/mnt.
>
> I would also like to get my system back up and running. I have put a
> fair bit of time into loading libraries and software.
>
> I have tried editing the grub.conf and commenting out the
> 2.6.18-92.1.10.el5 kernel so it used a previous kernel but I can not
> get past this error. There is no message from grub. The system comes
> straight from the BIOS messages into this red screen.
>
> Is there any other ways to determine what the problem is? The error
> messages says nothing more that a few lines of hex which don't look
> useful to me.
This turned out to be an grub issue. The illegal OpCode message seems
to come the HP hardware/BIOS.

I resolved it by booting using an CentOS cd, doing linux rescue at
boot.
>chroot /mnt/sysimage
>grub
grub> device (hd0) /dev/csiss/c0d0
grub> root (hd0,0)
grub> setup (hd0)

It took a couple of attempts, my knowledge of grub is limited. During
the process I also booted from a DOS floppy and did a fdisk /mbr. That
removed the Illegal OpCode which confirmed I was on the right route.

Hopefully this post might help some other poor HP harware user.
Dp.