Re: [xcat-user] Unable to boot from HD after auto-discovery.

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

rsetboot sets boot device. &nbsp;If the boot order of the target always netboot attempts first, then rsetboot doesn't matter. &nbsp;rsetboot is required if your boot sequence nominally jumps to the installed OS without trying to netboot.<div> </div><div>Now the issue of endless install, that would be a failure of the OS to update the management server. &nbsp;May need log output to suggest why updateflag would be failing... -----"Pocina, Goran" &lt;Gor...@DE...&gt; wrote: -----<div style="padding-left:5px;"><div style="padding-right:0px;padding-left:5px;border-left:solid black 2px;">To: xCAT Users Mailing list &lt;xca...@li...&gt; From: "Pocina, Goran" &lt;Gor...@DE...&gt; Date: 10/10/2012 08:22AM Subject: Re: [xcat-user] Unable to boot from HD after auto-discovery.

<!--Notes ACF
<meta http-equiv="Content-Type" content="text/html; charset=utf8">-->

<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->

<div class="WordSection1">
BTW I&#8217;m not completely clear on how &#8220;rpower&#8221;, &#8220;rsetboot&#8221;, &#8220;nodeset/rinstall&#8221; &nbsp;work together.&nbsp; Sometimes, before
 using &#8220;rinstall&#8221;, I find it&#8217;s necessary to run &#8220;rsetboot net&#8221;, otherwise the node simply boots up into the old OS without attempting an install.&nbsp;&nbsp; However with KVM guest installs, this doesn&#8217;t seem to be needed.&nbsp; Also, sometimes it&#8217;s necessary to run &#8220;rsetboot
 hd&#8221; following the install, otherwise the node will continuously re-install itself, other times it will simply boot up the new OS as expected.&nbsp;&nbsp;
<o:p></o:p>
<o:p>&nbsp;</o:p>
I suspect it has to do with the type of node, and with whether or not the install was completely successful, but
 I don&#8217;t completely understand it.<o:p></o:p>
<o:p>&nbsp;</o:p>
Thanks,<o:p></o:p>
<o:p>&nbsp;</o:p>
Goran<o:p></o:p>
<o:p>&nbsp;</o:p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
From:
 Pocina, Goran 
Sent: Tuesday, October 09, 2012 5:10 PM 
To: xCAT Users Mailing list 
Subject: RE: [xcat-user] Unable to boot from HD after auto-discovery.<o:p></o:p>
</div>
</div>
<o:p>&nbsp;</o:p>
Thanks.<o:p></o:p>
<o:p>&nbsp;</o:p>
The node went into standby mode.&nbsp;&nbsp; Should I remove that as well from kcmdline?<o:p></o:p>
<o:p>&nbsp;</o:p>
I removed &#8220;quiet console&#8230;&#8221; from bootparams.kcmdline, and then ran &#8220;rsetboot labcm001 hd&#8221; and &#8220;rpower boot&#8221;, which
 resulted in the following being generated:<o:p></o:p>
<o:p>&nbsp;</o:p>
[root@drdkvm0003 nodes]# cat /tftpboot/xcat/xnba/nodes/labcm0001<o:p></o:p>
#!gpxe<o:p></o:p>
#standby<o:p></o:p>
imgfetch -n kernel
<a href="http://$%7bnext-server%7d/tftpboot/xcat/genesis.kernel.x86_64">http://${next-server}/tftpboot/xcat/genesis.kernel.x86_64</a><o:p></o:p>
imgload kernel<o:p></o:p>
imgargs kernel console=tty0 xcatd=149.77.53.252:3001
destiny=standby BOOTIF=01-${netX/machyp}<o:p></o:p>
imgfetch
<a href="http://$%7bnext-server%7d/tftpboot/xcat/genesis.fs.x86_64.lzma">http://${next-server}/tftpboot/xcat/genesis.fs.x86_64.lzma</a><o:p></o:p>
imgexec kernel<o:p></o:p>
<o:p>&nbsp;</o:p>
It went into standby mode.&nbsp;&nbsp; The console show detailed kernel boot messages, followed by:<o:p></o:p>
<o:p>&nbsp;</o:p>
Received request to retry in a bit, will call xCAT back in NNN seconds.<o:p></o:p>
<o:p>&nbsp;</o:p>
[root@drdkvm0003 nodes]# nodels labcm0001 chain<o:p></o:p>
labcm0001: chain.chain: runcmd=bmcsetup,standby<o:p></o:p>
labcm0001: chain.node: labcm0001<o:p></o:p>
labcm0001: chain.currstate: standby<o:p></o:p>
labcm0001: chain.currchain: standby<o:p></o:p>
labcm0001: chain.ondiscover:
<o:p></o:p>
labcm0001: chain.comments:
<o:p></o:p>
labcm0001: chain.disable:<o:p></o:p>
<o:p>&nbsp;</o:p>
[root@drdkvm0003 nodes]# nodels labcm0001 bootparams<o:p></o:p>
labcm0001: bootparams.kcmdline: console=tty0 xcatd=149.77.53.252:3001
destiny=standby<o:p></o:p>
labcm0001: bootparams.kernel: xcat/genesis.kernel.x86_64<o:p></o:p>
labcm0001: bootparams.initrd: xcat/genesis.fs.x86_64.lzma<o:p></o:p>
labcm0001: bootparams.node: labcm0001<o:p></o:p>
labcm0001: bootparams.addkcmdline:
<o:p></o:p>
labcm0001: bootparams.comments:
<o:p></o:p>
labcm0001: bootparams.adddhcpstatements:
<o:p></o:p>
labcm0001: bootparams.disable:
<o:p></o:p>
labcm0001: bootparams.dhcpstatements:<o:p></o:p>
<o:p>&nbsp;</o:p>
<o:p>&nbsp;</o:p>
<o:p>&nbsp;</o:p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
From:
 Sten Wolf [<a href="mailto:st...@ch...">mailto:st...@ch...</a>] 
Sent: Tuesday, October 09, 2012 3:42 PM 
To: xCAT Users Mailing list 
Subject: Re: [xcat-user] Unable to boot from HD after auto-discovery.<o:p></o:p>
</div>
</div>
<o:p>&nbsp;</o:p>
That seems strange - why would you need to "nodeset boot" after "rsetboot hd" ? nodeset boot modifies tftpboot files, but rsetboot hd
 should already bypass the entire pxe chain. 
As an interim troubleshooting step - try removing the string "quiet console=ttyS1,115200" then issue rpower
 boot again to the node (do not "nodeset" or you will overwrite your modifications), this time with console attached directly to the node (or with ipmi console redirection, not serial redirection), to see what happens after initial image is loaded.<o:p></o:p>
<div>
On 09/10//2012 21:00, Pocina, Goran wrote:<o:p></o:p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
Posted again after fixing text formatting:<o:p></o:p>
&nbsp;<o:p></o:p>
xCAT 2.7.3&nbsp; &nbsp;CentOS &nbsp;6.2 local disk installs have been working for us on a node configured with noderes.netboot=xnba.&nbsp;<o:p></o:p>
We can toggle back and forth between &#8220;net&#8221; and &#8220;hd&#8221; boots using the &#8220;rsetboot: command.<o:p></o:p>
We recently tried auto-discovery, and since then haven&#8217;t been able to HD boot the node:<o:p></o:p>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Discovery works, with a correct DHCP entry created based on the switch port.<o:p></o:p>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Bmcsetup works, with correct IP address assigned to ipmi.<o:p></o:p>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OS 6.2 install on local disk works appears to work.<o:p></o:p>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
A boot attempt at this point displays the screen below:<o:p></o:p>
&nbsp;<o:p></o:p>
</blockquote>
</div>

<div>------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! <a href="http://p.sf.net/sfu/newrelic-dev2dev">http://p.sf.net/sfu/newrelic-dev2dev</a></div><div>_______________________________________________ xCAT-user mailing list xCA...@li... <a href="https://lists.sourceforge.net/lists/listinfo/xcat-user">https://lists.sourceforge.net/lists/listinfo/xcat-user</a> </div></div></div></div><div></div>

Re: [xcat-user] Unable to boot from HD after auto-discovery.

An extreme cluster/cloud administration toolkit

Re: [xcat-user] Unable to boot from HD after auto-discovery.