sdn: add/improve doc

[pve-docs.git] / system-booting.adoc

diff --git a/system-booting.adoc b/system-booting.adoc
index 8400a26e6a0fe7b75646717af656788c103248e6..24ceb7ee91df8ed7b2809ea0763193bad64d9d48 100644 (file)
--- a/system-booting.adoc
+++ b/system-booting.adoc
@@ -12,8 +12,9 @@ For EFI Systems installed with ZFS as the root filesystem `systemd-boot` is
 used. All other deployments use the standard `grub` bootloader (this usually
 also applies to systems which are installed on top of Debian).
 
+
 [[sysboot_installer_part_scheme]]
-Partitioning scheme used by the installer
+Partitioning Scheme Used by the Installer
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The {pve} installer creates 3 partitions on the bootable disks selected for
@@ -39,6 +40,45 @@ The created partitions are:
 Partition of all bootable disks for supporting older systems.
 
 
+[[sysboot_determine_bootloader_used]]
+Determine which Bootloader is Used
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+[thumbnail="screenshot/boot-grub.png", float="left"]
+
+The simplest and most reliable way to determine which bootloader is used, is to
+watch the boot process of the {pve} node.
+
+You will either see the blue box of `grub` or the simple black on white
+`systemd-boot`.
+
+[thumbnail="screenshot/boot-systemdboot.png"]
+
+Determining the bootloader from a running system might not be 100% accurate. The
+safest way is to run the following command:
+
+
+----
+# efibootmgr -v
+----
+
+If it returns a message that EFI variables are not supported, `grub` is used in
+BIOS/Legacy mode.
+
+If the output contains a line that looks similar to the following, `grub` is
+used in UEFI mode.
+
+----
+Boot0005* proxmox      [...] File(\EFI\proxmox\grubx64.efi)
+----
+
+If the output contains a line similar to the following, `systemd-bood` is used.
+
+----
+Boot0006* Linux Boot Manager   [...] File(\EFI\systemd\systemd-bootx64.efi)
+----
+
+
 [[sysboot_grub]]
 Grub
 ~~~~
@@ -120,7 +160,7 @@ initrd   /EFI/proxmox/5.0.15-1-pve/initrd.img-5.0.15-1-pve
 .Manually keeping a kernel bootable
 
 Should you wish to add a certain kernel and initrd image to the list of
-bootable kernel use `pve-efiboot-tool kernel add`.
+bootable kernels use `pve-efiboot-tool kernel add`.
 
 For example run the following to add the kernel with ABI version `5.0.15-1-pve`
 to the list of kernels to keep installed and synced to all ESPs:
@@ -188,7 +228,7 @@ To copy and configure all bootable kernels and keep all ESPs listed in
 ----
  pve-efiboot-tool refresh
 ----
-(The equivalent to running `update-grub` on Systems being booted with `grub`).
+(The equivalent to running `update-grub` on systems being booted with `grub`).
 
 This is necessary should you make changes to the kernel commandline, or want to
 sync all kernels and initrds.
@@ -196,12 +236,13 @@ sync all kernels and initrds.
 NOTE: Both `update-initramfs` and `apt` (when necessary) will automatically
 trigger a refresh.
 
+
 [[sysboot_edit_kernel_cmdline]]
-Editing the kernel commandline
+Editing the Kernel Commandline
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You can modify the kernel commandline in the following places, depending on the
-bootloarder used:
+bootloader used:
 
 .Grub
 
@@ -213,5 +254,5 @@ The kernel commandline needs to be placed in the variable
 .Systemd-boot
 
 The kernel commandline needs to be placed as one line in `/etc/kernel/cmdline`.
-To apply your changes, run `pve-efiboot-tool·refresh`, which sets it as the
+To apply your changes, run `pve-efiboot-tool refresh`, which sets it as the
 `option` line for all config files in `loader/entries/proxmox-*.conf`.