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

[Pocina, G. <Gor...@DE...>]

Thanks.

The node went into standby mode.   Should I remove that as well from kcmdline?

I removed "quiet console..." from bootparams.kcmdline, and then ran "rsetboot labcm001 hd" and "rpower boot", which resulted in the following being generated:

[root@drdkvm0003 nodes]# cat /tftpboot/xcat/xnba/nodes/labcm0001
#!gpxe
#standby
imgfetch -n kernel http://${next-server}/tftpboot/xcat/genesis.kernel.x86_64
imgload kernel
imgargs kernel console=tty0 xcatd=149.77.53.252:3001 destiny=standby BOOTIF=01-${netX/machyp}
imgfetch http://${next-server}/tftpboot/xcat/genesis.fs.x86_64.lzma
imgexec kernel

It went into standby mode.   The console show detailed kernel boot messages, followed by:

Received request to retry in a bit, will call xCAT back in NNN seconds.
[root@drdkvm0003 nodes]# nodels labcm0001 chain
labcm0001: chain.chain: runcmd=bmcsetup,standby
labcm0001: chain.node: labcm0001
labcm0001: chain.currstate: standby
labcm0001: chain.currchain: standby
labcm0001: chain.ondiscover:
labcm0001: chain.comments:
labcm0001: chain.disable:

[root@drdkvm0003 nodes]# nodels labcm0001 bootparams
labcm0001: bootparams.kcmdline: console=tty0 xcatd=149.77.53.252:3001 destiny=standby
labcm0001: bootparams.kernel: xcat/genesis.kernel.x86_64
labcm0001: bootparams.initrd: xcat/genesis.fs.x86_64.lzma
labcm0001: bootparams.node: labcm0001
labcm0001: bootparams.addkcmdline:
labcm0001: bootparams.comments:
labcm0001: bootparams.adddhcpstatements:
labcm0001: bootparams.disable:
labcm0001: bootparams.dhcpstatements:



From: Sten Wolf [mailto:st...@ch...]
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.

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.
On 09/10//2012 21:00, Pocina, Goran wrote:
Posted again after fixing text formatting:

xCAT 2.7.3   CentOS  6.2 local disk installs have been working for us on a node configured with noderes.netboot=xnba.
We can toggle back and forth between "net" and "hd" boots using the "rsetboot: command.
We recently tried auto-discovery, and since then haven't been able to HD boot the node:

-          Discovery works, with a correct DHCP entry created based on the switch port.

-          Bmcsetup works, with correct IP address assigned to ipmi.

-          OS 6.2 install on local disk works appears to work.

-          A boot attempt at this point displays the screen below: