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

Storix System Backup Administrator 69 Version 8.2 Linux System Recovery Guide
Intel 32-bit (BIOS) systems using LILO or GRUB: In addition, the boot filesystem must be in a primary
disk partition (1-4), not in an LVM logical volume or a striped software RAID (meta-disk) device.
Intel 64-bit (UEFI) systems using ELILO: In addition, the boot filesystem (/boot/efi) must be a VFAT
filesystem on a partition with the boot flag set. This may be either GPT or MSDOS partition table, but it
is recommended that the boot filesystem is on the first partition of the boot disk.
IBM System p and System i using Yaboot: These systems require that you have a PReP boot (type 41)
or FAT16 partition on the boot disk, into which the yaboot boot loader is copied. When using a PReP
partition, be careful to make this partition small (< 10 MB) since the entire partition is read into memory.
The boot filesystem must also be in a primary (1-4) partition on the same disk, and contain an ext2,
ext3, reiserfs or xfs filesystem.
It is sometimes advantageous to have the root (/) filesystem in a striped logical volume or software RAID,
or be a Reiserfs filesystem, for instance. For this to be possible, you cannot use the root filesystem as the
boot filesystem. Therefore, you can create a /boot (or /yaboot or /boot/efi) filesystem in addition to the
root filesystem. This will become the boot filesystem, and may be of a size only large enough to contain the
boot configuration files, kernel and initrd images. Since the root filesystem is no longer part of the boot
process, there are no limitations on the type of container (LVM, RAID, partition, etc) of the root filesystem,
or its filesystem type.
If these conditions are met, SBAdmin will create this filesystem during the system install process and use it
to store the boot configuration files, kernel and initrd image required to mount the “real” root filesystem.
With all of the information and files required by the boot loader existing in this filesystem there are no
longer ANY limitations on what device or filesystem the root filesystem can be created on!
Refer to the Boot loader section for additional information on each boot loader’s requirements.
Doing it yourself
In some cases, SBAdmin may not be able to determine what device support is required or already built into
the kernel. Therefore, at the end of the installation process, you are placed in a prompt (assuming this is
not a no-prompt installation), where you can use your own commands for configuring a different boot
loader as needed. At this point, you are given a message similar to the following:
=====================================================================
THE SYSTEM HAS BEEN RESTORED SUCCESSFULLY!
=====================================================================
LILO has been configured as the boot loader. If you want to use a
different boot loader or require additional configuration prior to
rebooting the system, you may do so now.
The LILO boot configuration file is /etc/lilo.conf. Your original
lilo.conf, if any, has been saved as /storix/temp/storix_install/lilo.conf.
---------------------------------------------------
Please remove any boot media and be sure the
system firmware is configured to boot from "sda".
---------------------------------------------------
====================================================================="
When done, type "exit" to complete the installation process and reboot.
sh>
At this point, if no change is required, just type “exit” to allow the system to reboot. If you want to make
changes, you can manually update your boot loader configuration or install a different boot loader. This will
override the boot loader configuration that SBAdmin applied. If you want to revert back to the original boot
loader configuration that was overwritten by SBAdmin, the original copies of the config files are located in
the /storix/temp/storix_install directory (assuming /storix is the data directory on client). Be warned
however that the SBAdmin configuration has taken into account any changes to the system to ensure it will
boot after the restore. The previous configuration may no longer be valid.