...
- First, boot the machine and wait for the UEFI boot prompt and select the EBL option, as described here /wiki/spaces/CTT/pages/25088393943.
- Then enter the FTP command line as described here.
...
| ERP CentOS Version | Firmware Build |
|---|---|
| 17.08 (build 9597) | 153 |
To upload your own firmware to the FTP, contact the SDI group with FTP instructions. Remember to chmod new dir/files, or the update process won't be able to see it.
...
Download kernel/initrd from http://builds.96boards.org/snapshots/reference-platform/components/centos-installer-staging/9497/images/pxeboot/
Set init.stage2 to http://builds.96boards.org/snapshots/reference-platform/components/centos-installer-staging/9497/
This will download the squashfs.img from: http://builds.96boards.org/snapshots/reference-platform/components/centos-installer-staging/9497/LiveOS/
Press the [PXE Boot] button and follow the console without interruptions.
...
As soon as Grub downloads the kernel/initrd, that'll setup the network and it'll download squashfs's stage 2 image. Once that boots, you'll see a screen with a message:
Starting installer, one moment...That will hang in there for a while if you have a broken IPMI image.
Working around the IPMI bug
There is a bug in the IPMI tool for now, so you'll need to kill it before the installer can execute. It'll hang saying waiting for the installer. This is due to the IPMI tool being locked.
Until we find the cause of the hang, you can work around by killing the process.
The installer is running inside tmux, so you'll need to go to the shell pane (ctrl+b+n), then pgrep ipmi, then kill the PID that it prints.
This will free the installer to proceed. To go back to the installer pane, just use ctrl+b+p
If you selected the Kickstart + inst.cmdline, the whole process will proceed without interruptions.
After the installation process starts, it can take up to 15 minutes more to finish. Go walk the dog.
Installer options
If you haven't selected inst.cmdline, the installer will ask you what type you want.
...
If you have added the right KS file in the machine setup and have chosen inst.cmdline, the installation will proceed automatically.
After the installation process starts, it can take up to 15 minutes more to finish. Go walk the dog.
Working around the IPMI bug (again)
Once it gets to "Running post-install scripts", the ipmi tool will hang again.
Same thing as last time, (ctrl+b+n), pgrep ipmi, kill the PID.
Restarting
Finally, the installation will say it finished. If all went well, you should be able to reboot (no PXE) and wait long enough for a CentOS prompt.
...