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]] Sent: Friday, July 29, 2016 3:36 PM To: [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
