This page will walk-through booting the LiveCD .iso
file directly onto a BMC.
A Cray Pre-Install Toolkit ISO is required for this process. This ISO can be obtained from:
Most BMCs offer a Web Interface for controlling the node and for providing access to its BIOS and firmware.
Refer to the following pages based on your node vendor for help mounting an ISO image:
iLO BMCs allow for booting directly from an HTTP-accessible ISO location.
Enter the
Virtual Media URL
, selectBoot on Next Reset
, and clickInsert Media
.
Next reboot by selecting
Reset
in the top right power menu.
Open the virtual terminal by choosing the
HTML5 Console
option when clicking the terminal image in the bottom left corner.
NOTE
It may appear that the boot is stalled at a line ofEXT4-fs (loop1): mounted ...
orStarting dracut pre-mount hook...
. This is the step when it actually begins downloading the ISO’s squashfs root filesystem and can take a few minutes
Gigabyte BMCs allow for booting over NFS or HTTP.
Go to the BMC settings and setup the remote ISO for your protocol and node.
Web Interface
Access your BMC’s web interface and navigate to Settings
-> Media Redirection Settings
-> General Settings
.
Enable Remote Media Support
and Mount CD/DVD
and then fill in the server IP or DNS name and the path to the server.
NOTE
The Gigabyte URL appears to not allow certain characters and has a limit on path length. You may need to move or rename the ISO to a location with a smaller file name.
Next navigate to Image Redirection
-> Remote Images
and click on the Start
button to start the Virtual ISO mount.
Finally, reboot the node and select the Virtual CDROM
option from the manual boot options.
Intel BMCs allow for booting with direct ISO mounts.
Go to the
Virtual Media
menu.
Choose your ISO file:
Click
mount
to make it available.
NOTE
Do not close theVirtual Media
window or the main BMC page until done.
After attaching and booting into the ISO, the password will need to be changed before using the booted OS.
NOTE
The root OS/
directory is writable without persistence. This means that restarting the machine will result in all changes being lost. Before restarting, consider following Backing up the Overlay COW FS and the accompanying Restoring from an Overlay COW FS Backup section.
You can backup the writable overlay upper-dir so that your changes are not lost after a reboot or when updating your ISO.
This requires that you have a location to which you can scp
a tar file as a backup.
tar czf /run/overlay.tar.gz -C /run/overlayfs/rw .
scp /run/overlay.tar.gz <somelocation>
NOTE
If you want to reduce the size of the backup you can also delete any squashfs files first, or exclude them in the tar command using--exclude='*.squashfs'
. You will then need to re-populate those after you restore your backup
Restore a backed up tar file from the previous command with
scp <somelocation> /run/overlay.tar.gz
tar xf /run/overlay.tar.gz -C /run/overlayfs/rw
mount -o remount /
If you excluded the squashfs
files from the backup you will also need to repopulate them following the configuration section.