For what it is worth, I'd say that so long as you have working 'rsetboot', I actually like the 'boot from hard disk first on normal boot' behavior. It's a touch faster and rsetboot can override.
That's my personal opinion on that mode. From: Andrew Loftus [mailto:[email protected]] Sent: Friday, July 29, 2016 4:56 PM To: xCAT Users Mailing list Subject: Re: [xcat-user] Boot order changed after CentOS install on Lenovo 3550 # pasu backup01 show BootOrder backup01: BootOrder.BootOrder=CentOS=PXE Network=Hard Disk 0 backup01: BootOrder.WolBootOrder=PXE Network=CD/DVD Rom=Hard Disk 0 What's interesting is that the UEFI update is expected behavior, which seems to conflict with the preferred behavior for an xCAT deployed machine is to always boot from PXE first, to allow a re-install when necessary. Otherwise, an extra step is required to force a new installation, namely, rsetboot. Am I correct in my thinking? I'm going to try Arif's suggestion of setting BootModes.SystemBootMode=UEFI Mode and see how that goes. On Fri, Jul 29, 2016 at 3:12 PM, Jarrod Johnson <[email protected]<mailto:[email protected]>> wrote: Can you do pasu <node> show BootOrder You could, if you'd like, change the boot order to 'Hard disk 0' with asu/pasu and it should work (centos 7 will work that way, centos 6 will not). I may also like to see asu show all if you can't find hard disk at all. From: Andrew Loftus [mailto:[email protected]<mailto:[email protected]>] Sent: Friday, July 29, 2016 4:07 PM To: xCAT Users Mailing list Subject: Re: [xcat-user] Boot order changed after CentOS install on Lenovo 3550 Thanks for the information Jarrod! There is no special partitioning and only one "visible" hard drive (there are two physical drives setup in a hardware mirror). I'm relatively new to UEFI systems. Perhaps if I understand it better I can troubleshoot it better. Where can I learn more about the UEFI install procedure that you mentioned above? On Fri, Jul 29, 2016 at 2:40 PM, Jarrod Johnson <[email protected]<mailto:[email protected]>> wrote: Just using the normal storage local? No SAN attached storage or anything? For reference, on install UEFI compatible systems look at the partition id they write their boot loader to. They take the partition uuid and tell UEFI firmware 'hey, next time boot to this file on the partition with this UUID'. If it for some reason selected a storage device that is *not* visible from UEFI, this behavior would be seen (It's looking for a UUID that doesn't exist). Is there a custom partition plan? Are there multiple disks? Some versions of CentOS will struggle if '/boot' and '/boot/efi' get split up, for example. From: Andrew Loftus [mailto:[email protected]<mailto:[email protected]>] Sent: Friday, July 29, 2016 3:36 PM To: [email protected]<mailto:[email protected]> Subject: [xcat-user] Boot order changed after CentOS install on Lenovo 3550 xCAT version: 2.11.1 OS: CentOS Linux release 7.2.1511 (Core) Hardware: Lenovo X-series 3550 Install type: diskful install Node PXE boots successfully and OS install completes successfully. Upon reboot, the machine fails to boot because it can't find a valid OS. Using rcons to get to machine console, we find a new boot option named 'CentOS' and it is first in the boot priority list. Does anyone know where this comes from? Why it's there? How to fix it or prevent it from getting set in the first place? Even a gentle shove in the right direction to troubleshoot this would be greatly appreciated. Cheers, --Andy
------------------------------------------------------------------------------
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
