Illegal OpCode in NFS Kickstart
From: Jason Dixon (jason_at_dixongroup.net)
Date: 09/29/03
- Previous message: R.E.: "imap question again...sorry if u replied before"
- Next in thread: Jason Dixon: "Re: Illegal OpCode in NFS Kickstart"
- Reply: Jason Dixon: "Re: Illegal OpCode in NFS Kickstart"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Red Hat Mailing List <redhat-list@redhat.com> Date: 29 Sep 2003 15:22:43 -0400
I'm attempting a RHAS 2.1 pxeboot NFS kickstart on an HP DL-740. This
configuration works fine on a variety of other Compaq/HP servers
(1850/320/360/380/580/etc). However, attempts to kickstart this server
die with a "red screen of death" and an error message of "Illegal
OpCode".
So far, I've gathered that it locks up right after loading the vmlinuz
and initrd.img from the dhcp server. However, this happens *before* the
install attempts to nfs mount the / directory. I've verified that this
is not a network issue by booting into rescue mode and mounting nfs (and
tcpdump-ing on the nfs server). At this point, it appears to be a
problem with the cciss driver for the internal array in the pxeboot
images.
Red Hat has asked me to try this config with the RHAS 2.1 Update 2
images. I was able to successfully install via CD, but the pxeboot NFS
kickstart still fails in the same way. Has anyone ever seen anything
like this? Neither google nor RH's bugzilla were at all helpful.
TIA,
-- Jason Dixon, RHCE DixonGroup Consulting http://www.dixongroup.net -- redhat-list mailing list unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
- Previous message: R.E.: "imap question again...sorry if u replied before"
- Next in thread: Jason Dixon: "Re: Illegal OpCode in NFS Kickstart"
- Reply: Jason Dixon: "Re: Illegal OpCode in NFS Kickstart"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- V210 BGE0@1000FDX (Adam Tomkinson)
... sunmanagers Digest, Vol 31, Issue 28 ... When connecting a server to
a Gig interface you need to enable autoneg ... Blocked port after process kill ...
NFS oddity ... (SunManagers) - V210 BGE0@1000FDX
... When connecting a server to a Gig interface you need to enable autoneg ... Blocked
port after process kill ... NFS oddity ... where hostname is the name of the
NFS client which will automount the ... (SunManagers) - Solved: Perl/NFS "Text File Busy" Error And Related Problems
... Â That means I am actually editing the Perl file on ... and I am running it
on another (my server). ... The first problem I had was that when I saved my script
through NFS, ... apt-get install nfs-kernel-server ... (Debian-User) - RC1 dump hangs - sometimes
... nfs send error 35 for server backup:/back ... K8-class CPU) ...
port may not be enabled ... (freebsd-current) - 7.0 RC1 dump hangs - sometimes
... nfs send error 35 for server backup:/back ... K8-class CPU) ...
port may not be enabled ... (freebsd-current)