<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:m = "http://schemas.microsoft.com/office/2004/12/omml"><HEAD> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2900.3395" name=GENERATOR> <STYLE>@font-face { font-family: Calibri; } @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; } P.MsoNormal { FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif" } LI.MsoNormal { FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif" } DIV.MsoNormal { FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif" } A:link { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } A:visited { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.EmailStyle17 { COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-compose } .MsoChpDefault { mso-style-type: export-only } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US vLink=purple link=blue> <DIV dir=ltr align=left><SPAN class=457565618-27082008><FONT face=Arial color=#0000ff size=2>Cameron,</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=457565618-27082008><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=457565618-27082008><FONT face=Arial color=#0000ff size=2>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.</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=457565618-27082008><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=457565618-27082008><FONT face=Arial color=#0000ff size=2>Gordon</FONT></SPAN></DIV><BR> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> <FONT face=Tahoma size=2><B>From:</B> Kennedy, Cameron [mailto:Cameron.Kennedy@bovislendlease.com] <BR><B>Sent:</B> Wednesday, August 27, 2008 12:33 PM<BR><B>To:</B> Kickstart-list@redhat.com<BR><B>Subject:</B> RHEL5.2, kickstart, USB, "OPCODE" error after reboot <BR></FONT><BR></DIV> <DIV></DIV> <DIV class=Section1> <P class=MsoNormal>Hi all, <o:p></o:p></P> <P class=MsoNormal>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: <o:p></o:p></P> <P class=MsoNormal>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. <o:p></o:p></P> <P class=MsoNormal>If I build the server without the USB stick but using the same kickstart file (copied to the DVD) it works fine. <o:p></o:p></P> <P class=MsoNormal><o:p> </o:p></P> <P class=MsoNormal>Thinking that the USB stick (/dev/sda) was being incorporated into the build process (LVM), I added the line: <o:p></o:p></P> <P class=MsoNormal>“ignoredisk --drives=sda,sdb,sdc,sdd,sde,sdf” to the kickstart script. This did not fix the issue. <o:p></o:p></P> <P class=MsoNormal>I then added the line: <o:p></o:p></P> <P class=MsoNormal>“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?<o:p></o:p></P> <P class=MsoNormal><o:p> </o:p></P> <P class=MsoNormal>Thanks. <o:p></o:p></P> <P class=MsoNormal><o:p> </o:p></P> <P class=MsoNormal><o:p> </o:p></P></DIV><BR clear=all> <P> <HR SIZE=1> <P></P> <P><FONT face="Arial Narrow" size=2>"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." </FONT></P></BLOCKQUOTE></BODY></HTML>