Permalink
Switch branches/tags
yast-bootloader/2_22_0 yast-bootloader/2_21_0 yast-bootloader/2_20_1 yast-bootloader/2_19_16 yast-bootloader/2_19_15 yast-bootloader/2_19_14 yast-bootloader/2_19_13 yast-bootloader/2_19_12 yast-bootloader/2_19_11 yast-bootloader/2_19_10 yast-bootloader/2_19_9 yast-bootloader/2_19_8 yast-bootloader/2_19_7 yast-bootloader/2_19_6 yast-bootloader/2_19_5 yast-bootloader/2_19_4 yast-bootloader/2_19_3 yast-bootloader/2_19_2 yast-bootloader/2_19_1 yast-bootloader/2_19_0 yast-bootloader/2_18_17 yast-bootloader/2_18_16 yast-bootloader/2_18_15 yast-bootloader/2_18_14 yast-bootloader/2_18_13 yast-bootloader/2_18_11 yast-bootloader/2_18_10 yast-bootloader/2_18_9 yast-bootloader/2_18_8 yast-bootloader/2_18_7 yast-bootloader/2_18_6 yast-bootloader/2_18_5 yast-bootloader/2_18_4 yast-bootloader/2_18_3 yast-bootloader/2_18_2 yast-bootloader/2_18_1 yast-bootloader/2_18_0 yast-bootloader/2_17_46 yast-bootloader/2_17_45 yast-bootloader/2_17_44 yast-bootloader/2_17_43 yast-bootloader/2_17_42 yast-bootloader/2_17_41 yast-bootloader/2_17_40 yast-bootloader/2_17_39 yast-bootloader/2_17_38 yast-bootloader/2_17_37 yast-bootloader/2_17_36 yast-bootloader/2_17_35 yast-bootloader/2_17_34 yast-bootloader/2_17_33 yast-bootloader/2_17_32 yast-bootloader/2_17_31 yast-bootloader/2_17_30 yast-bootloader/2_17_29 yast-bootloader/2_17_28 yast-bootloader/2_17_27 yast-bootloader/2_17_26 yast-bootloader/2_17_25 yast-bootloader/2_17_24 yast-bootloader/2_17_23 yast-bootloader/2_17_22 yast-bootloader/2_17_21 yast-bootloader/2_17_20 yast-bootloader/2_17_19 yast-bootloader/2_17_18 yast-bootloader/2_17_17 yast-bootloader/2_17_16 yast-bootloader/2_17_15 yast-bootloader/2_17_14 yast-bootloader/2_17_13 yast-bootloader/2_17_12 yast-bootloader/2_17_11 yast-bootloader/2_17_10 yast-bootloader/2_17_9 yast-bootloader/2_17_8 yast-bootloader/2_17_7 yast-bootloader/2_17_6 yast-bootloader/2_17_5 yast-bootloader/2_17_4 yast-bootloader/2_17_3 yast-bootloader/2_17_2 yast-bootloader/2_17_1 yast-bootloader/2_16_17 yast-bootloader/2_16_16 yast-bootloader/2_16_15 yast-bootloader/2_16_14 yast-bootloader/2_16_13 yast-bootloader/2_16_12 yast-bootloader/2_16_11 yast-bootloader/2_16_10 yast-bootloader/2_16_9 yast-bootloader/2_16_8 yast-bootloader/2_16_7 yast-bootloader/2_16_6 yast-bootloader/2_16_5 yast-bootloader/2_16_4 yast-bootloader/2_16_3 yast-bootloader/2_16_2 yast-bootloader/2_16_1
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
82 lines (62 sloc) 3.6 KB

Supported Scenarios

The goal of this document is to have a single source of information which scenarios are supported by yast2-bootloader.

bootloaders

  • grub2
  • grub2-efi
    • only for UEFI boot
    • only with GPT (see bug)
  • none

Partition table

storage configuration

  • software RAID
    • /boot cannot be on RAID unless it is RAID1
    • cannot have stage1 on MD RAID1, so when /boot is on RAID1, then boot from MBR have to be used
  • LVM
    • /boot cannot be encrypted (not bootloader limitation see bug)
    • LVM can contain volumes on partition-less disks as long as at least one volume lives on partition and disk with such volume is first in boot order. see bug
  • multipath
  • Device mapper
  • local hard disk (including USB/ieee1394)
  • local (hardware) RAID array of any type
  • BIOS-RAID (handled via DM-RAID or MD RAID)
  • iSCSI server with persistent IP address / disk identification
  • NFSv3,v4 share on server with fixed IP address

Architectures

  • x86
  • x86_64
  • ppc64(le and be)
  • s390x
    • /boot/zipl must be on ext fs ( unless upgraded from working zipl configuration )
    • only GRUB2

Stage1 locations

  • MBR of disk where is /boot
  • MBR of identical disks in MD RAID if it contains /boot fate
  • /boot
  • extended partition
    • /boot has to be on a logical partition

Required packages

As we've previously mentioned, we have 3 options for bootloaders: grub2, grub2-efi, and none. The bootloader option, the system configuration, and its architecture will define the required packages. Besides that, the system will always require the package kexec-tools unless the installation is happening through a live medium.

grub2

This is the most common option and requires grub2. There is also special cases that may require additional packages:

  • Generic mbr binary files will require the package syslinux.
  • If using trusted boot option, systems with x86_64 and i386 architectures will require the packages trustedgrub2 and trustedgrub2-i386-pc.

grub2-efi

This option requires packages based on the architecture of the system:

  • i386 architecture requires: grub2-i386-efi.
  • x86_64 architecture requires: grub2-x86_64-efi. If secure boot is used, it also requires shim and mokutil.
  • arm architecture requires: grub2-arm-efi.
  • aarch64 architecture requires: grub2-arm64-efi.

none

This option has no additional package requirement.