Skip to end of banner
Go to start of banner

CentOS on D03/D05

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 7 Next »

Installing CentOS on D03s/D05s is simple and requires three steps using mr-provisioner.

Flashing a new firmware

To flash the new firmware, follow these steps:

  1. First, boot the machine and wait for the UEFI boot prompt and select the EBL option, as described here.
  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.

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.

Choosing the right PXE options

Using mr-provisioner, edit the machine you want and add these options:

  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
    3. inst.cmdline: if you're using a kickstart script, this makes sure there are no interruptions
  3. A good Anaconda KickStart script (the one attached here is a good start)
  4. Netboot enabled: Yes

Example:

Download kernel/initrd from http://builds.96boards.org/snapshots/reference-platform/components/centos-installer-staging/94/images/pxeboot/

Set init.stage2 to http://builds.96boards.org/snapshots/reference-platform/components/centos-installer-staging/94/

This will download the squashfs.img from: http://builds.96boards.org/snapshots/reference-platform/components/centos-installer-staging/94/LiveOS/

Press the [PXE Boot] button and follow the console without interruptions.

To learn about all kernel arguments for the PXE installer, check this page.

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

Running the installer

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+1.

Installer options

The installer will ask you what type you want. If you want to use VNC, you'll have to attach it somehow. If you just want a minimal install, use the KickStarter script attached here and select "console".

If you have added the right KS file in the machine setup, 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.

  • No labels