Menu
▾
▴
Re: [xcat-user] Unable to boot from HD after auto-discovery.
|
From: Sten W. <st...@ch...> - 2012-10-10 17:34:41
|
On 10/10//2012 16:13, Jarrod B Johnson wrote:
> rsetboot sets boot device. If the boot order of the target always
> netboot attempts first, then rsetboot doesn't matter. rsetboot is
> required if your boot sequence nominally jumps to the installed OS
> without trying to netboot.
>
> Now the issue of endless install, that would be a failure of the OS to
> update the management server. May need log output to suggest why
> updateflag would be failing...
>
> -----"Pocina, Goran" <Gor...@DE...> wrote: -----
> To: xCAT Users Mailing list <xca...@li...>
> From: "Pocina, Goran" <Gor...@DE...>
> Date: 10/10/2012 08:22AM
> Subject: Re: [xcat-user] Unable to boot from HD after auto-discovery.
>
> BTW I'm not completely clear on how "rpower", "rsetboot",
> "nodeset/rinstall" work together. Sometimes, before using
> "rinstall", I find it's necessary to run "rsetboot net", otherwise the
> node simply boots up into the old OS without attempting an install.
> However with KVM guest installs, this doesn't seem to be needed.
> Also, sometimes it's necessary to run "rsetboot hd" following the
> install, otherwise the node will continuously re-install itself, other
> times it will simply boot up the new OS as expected.
>
rpower is an ipmi directive - it changes the power state (or report on
it) for a node.
rsetboot is also an ipmi directive - it's a one time change of the first
boot device ( permanent change is via bios/uefi ) for next boot only.
nodeset is an xcat directive - it accomplishes the following as far as I
can tell - set the pxe file (in /tftpboot) , the kickstart file ( in
/install/autoinst) and the dhcp lease ( in /var/lib/dhcpd/dhcpd.leases )
for the node(s).
I hope it's now clear that you have to "rsetboot net" when your
bios/uefi has the hdd as first boot device. Similarly, "rsetboot hd"
means that the bios/uefi is set correctly to net install first (but as
Jarrod pointed out the problem lies with node not notifying the MN it
had been installed, so the pxe file is not updated to "LOCALBOOT 0").
A similar issue sometimes observed when the pxe directive of LOCALBOOT
is not observed - the pxe file is correct, but the node tries to boot
from net over and over again.
can you provide the output of "lsdef labcm0001 -i provmethod,nodetype"?
possibly your node is no longer configured as statefull.
> I suspect it has to do with the type of node, and with whether or not
> the install was completely successful, but I don't completely
> understand it.
>
> Thanks,
>
> Goran
>
> *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.
>
> 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
> <ttp://$%7bnext-server%7d/tftpboot/xcat/genesis.kernel.x86_64%22>
>
> imgload kernel
>
> imgargs kernel console=tty0 xcatd9.77.53.252:3001 *destiny=standby*
> BOOTIF-${netX/machyp}
>
> imgfetch http://${next-server}/tftpboot/xcat/genesis.fs.x86_64.lzma
> <ttp://$%7bnext-server%7d/tftpboot/xcat/genesis.fs.x86_64.lzma%22>
>
> 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 xcatd9.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...
> <ailto:st...@ch...%22>]
> *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:
>
> ------------------------------------------------------------------------------
> 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!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> xCAT-user mailing list
> xCA...@li...
> https://lists.sourceforge.net/lists/listinfo/xcat-user
|
