Chapter 23. Installation and Booting

BFS installation fails on VV when automatic LVM partitioning is selected

When attempting installation using Boot From SAN (BFS) with an HP StoreServ 3PAR Storage Volume (VV), the installation fails during disk partitioning and LVM volume group activation with the message:
Volume group "VolGroup" has insufficient free space.
The failure is seen across all StoreServ volume types (Std VV, TPVV, TDVV). To work around this problem, if using LVM, select the Custom Partition Layout option and reduce the swap and /home partition size by 1-2 GB. If not using LVM, Select the Standard Partition option. (BZ#1190264)

Using the --nocore option in the %packages section of a kickstart file may result in a broken system

If the --nocore option is used in the %packages section of a kickstart file, core system packages and libraries will not be installed, which may result in the system being unable to perform essential tasks such as user creation, and may render the system unusable. To avoid this problem, do not use --nocore. (BZ#1191897)

The zipl boot loader requires target information in each section

When calling the zipl tool manually from a command line using a section name as a parameter, the tool was previously using the target defined in the default section of the /etc/zipl.conf file. In the current version of zipl the default sections' target is not being used automatically, resulting in an error.
To work around the problem, manually edit the /etc/zipl.conf configuration file and copy the line starting with target= from the default section to every section. (BZ#1203627)

The installer displays the number of multipath devices and number of multipath devices selected incorrectly

Multipath devices are configured properly, but the installer displays the number of devices and number of selected devices incorrectly. There is no known workaround at this point. (BZ#914637)

The installer displays the amount of disk space within multipath devices incorrectly

Multipath devices are configured properly, but the installer displays disk space and number of devices incorrectly. There is no known workaround at this point. (BZ#1014425)