Content Comparison

...

1. First, boot the machine and wait for the UEFI boot prompt and select the EBL option, as described here /wiki/spaces/CTT/pages/25088393943.
2. Then enter the FTP command line as described here.

To know what firmware you need for which ERP/CentOS version, contact the SDI/Server groups at LEG.

Here's a list of the know firmware/ERP pairs available in the MLab:

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.

...

1. Kernel/initrd: Make sure they're the same and compatible
2. Kernel opts: You have to set two important flags:
   1. init.stage2: set this to the URL of where you downloaded the kernel/initrd
   2. noverifyssl: this is important, as some D05s can't download the squashfs.img otherwise necessary on first install, as UEFI's date is not set on first boot, and CentOS forces HTTPS downloads (and certificate is invalid). Remaining installs don't need this.
   3. inst.cmdline: if you're using a kickstart script, this makes sure there are no interruptions
   4. acpi=on: this may not be necessary, but CentOS only works with ACPI, so doesn't hurt
3. A good Anaconda KickStart script (the one attached here is a good start)
4. Netboot enabled: Yes

...

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.

...

To learn about all Anaconda's Kick Start script options, read this.

Running the installer

After boot, it can take up to 15 minutes to get to the PXE boot Grub. Go make some tea.

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.

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.

Change Passwords

If you followed the kick start file above, the root password is "centos" and the user "centos" has password "centos" and has sudo.

Change the passwords immediately!