RHEL5.2, kickstart, USB, "OPCODE" error after reboot

[Kennedy, Cameron]

Thanks Gordon and Greg for your advice. I was able to test both options
and found them to work. Going forward "-driveorder" will have to be the
option I use to get a consistent result, though, as this is primarily
for DR planning purposes and I can't be guaranteed that I will have HP
hardware (though we generally do in tests) I might also have to use some
type of %pre script to determine if this is a HP server or something
else and adjust the "-driveorder" parameter accordingly. It is odd that
the "ignoredisk" option doesn't seem to take effect. 

 

Thanks

 

 

From: kickstart-list-bounces at redhat.com
[mailto:kickstart-list-bounces at redhat.com] On Behalf Of Keegan, Gordon
Sent: Wednesday, August 27, 2008 3:00 PM
To: Discussion list about Kickstart
Subject: RE: RHEL5.2, kickstart, USB, "OPCODE" error after reboot 

 

Cameron,

 

We've seen similar behavior on a couple of our HP servers.  I think
there may be a bug in anaconda somewhere.  If you can boot to into a
rescue mode, check the /boot/grub/device.map file and see if "(hd0)"
maps to "dev/cciss/c0d0" like it's supposed to, or if it maps to
"/dev/sd##" instead.  The couple of times that we've seen it, we have
been able to edit the device.map file then re-run the grub-install and
it booted up normally.

 

Gordon

	 

	
________________________________


	From: Kennedy, Cameron
[mailto:Cameron.Kennedy at bovislendlease.com] 
	Sent: Wednesday, August 27, 2008 12:33 PM
	To: Kickstart-list at redhat.com
	Subject: RHEL5.2, kickstart, USB, "OPCODE" error after reboot 

	Hi all, 

	Just starting to play around with RHEL5.2 servers in our
environment and am coming up with a strange kickstart issue. I have
narrowed it down to the following scenario: 

	Build a HP 385 server, using a RHEL5.2 DVD cut from a downloaded
ISO, and the kickstart file located on a USB stick. After the initial
build, the server reboots, the DVD and USB stick are manually removed
and right where the GRUB screen should be displayed, I get a screen that
looks like a kernel panic screen, though starts with the line "Illegal
OPCODE" and then a bunch of hex output. 

	If I build the server without the USB stick but using the same
kickstart file (copied to the DVD) it works fine. 

	 

	Thinking that the USB stick (/dev/sda) was being incorporated
into the build process (LVM), I added the line: 

	"ignoredisk --drives=sda,sdb,sdc,sdd,sde,sdf"  to the kickstart
script. This did not fix the issue. 

	I then added the line: 

	"part /boot --fstype ext3 --size=200 --ondrive=cciss/c0d0"
forcing /boot to be created on the internal raid disk, which also failed
the fix the issue. I did watch the <F4> screen during the last build
process and I know that /boot is created on /dev/cciss/c0d0 (HP raid)
and the partition information on the USB stick appears to be unchanged
(i.e. not formatted). So I am at a loss as to what else I could check. I
do know the exact same kickstart script, server, usb stick combination
builds a RHEL4.6 server without any problems. Has anyone else seen this
or have any ideas?

	 

	Thanks.  

	 

	 

	
	

	
________________________________


	"This email (including any attachments) is confidential. If you
are not the intended recipient you must not copy, use, disclose,
distribute or rely on the information contained in it. If you have
received this email in error, please notify the sender immediately by
reply email and delete the email from your system. Confidentiality and
legal privilege attached to this communication are not waived or lost by
reason of mistaken delivery to you. Lend Lease does not guarantee that
this email or the attachment(s) are unaffected by computer virus,
corruption or other defects. Lend Lease may monitor incoming and
outgoing emails for compliance with its Email Policy. Please note that
our servers may not be located in your country." 



----------------------------------------- This email (including any attachments) is confidential.  If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it.  If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system.  Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you.  Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects.  Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy.  Please note that our servers may not be located in your country.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/kickstart-list/attachments/20080828/0bacb4aa/attachment.htm>