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

[Kennedy, Cameron]

Thanks for the reply. 

 

I have this line for the bootloader: 

"bootloader --location=mbr --ondrive=cciss/c0d0" 

 

I added this at the same time as I modified the "part /boot" line shown
below. But, this didn't seem to fix the issue. 

 

 

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

 

I would think part of the bootloader is being placed on the USB stick.

 

What do you have for the bootloader statement in kickstart? is there a
driveorder parameter on the directive?

 

Greg Caetano
Hewlett-Packard Company
ESS Software
Platform & Business Enablement Solutions Engineering
Chicago, IL
greg.caetano at hp.com
Red Hat Certified Engineer

 

 

________________________________

From: kickstart-list-bounces at redhat.com
[mailto:kickstart-list-bounces at redhat.com] On Behalf Of Kennedy, Cameron
Sent: Wednesday, August 27, 2008 11:33 AM
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/20080827/2d7c70be/attachment.htm>