Storix Software SBAdmin Linux System Recovery Guide - Manual (Page 68)

directory (where STXPATH is the Storix data directory). A new GRUB2 boot option configuration file
/etc/grub.d/01_storix will be created.
LILO – If GRUB or GRUB2 are not being used, LILO will be used instead. If there was a previous
configuration in the /etc/lilo.conf file, that configuration is saved to the STXPATH/temp/storix_install
directory (where STXPATH is the Storix data directory). A new stanza with the boot configuration will
be added to the prior lilo.conf file, if any, or if the previous file was invalid (or unused) a new file will be
created with only one stanza used to boot the system. If a previous file existed, the original copy will be
saved in the STXPATH/temp/storix_install directory (where STXPATH is the Storix data directory).
ELILO – Systems that boot from UEFI firmware with use the ELILO boot loader. The boot loader
configuration file used by ELILO is elilo.conf and will be found in the VFAT filesystem used as the boot
filesystem (typically /boot/efi or a subdirectory of /boot/efi). If the system previously used ELILO, the
original version will be copied to STXPATH/storix/storix_install (where STXPATH is the Storix data
directory) before it is changed.
2. For IBM POWER (System p) and System i systems
Yaboot - SBAdmin does not use the utilities that accompany this boot loader, as they differ greatly
between distributions. Instead, SBAdmin creates its own /etc/yaboot.conf file, then copies the yaboot
boot loader (yaboot.chrp) to the PReP Boot or FAT16 partition. If a previous yaboot.conf file existed,
it will be copied to the STXPATH/temp/storix_install directory (where STXPATH is the Storix data
directory) before being changed.
Refer also to the Boot loader section.
Initial Ramdisk Image
SBAdmin will attempt to determine if any device support is required to mount the root filesystem that is not
already built into your kernel. This may include various filesystem support, LVM commands and modules, or
software RAID commands and modules. If it is determined that required device support is not built into the
kernel, then an Initial Ramdisk Image (initrd/initramfs) is automatically created.
The initrd/initramfs image will contain the device support modules and programs, and a script for loading
and initializing the modules. The initrd is loaded by the kernel prior to mounting the root filesystem.
Therefore, the initrd will initialize any support needed to mount the root filesystem
The /boot filesystem
Boot loaders must be able to access information restored to the system during startup. This information is
contained in the /boot directory (or sometimes /yaboot or /boot/efi) of a filesystem. The /boot directory
may be in the root (/) filesystem or may be its own filesystem. We’ll just refer to it as the “boot” filesystem
here.
The system recovery process will verify that your system configuration, boot loader
and boot device are valid and will require you to make changes as necessary in the
installation menus. In the installation menus, you will only be able to make
selections that are valid, based on your system type, boot filesystem type, and
support available on your system. The menus will also recommend creating a
separate /boot filesystem when necessary.
The boot filesystem must be of a type that the boot loader recognizes. LILO, for instance, must map the
physical disk blocks that make up the boot configuration files, kernel and initrd image. To do so, it must
know the filesystem format. Yaboot and GRUB boot loaders must be able to mount the boot filesystem in
order to find the configuration file, kernel and initrd. In any case, the boot filesystem must be a filesystem
type that the boot loader supports. ELILO must be on a VFAT type filesystem and the partition must be
marked with the boot flag.
Storix System Backup Administrator 68 Version 8.2 Linux System Recovery Guide