{{Article summary text|Covers various aspects of version 2 of the GRand Unified Bootloader (GRUB).}}

+

{{Related|Arch Boot Process}}

−

{{Article summary heading|Overview}}

+

{{Related|Boot Loaders}}

−

{{Article summary text|{{Boot process overview}}}}

+

{{Related|Master Boot Record}}

−

{{Article summary heading|Related}}

+

{{Related|GUID Partition Table}}

−

{{Article summary wiki|BURG}} - BURG is a brand-new boot loader based on GRUB v2. It can be built on a wider range of OS, and has a highly configurable menu system which works in both text and graphic mode.

[https://www.gnu.org/software/grub/ GRUB] - not to be confused with [[GRUB Legacy]] - is the next generation of the GRand Unified Bootloader. GRUB is derived from [http://www.nongnu.org/pupa/ PUPA] which was a research project to develop the next generation of what is now GRUB Legacy. GRUB has been rewritten from scratch to clean up everything and provide modularity and portability [https://www.gnu.org/software/grub/grub-faq.html#q1].

[https://www.gnu.org/software/grub/ GRUB] - not to be confused with [[GRUB Legacy]] - is the next generation of the GRand Unified Bootloader. GRUB is derived from [http://www.nongnu.org/pupa/ PUPA] which was a research project to develop the next generation of what is now GRUB Legacy. GRUB has been rewritten from scratch to clean up everything and provide modularity and portability [https://www.gnu.org/software/grub/grub-faq.html#q1].

Line 36:

Line 34:

=== Notes for GRUB Legacy users ===

=== Notes for GRUB Legacy users ===

−

* Upgrading from [[GRUB Legacy]] to GRUB is much the same as freshly installing GRUB, which is covered [[#Installation|below]]

+

* Upgrading from [[GRUB Legacy]] to GRUB is much the same as freshly installing GRUB. This topic is covered [[#Installation|here]].

−

* There are differences in the commands of GRUB Legacy and GRUB. Familiarize yourself with [https://www.gnu.org/software/grub/manual/grub.html#Commands GRUB commands] before proceeding (e.g. "find" has been replaced with "search")

+

* There are differences in the commands of GRUB Legacy and GRUB. Familiarize yourself with [https://www.gnu.org/software/grub/manual/grub.html#Commands GRUB commands] before proceeding (e.g. "find" has been replaced with "search").

−

* GRUB is now ''modular'' and no longer requires "stage 1.5". As a result, the bootloader itself is limited -- modules are loaded from the hard drive as needed to expand functionality (e.g. for [[LVM]] or RAID support)

+

* GRUB is now ''modular'' and no longer requires "stage 1.5". As a result, the bootloader itself is limited -- modules are loaded from the hard drive as needed to expand functionality (e.g. for [[LVM]] or RAID support).

−

* Device naming has changed between GRUB Legacy and GRUB. Partitions are numbered from 1 instead of 0 while drives are still numbered from 0, and prefixed with partition-table type. For example, {{ic|/dev/sda1}} would be referred to as {{ic|(hd0,msdos1)}} (for MBR) or {{ic|(hd0,gpt1)}} (for GPT)

+

* Device naming has changed between GRUB Legacy and GRUB. Partitions are numbered from 1 instead of 0 while drives are still numbered from 0, and prefixed with partition-table type. For example, {{ic|/dev/sda1}} would be referred to as {{ic|(hd0,msdos1)}} (for MBR) or {{ic|(hd0,gpt1)}} (for GPT).

−

* GRUB is noticeably bigger than GRUB legacy (occupies ~13 MB in /boot). If you are booting from a separate /boot partition, and this partition is smaller than 32 MB, you will run into disk space issues, and pacman will refuse to install new kernels.

+

* GRUB is noticeably bigger than GRUB legacy (occupies ~13 MB in {{ic|/boot}}). If you are booting from a separate {{ic|/boot}} partition, and this partition is smaller than 32 MB, you will run into disk space issues, and pacman will refuse to install new kernels.

Only 446 bytes of the MBR contain boot code, the next 64 contain the partition table. If you do not want to overwrite your partition table when restoring, it is strongly advised to backup only the MBR boot code:

Only 446 bytes of the MBR contain boot code, the next 64 contain the partition table. If you do not want to overwrite your partition table when restoring, it is strongly advised to backup only the MBR boot code:

GRUB in [[GPT|BIOS-GPT]] configuration requires a [http://www.gnu.org/software/grub/manual/html_node/BIOS-installation.html BIOS boot partition] to embed its {{ic|core.img}} in the absence of post-MBR gap in GPT partitioned systems (which is taken over by the GPT Primary Header and Primary Partition table). This partition is used by GRUB only in BIOS-GPT setups. No such partition type exists in case of MBR partitioning (at least not for GRUB). This partition is also not required if the system is UEFI based, as no embedding of bootsectors takes place in that case.

GRUB in [[GPT|BIOS-GPT]] configuration requires a [http://www.gnu.org/software/grub/manual/html_node/BIOS-installation.html BIOS boot partition] to embed its {{ic|core.img}} in the absence of post-MBR gap in GPT partitioned systems (which is taken over by the GPT Primary Header and Primary Partition table). This partition is used by GRUB only in BIOS-GPT setups. No such partition type exists in case of MBR partitioning (at least not for GRUB). This partition is also not required if the system is UEFI based, as no embedding of bootsectors takes place in that case.

−

For a BIOS-GPT configuration, create a 1007 KiB partition at the beginning of the disk using gdisk, cgdisk or GNU Parted with no filesystem. The size of 1007 KiB will allow for the following partition to be correctly alligned at 1024 KiB. If needed, the partition can also be located somewhere else on the disk, but it should be within the first 2 TiB region. Set the partition type to {{ic|ef02}} in (c)gdisk or {{ic|set <BOOT_PART_NUM> bios_grub on}} in GNU Parted.

+

For a BIOS-GPT configuration, create a 1007 KiB partition at the beginning of the disk using gdisk, cgdisk or GNU Parted with no filesystem. The size of 1007 KiB will allow for the following partition to be correctly alligned at 1024 KiB. If needed, the partition can also be located somewhere else on the disk, but it should be within the first 2 TiB region. Set the partition type to {{ic|ef02}} in (c)gdisk or {{ic|set ''BOOT_PART_NUM'' bios_grub on}} in GNU Parted.

+

+

The GPT partition also creates a protective MBR partition to stop unsupported tools from modifying it. You may need to set a bootable flag on this protective MBR e.g., using cfdisk, or some BIOSes/EFIs will refuse to boot.

{{Note|It is recommended to read and understand the [[UEFI]], [[GPT]] and [[UEFI Bootloaders]] pages.}}

===== Check if you have GPT and an ESP =====

===== Check if you have GPT and an ESP =====

−

An EFI System Partition (ESP) is needed on every disc you wan to boot using EFI. GPT isn't strictly necessary, but it is highly recommended and is the only method currently supported in this article. If you are installing Archlinux on an EFI-capable computer with an already-working operating system, like Windows 8 for example, it is very likely that you already have an ESP. To check for GPT and for an ESP, use {{ic|parted}} as root to print the partition table of the disk you want to boot from. (We're calling it /dev/sda.)

+

An EFI System Partition (ESP) is needed on every disc you wan to boot using EFI. GPT is not strictly necessary, but it is highly recommended and is the only method currently supported in this article. If you are installing Archlinux on an EFI-capable computer with an already-working operating system, like Windows 8 for example, it is very likely that you already have an ESP. To check for GPT and for an ESP, use {{ic|parted}} as root to print the partition table of the disk you want to boot from. (We are calling it /dev/sda.)

# parted /dev/sda print

# parted /dev/sda print

Line 91:

Line 91:

===== Create an ESP =====

===== Create an ESP =====

−

If you do not have an ESP, you will need to create it. Follow [[Unified Extensible Firmware Interface#EFI System Partition]] for instructions on creating an ESP.

+

If you do not have an ESP, you will need to create it. Follow [[UEFI#EFI System Partition]] for instructions on creating an ESP.

== Installation ==

== Installation ==

Line 97:

Line 97:

=== BIOS systems ===

=== BIOS systems ===

−

GRUB can be [[pacman|installed]] with the {{Pkg|grub}} package from the [[official repositories]]. It will replace {{Pkg|grub-legacy}} , if it is installed.

+

GRUB can be [[pacman|installed]] with the {{Pkg|grub}} package from the [[official repositories]]. It will replace {{AUR|grub-legacy}} , if it is installed.

{{Note|Simply installing the package will not update the {{ic|/boot/grub/i386-pc/core.img}} file and the GRUB modules in {{ic|/boot/grub/i386-pc}}. You need to update them manually using {{ic|grub-install}} as explained below.}}

{{Note|Simply installing the package will not update the {{ic|/boot/grub/i386-pc/core.img}} file and the GRUB modules in {{ic|/boot/grub/i386-pc}}. You need to update them manually using {{ic|grub-install}} as explained below.}}

−

==== Install Boot Files ====

+

Before installing, make sure the correct UUIDs of your disks are inserted into {{ic| grub.cfg}}:

{{Note|The method is specific to installing GRUB to a partitioned (MBR or GPT) disk, with GRUB files installed to {{ic|/boot/grub}} and its first stage code installed to the 440-byte MBR boot code region (not to be confused with MBR partition table). For partitionless disk (super-floppy) please refer to [[#Install to partition or partitionless disk]]}}

{{Note|The method is specific to installing GRUB to a partitioned (MBR or GPT) disk, with GRUB files installed to {{ic|/boot/grub}} and its first stage code installed to the 440-byte MBR boot code region (not to be confused with MBR partition table). For partitionless disk (super-floppy) please refer to [[#Install to partition or partitionless disk]]}}

{{Note|{{ic|1=--target=i386-pc}} instructs {{ic|grub-install}} to install for BIOS systems only. It is recommended to always use this option to remove ambiguity in grub-install.}}

+

* {{ic|1=--target=i386-pc}} instructs {{ic|grub-install}} to install for BIOS systems only. It is recommended to always use this option to remove ambiguity in grub-install.

+

}}

If you use [[LVM]] for your {{ic|/boot}}, you can install GRUB on multiple physical disks.

If you use [[LVM]] for your {{ic|/boot}}, you can install GRUB on multiple physical disks.

−

Continue with [[GRUB#Generate config file]] below. The grub config file is not generated by {{ic|grub-install}} command.

+

===== Install to partition or partitionless disk =====

−

−

===== Install to Partition or Partitionless Disk =====

{{Note|GRUB does not encourage installation to a partition boot sector or a partitionless disk like GRUB Legacy or Syslinux does. This kind of setup is prone to breakage, especially during updates, and is not supported by Arch devs.}}

{{Note|GRUB does not encourage installation to a partition boot sector or a partitionless disk like GRUB Legacy or Syslinux does. This kind of setup is prone to breakage, especially during updates, and is not supported by Arch devs.}}

Line 137:

Line 140:

# chattr +i /boot/grub/i386-pc/core.img

# chattr +i /boot/grub/i386-pc/core.img

−

{{Note|{{ic|/dev/sdaX}} used for example only.}}

+

{{Note|

−

+

* {{ic|/dev/sdaX}} used for example only.

−

{{Note|{{ic|1=--target=i386-pc}} instructs {{ic|grub-install}} to install for BIOS systems only. It is recommended to always use this option to remove ambiguity in grub-install.}}

+

* {{ic|1=--target=i386-pc}} instructs {{ic|grub-install}} to install for BIOS systems only. It is recommended to always use this option to remove ambiguity in ''grub-install''.

+

}}

You need to use the {{ic|--force}} option to allow usage of blocklists and should not use {{ic|1=--grub-setup=/bin/true}} (which is similar to simply generating {{ic|core.img}}).

You need to use the {{ic|--force}} option to allow usage of blocklists and should not use {{ic|1=--grub-setup=/bin/true}} (which is similar to simply generating {{ic|core.img}}).

Line 160:

Line 164:

The workaround for this is to set the immutable flag on {{ic|/boot/grub/i386-pc/core.img}} (using chattr command as mentioned above) so that the sector locations of the {{ic|core.img}} file in the disk is not altered. The immutable flag on {{ic|/boot/grub/i386-pc/core.img}} needs to be set only if {{ic|grub}} is installed to a partition boot sector or a partitionless disk, not in case of installation to MBR or simple generation of {{ic|core.img}} without embedding any bootsector (mentioned above).

The workaround for this is to set the immutable flag on {{ic|/boot/grub/i386-pc/core.img}} (using chattr command as mentioned above) so that the sector locations of the {{ic|core.img}} file in the disk is not altered. The immutable flag on {{ic|/boot/grub/i386-pc/core.img}} needs to be set only if {{ic|grub}} is installed to a partition boot sector or a partitionless disk, not in case of installation to MBR or simple generation of {{ic|core.img}} without embedding any bootsector (mentioned above).

−

−

Continue with [[GRUB#Generate config file]] below. The grub config file is not generated by {{ic|grub-install}} command.

* {{ic|1=--target=i386-pc}} instructs {{ic|grub-install}} to install for BIOS systems only. It is recommended to always use this option to remove ambiguity in grub-install.

+

}}

+

+

You can then chainload GRUB's {{ic|core.img}} from GRUB Legacy or syslinux as a Linux kernel or as a multiboot kernel.

+

+

=== UEFI systems ===

−

{{Note|{{ic|1=--target=i386-pc}} instructs {{ic|grub-install}} to install for BIOS systems only. It is recommended to always use this option to remove ambiguity in grub-install.}}

+

{{Note|It is well known that different motherboard manufactures implement UEFI differently. Users experiencing problems getting GRUB or EFI to work properly are encouraged to share detailed steps for hardware-specific cases where UEFI booting does not work as described below. In an effort to keep the parent [[GRUB]] article neat and tidy, see the [[GRUB EFI Examples]] page for these special cases.}}

−

You can then chainload GRUB's {{ic|core.img}} from GRUB Legacy or syslinux as a Linux kernel or as a multiboot kernel.

+

First install the {{Pkg|grub}}, {{Pkg|dosfstools}}, and {{Pkg|efibootmgr}} packages, then follow the instructions below. (The last two packages are required for EFI support in grub.)

+

+

{{Note|Simply installing the package will not update the {{ic|core.efi}} file and the GRUB modules in the ESP. You need to do this manually using {{ic|grub-install}} as explained below.}}

+

+

==== Install boot files ====

+

+

===== Recommended method =====

+

+

{{Note|

+

* The below commands assume you are using installing GRUB for {{ic|x86_64-efi}} (for {{ic|IA32-efi}} replace {{ic|x86_64-efi}} with {{ic|i386-efi}} in the below commands)

+

* To do this, you need to boot using UEFI and not BIOS. If you booted by just copying the ISO file to the USB drive, you have booted using BIOS. You will need to [[Unified Extensible Firmware Interface#Create UEFI bootable USB from ISO|create a UEFI bootable USB device]] and reboot with it or grub-install will show errors.

+

}}

+

+

First, mount the ESP at your preferred mountpoint (usually {{ic|/boot/efi}}, hereafter referred to as $esp). On a first install, you will need to mkdir /boot/efi, if that's where you want to mount it.

+

+

Now, install the GRUB UEFI application to {{ic|$esp/EFI/grub}} and its modules to {{ic|/boot/grub/x86_64-efi}}:

* If you have a problem when running grub-install with sysfs or procfs and it says you have to "modprobe efivars", try [[Unified_Extensible_Firmware_Interface#Switch_to_efivarfs]].

+

* Without {{ic|--target}} or {{ic|--directory}} option, grub-install cannot determine for which firmware to install. In such cases {{ic|grub-install}} will print {{ic|source_dir does not exist. Please specify --target or --directory}}.

+

* {{ic|--efi-directory}} and {{ic|--bootloader-id}} are specific to GRUB UEFI. {{ic|--efi-directory}} specifies the mountpoint of the ESP. It replaces {{ic|--root-directory}}, which is deprecated. {{ic|--bootloader-id}} specifies the name of the directory used to store the {{ic|grubx64.efi}} file.

+

* If you notice carefully, there is no <device_path> option (Eg: {{ic|/dev/sda}}) at the end of the {{ic|grub-install}} command unlike the case of setting up GRUB for BIOS systems. Any <device_path> provided will be ignored by the install script, as UEFI bootloaders do not use MBR or Partition boot sectors at all.

+

}}

+

+

GRUB is now installed.

+

+

===== Alternative method =====

+

+

If you want to keep all of the GRUB boot files inside the EFI System Partition itself, add {{ic|--boot-directory&#61;$esp/EFI}} to the grub-install command:

This puts the GRUB modules in {{ic|$esp/EFI/grub}}. ('/grub' is hard coded onto the end of this path.) Using this method, grub.cfg is kept on the EFI System Partition as well, so make sure you point grub-mkconfig to the right place in the configuration phase:

+

+

# grub-mkconfig -o $esp/EFI/grub/grub.cfg

+

+

Configuration is otherwise the same.

+

+

==== Create a GRUB entry in the firmware boot manager ====

+

+

{{ic|grub-install}} automatically tries to create a menu entry in the boot manager. If it does not, then see [[Beginners' Guide#GRUB]] for instructions to use {{ic|efibootmgr}} to create a menu entry. However, the problem is likely to be that you have not booted your CD/USB in UEFI mode, as in [[UEFI#Create UEFI bootable USB from ISO]].

+

+

==== GRUB Standalone ====

+

+

{{Note|Use {{Aur|grub-git}} pkg for standalone GRUB EFI image as the {{Pkg|grub}} pkg does not contain various grub-mkstandalone specific fixes (specifically {{ic|${cmdpath} }} support, which is necessary).}}

+

+

It is possible to create a {{ic|grubx64_standalone.efi}} application which has all the modules embedded in a tar archive within the UEFI application, thus removing the need for having a separate directory populated with all the GRUB UEFI modules and other related files. This is done using the {{ic|grub-mkstandalone}} command (included in {{Pkg|grub}}) as follows"

+

+

# echo 'configfile ${cmdpath}/grub.cfg' > /tmp/grub.cfg ## use single quotes, ${cmdpath} should be present as it is

{{Note|The option {{ic|1=--modules="part_gpt part_msdos"}} (with the quotes) is necessary for {{ic|${cmdpath} }} feature to work properly.}}

+

+

Then copy the GRUB config file to {{ic|$esp/EFI/grub/grub.cfg}} and create a UEFI Boot Manager entry for {{ic|$esp/EFI/grub/grubx64_standalone.efi}} using [[UEFI#efibootmgr|efibootmgr]].

+

+

===== GRUB Standalone - Technical Info =====

+

+

The GRUB EFI file always expects its config file to be at {{ic|${prefix}/grub.cfg}}. However in the standalone GRUB EFI file, the {{ic|${prefix} }} is located inside a tar archive and embedded inside the standalone GRUB EFI file itself (inside grub env it is denoted by {{ic|"(memdisk)"}}, without quotes). This tar archive contains all the files that would be stored normally at {{ic|/boot/grub}} in case of a normal GRUB EFI install.

+

+

Due to this embedding of {{ic|/boot/grub}} contents inside the standalone image itself, it does not rely on actual (external) {{ic|/boot/grub}} for anything. Thus in case of standalone GRUB EFI file {{ic|1=${prefix}==(memdisk)/boot/grub}} and the standalone GRUB EFI file reads expects the config file to be at {{ic|1=${prefix}/grub.cfg==(memdisk)/boot/grub/grub.cfg}}.

+

+

Hence to make sure the standalone GRUB EFI file reads the external {{ic|grub.cfg}} located in the same dir as the EFI file (inside grub env it is denoted by {{ic|${cmdpath}}}), we create a simple {{ic|/tmp/grub.cfg}} which instructs GRUB to use {{ic|${cmdpath}/grub.cfg}} as its config ({{ic|configfile ${cmdpath}/grub.cfg}} command in {{ic|(memdisk)/boot/grub/grub.cfg}}). We then instruct grub-mkstandalone to copy this {{ic|/tmp/grub.cfg}} file to {{ic|${prefix}/grub.cfg}} (which is actually {{ic|(memdisk)/boot/grub/grub.cfg}}) using the option {{ic|1="/boot/grub/grub.cfg=/tmp/grub.cfg"}}.

+

+

This way the standalone GRUB EFI file and actual {{ic|grub.cfg}} can be stored in any dir inside the EFI System Partition (as long as they are in the same dir), thus making them portable.

+

+

== Generating main configuration file ==

+

+

After the installation, the main configuration file {{ic|grub.cfg}} needs to be generated. The generation process can be influenced by a variety of options in {{ic|/etc/default/grub}} and scripts in {{ic|/etc/grub.d/}}, this is covered in the [[#Basic configuration]] and [[#Advanced configuration]] sections.

−

==== Generate config file ====

+

{{Note|Remember that {{ic|grub.cfg}} has to be re-generated after any change to {{ic|/etc/default/grub}} or {{ic|/etc/grub.d/*}}.}}

−

Finally, generate a configuration for GRUB (this is explained in greater detail in the Configuration section):

* The file path for BIOS systems is {{ic|/boot/grub/grub.cfg}}, NOT {{ic|/boot/grub/i386-pc/grub.cfg}}.

+

* For EFI systems, if GRUB was installed with the {{ic|1=--boot-directory=$esp/EFI}} option set, the {{ic|grub.cfg}} file must be placed in the same directory as {{ic|grubx64.efi}}. Otherwise, the {{ic|grub.cfg}} file goes in {{ic|/boot/grub/}}, just like in BIOS systems.

+

* If you are trying to run ''grub-mkconfig'' in a chroot or ''systemd-nspawn'' container, you might notice that it does not work, complaining that ''grub-probe'' cannot get the "canonical path of /dev/sdaX". In this case, try using ''arch-chroot'' as described [https://bbs.archlinux.org/viewtopic.php?pid&#61;1225067#p1225067 here].

By default the generation scripts automatically add menu entries for Arch Linux to any generated configuration. However, entries for other operating systems do not work out of the box. On BIOS systems, you may want to install {{Pkg|os-prober}}, which detects other operating systems installed on your machine and adds entries for them into {{ic|grub.cfg}}. It can detect only systems on mounted partitions, so mount them before running ''grub-mkconfig''. See [[#Dual-booting]] for advanced configuration.

This section covers only editing the {{ic|/etc/default/grub}} configuration file. See [[#Advanced configuration]] if you need more.

−

This should work out of the box, but an extra utility needs to be installed: os-prober. Install it, then rerun grub-mkconfig -o /boot/grub/grub.cfg. If this fails, you can try manually adding an entry by following the instructions below.

+

{{Note|Remember to always [[#Generating main configuration file|re-generate the main configuration file]] after you make changes to {{ic|/etc/default/grub}}.}}

−

{{Note|If Windows is not found, try mounting its boot partition}}

+

==== Additional arguments ====

−

===== Microsoft Windows installed in BIOS-MBR mode =====

+

To pass custom additional arguments to the Linux image, you can set the {{ic|GRUB_CMDLINE_LINUX}} + {{ic|GRUB_CMDLINE_LINUX_DEFAULT}} variables in {{ic|/etc/default/grub}}. The two are appended to each other and passed to kernel when generating regular boot entries. For the ''recovery'' boot entry, only {{ic|GRUB_CMDLINE_LINUX}} is used in the generation.

−

{{Note|GRUB supports booting {{ic|bootmgr}} directly and chainload of partition boot sector is no longer required to boot Windows in a BIOS-MBR setup.}}

+

It is not necessary to use both, but can be useful. For example, you could use {{ic|<nowiki>GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/sdaX</nowiki> quiet"}} where {{ic|sda'''X'''}} is your swap partition to enable resume after hibernation. This would generate a recovery boot entry without the resume and without ''quiet'' suppressing kernel messages during a boot from that menu entry. Though, the other (regular) menu entries would have them as options.

+

+

For generating the GRUB recovery entry you also have to comment out {{ic|<nowiki>#GRUB_DISABLE_RECOVERY=true</nowiki>}} in {{ic|/etc/default/grub}}.

+

+

You can also use {{ic|<nowiki>GRUB_CMDLINE_LINUX="resume=/dev/disk/by-uuid/${swap_uuid}"</nowiki>}}, where {{ic|${swap_uuid} }} is the [[Persistent_block_device_naming|UUID]] of your swap partition.

+

+

Multiple entries are separated by spaces within the double quotes. So, for users who want both resume and systemd it would look like this:

In GRUB it is possible, by default, to change the look of the menu. Make sure to initialize, if not done already, GRUB graphical terminal, gfxterm, with proper video mode, gfxmode, in GRUB. This can be seen in the section [[#"No suitable mode found" error]]. This video mode is passed by GRUB to the linux kernel via 'gfxpayload' so any visual configurations need this mode in order to be in effect.

+

+

==== Setting the framebuffer resolution ====

−

{{Warning|It is the '''system partition''' that has {{ic|bootmgr}}, not your "real" Windows partition (usually C:). When showing all UUIDs with blkid, the system partition is the one with {{ic|LABEL&#61;"SYSTEM RESERVED"}} or {{ic|LABEL&#61;"SYSTEM"}} and is only about 100 to 200 MB in size (much like the boot partition for Arch). See [[Wikipedia:System partition and boot partition]] for more info.}}

+

GRUB can set the framebuffer for both GRUB itself and the kernel. The old {{ic|1=vga=}} way is deprecated. The preferred method is editing {{ic|/etc/default/grub}} as the following sample:

−

Throughout this section, it is assumed your Windows partition is /dev/sda1. A different partition will change every instance of hd0,msdos1. First, find the UUID of the NTFS filesystem of the Windows's SYSTEM PARTITION where the {{ic|bootmgr}} and its files reside. For example, if Windows {{ic|bootmgr}} exists at {{ic|/media/SYSTEM_RESERVED/bootmgr}}:

+

GRUB_GFXMODE=1024x768x32

+

GRUB_GFXPAYLOAD_LINUX=keep

−

For Windows Vista/7/8:

+

To generate the changes, run:

+

# grub-mkconfig -o /boot/grub/grub.cfg

−

# grub-probe --target=fs_uuid /media/SYSTEM_RESERVED/bootmgr

+

The {{ic|gfxpayload}} property will make sure the kernel keeps the resolution.

* If this example does not work for you try to replace {{ic|1=gfxmode="1024x768x32"}} by {{ic|1=vbemode="0x105"}}. Remember to replace the specified resolution with one suitable for your screen

+

* To show all the modes you can use {{ic|1=# hwinfo --framebuffer}} (hwinfo is available in [community]), while at GRUB prompt you can use the {{ic|1=vbeinfo}} command

+

}}

−

{{Note|For Windows XP, replace {{ic|bootmgr}} with {{ic|NTLDR}} in the above commands. And note that there may not be a separate SYSTEM_RESERVED partition; just probe the file NTLDR on your Windows partition.}}

+

If this method does not work for you, the deprecated {{ic|1=vga=}} method will still work. Just

+

add it next to the {{ic|1="GRUB_CMDLINE_LINUX_DEFAULT="}} line in {{ic|/etc/default/grub}}

+

for eg: {{ic|1="GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=792"}} will give you a {{ic|1024x768}} resolution.

−

Then, add the below code to {{ic|/etc/grub.d/40_custom}} or {{ic|/boot/grub/custom.cfg}} and regenerate {{ic|grub.cfg}} with {{ic|grub-mkconfig}} as explained above to boot Windows (XP, Vista, 7 or 8) installed in BIOS-MBR mode:

+

You can choose one of these resolutions: {{ic|640×480}}, {{ic|800×600}}, {{ic|1024×768}}, {{ic|1280×1024}}, {{ic|1600×1200}}, {{ic|1920×1200}}

−

For Windows Vista/7/8:

+

==== 915resolution hack ====

−

menuentry "Microsoft Windows Vista/7/8 BIOS-MBR" {

+

Some times for Intel graphic adapters neither {{ic|1=# hwinfo --framebuffer}} nor {{ic|1=vbeinfo}} will show you the desired resolution. In this case you can use {{ic|915resolution}} hack. This hack will temporarily modify video BIOS and add needed resolution. See [http://915resolution.mango-lang.org/ 915resolution's home page]

{{Note| In some cases, mine I have installed GRUB before a clean Windows 8, you you cannot boot windows having an error with \boot\bcd (error code 0xc000000f). You can fix it going to Windows Recovery Console (cmd from install disk) and executing:

+

GRUB comes with support for background images and bitmap fonts in {{ic|pf2}} format. The unifont font is included in the {{Pkg|grub}} package under the filename {{ic|unicode.pf2}}, or, as only ASCII characters under the name {{ic|ascii.pf2}}.

−

x:\> "bootrec.exe /fixboot"

−

x:\> "bootrec.exe /RebuildBcd".

−

{{Warning| Do not use "bootrec.exe /Fixmbr" because it will wipe GRUB out. }}

−

}}

−

{{ic|/etc/grub.d/40_custom}} can be used as a template to create {{ic|/etc/grub.d/nn_custom}}. Where {{ic|nn}} defines the precendence, indicating the order the script is executed. The order scripts are executed determine the placement in the grub boot menu.

{{Note|{{ic|nn}} should be greater than 06 to ensure necessary scripts are executed first.}}

+

Make sure you have set up the proper [[#Setting the framebuffer resolution|framebuffer resolution]].

−

=== UEFI systems ===

+

Edit {{ic|/etc/default/grub}} like this:

+

GRUB_BACKGROUND="/boot/grub/myimage"

+

#GRUB_THEME="/path/to/gfxtheme"

+

GRUB_FONT="/path/to/font.pf2"

−

{{Note|It is well known that different motherboard manufactures implement UEFI differently. Users experiencing problems getting GRUB or EFI to work properly are encouraged to share detailed steps for hardware-specific cases where UEFI booting does not work as described below. In an effort to keep the parent [[GRUB]] article neat and tidy, see the [[GRUB EFI Examples]] page for these special cases.}}

+

{{Note|If you have installed GRUB on a separate partition, {{ic|/boot/grub/myimage}} becomes {{ic|/grub/myimage}}.}}

−

First install the {{Pkg|grub}}, {{Pkg|dosfstools}}, and {{Pkg|efibootmgr}} packages, then follow the instructions below. (The last two packages are required for EFI support in grub.)

+

[[#Generating main configuration file|Re-generate]] {{ic|grub.cfg}} to apply the changes. If adding the splash image was successful, the user will see {{ic|"Found background image..."}} in the terminal as the command is executed. If this phrase is not seen, the image information was probably not incorporated into the {{ic|grub.cfg}} file.

+

+

If the image is not displayed, check:

+

* The path and the filename in {{ic|/etc/default/grub}} are correct

+

* The image is of the proper size and format (tga, png, 8-bit jpg)

+

* The image was saved in the RGB mode, and is not indexed

+

* The console mode is not enabled in {{ic|/etc/default/grub}}

+

* The command {{ic|grub-mkconfig}} must be executed to place the background image information into the {{ic|/boot/grub/grub.cfg}} file

−

{{Note|Simply installing the package will not update the {{ic|core.efi}} file and the GRUB modules in the ESP. You need to do this manually using {{ic|grub-install}} as explained below.}}

+

==== Theme ====

−

==== Install Boot Files ====

+

Here is an example for configuring Starfield theme which was included in GRUB package.

−

===== Recommended Method =====

+

Edit {{ic|/etc/default/grub}}

+

GRUB_THEME="/usr/share/grub/themes/starfield/theme.txt"

−

{{Note|

+

[[#Generating main configuration file|Re-generate]] {{ic|grub.cfg}} to apply the changes. If configuring the theme was successful, you will see {{ic|Found theme: /usr/share/grub/themes/starfield/theme.txt}} in the terminal.

−

* The below commands assume you are using installing GRUB for {{ic|x86_64-efi}} (for {{ic|IA32-efi}} replace {{ic|x86_64-efi}} with {{ic|i386-efi}} in the below commands)

−

* To do this, you need to boot using UEFI and not BIOS. If you booted by just copying the ISO file to the USB drive, you have booted using BIOS. You will need to [[Unified Extensible Firmware Interface#Create UEFI bootable USB from ISO|create a UEFI bootable USB device]] and reboot with it or grub-install will show errors.

−

}}

−

First, mount the ESP at your preferred mountpoint (usually {{ic|/boot/efi}}, hereafter referred to as $esp). On a first install, you will need to mkdir /boot/efi, if that's where you want to mount it.

+

Your splash image will usually not be displayed when using a theme.

−

Now, install the GRUB UEFI application to {{ic|$esp/EFI/grub}} and its modules to {{ic|/boot/grub/x86_64-efi}}:

You can set the menu colors in GRUB. The available colors for GRUB can be found in [https://www.gnu.org/software/grub/manual/html_node/Theme-file-format.html the GRUB Manual].

+

Here is an example:

−

{{Note|

+

Edit {{ic|/etc/default/grub}}:

−

* Without {{ic|--target}} or {{ic|--directory}} option, grub-install cannot determine for which firmware to install. In such cases {{ic|grub-install}} will print {{ic|source_dir does not exist. Please specify --target or --directory}}.

+

GRUB_COLOR_NORMAL="light-blue/black"

−

* {{ic|--efi-directory}} and {{ic|--bootloader-id}} are specific to GRUB UEFI. {{ic|--efi-directory}} specifies the mountpoint of the ESP. It replaces {{ic|--root-directory}}, which is deprecated. {{ic|--bootloader-id}} specifies the name of the directory used to store the {{ic|grubx64.efi}} file.

+

GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

−

* If you notice carefully, there is no <device_path> option (Eg: {{ic|/dev/sda}}) at the end of the {{ic|grub-install}} command unlike the case of setting up GRUB for BIOS systems. Any <device_path> provided will be ignored by the install script, as UEFI bootloaders do not use MBR or Partition boot sectors at all.

−

}}

−

GRUB is now installed. You may proceed to [[#Configuration]].

+

==== Hidden menu ====

−

===== Alternate Method =====

+

One of the unique features of GRUB is hiding/skipping the menu and showing it by holding {{ic|Esc}} when needed. You can also adjust whether you want to see the timeout counter.

−

If you want to keep all of the GRUB boot files inside the EFI System Partition itself, add {{ic|--boot-directory&#61;$esp/EFI}} to the grub-install command:

+

Edit {{ic|/etc/default/grub}} as you wish. Here is an example where the comments from the beginning of the two lines have been removed to enable the feature, the timeout has been set to five seconds and to be shown to the user:

This puts the GRUB modules in {{ic|$esp/EFI/grub}}. ('/grub' is hard coded onto the end of this path.) Using this method, grub.cfg is kept on the EFI System Partition as well, so make sure you point grub-mkconfig to the right place in the configuration phase:

+

Users who use NVIDIA proprietary driver might wish to disable GRUB's framebuffer as it can cause problems with the binary driver.

−

# grub-mkconfig -o $esp/EFI/grub/grub.cfg

+

To disable framebuffer, edit {{ic|/etc/default/grub}} and uncomment the following line:

+

GRUB_TERMINAL_OUTPUT=console

−

Configuration is otherwise the same.

+

Another option if you want to keep the framebuffer in GRUB is to revert to text mode just before starting the kernel. To do that modify the variable in {{ic|/etc/default/grub}}:

+

GRUB_GFXPAYLOAD_LINUX=text

−

==== Create a GRUB entry in the firmware boot manager ====

+

=== Persistent block device naming ===

−

{{ic|grub-install}} automatically tries to create a menu entry in the boot manager. If it does not, then see [[Beginners' Guide#GRUB]] for instructions to use {{ic|efibootmgr}} to create a menu entry. However, the problem is likely to be that you have not booted your CD/USB in UEFI mode, as in [[Unified Extensible Firmware Interface#Create UEFI bootable USB from ISO]].

+

One naming scheme for [[Persistent block device naming]] is the use of globally unique UUIDs to detect partitions instead of the "old" {{ic|/dev/sd*}}. Advantages are covered up in the above linked article.

−

==== Create GRUB Standalone UEFI application ====

+

Persistent naming via filesystem UUIDs are used by default in GRUB.

−

It is possible to create a {{ic|grubx64_standalone.efi}} application which has all the modules embedded in a memdisk within the UEFI application, thus removing the need for having a separate directory populated with all the GRUB UEFI modules and other related files. This is done using the {{ic|grub-mkstandalone}} command which is included in {{Pkg|grub}}.

+

{{Note|The {{ic|/boot/grub.cfg}} file needs regeneration with the new UUID in {{ic|/etc/default/grub}} every time a relevant filesystem is resized or recreated. Remember this when modifying partitions & filesystems with a Live-CD.}}

−

The easiest way to do this would be with the install command already mentioned before, but specifying the modules to include. For example:

+

Whether to use UUIDs is controlled by an option in {{ic|/etc/default/grub}}:

The {{ic|grubx64_standalone.efi}} file expects {{ic|grub.cfg}} to be within its $prefix which is {{ic|(memdisk)/boot/grub}}. The memdisk is embedded within the EFI app. The {{ic|grub-mkstandlone}} script allow passing files to be included in the memdisk image to be as the arguments to the script (in <any extra files you want to include>).

+

=== Recall previous entry ===

−

If you have the {{ic|grub.cfg}} at {{ic|/home/user/Desktop/grub.cfg}}, then create a temporary {{ic|/home/user/Desktop/boot/grub/}} directory, copy the {{ic|/home/user/Desktop/grub.cfg}} to {{ic|/home/user/Desktop/boot/grub/grub.cfg}}, cd into {{ic|/home/user/Desktop/boot/grub/}} and run:

+

GRUB can remember the last entry you booted from and use this as the default entry to boot from next time. This is useful if you have multiple kernels (i.e., the current Arch one and the LTS kernel as a fallback option) or operating systems. To do this, edit {{ic|/etc/default/grub}} and change the value of {{ic|GRUB_DEFAULT}}:

The reason to {{ic|cd}} into {{ic|/home/user/Desktop/boot/grub/}} and to pass the file path as {{ic|boot/grub/grub.cfg}} (notice the lack of a leading slash - {{ic|boot/}} vs. {{ic|/boot/}} ) is because {{ic|dir1/dir2/file}} is included as {{ic|(memdisk)/dir1/dir2/file}} by the {{ic|grub-mkstandalone}} script.

+

This ensures that GRUB will default to the saved entry. To enable saving the selected entry, add the following line to {{ic|/etc/default/grub}}:

−

If you pass {{ic|/home/user/Desktop/grub.cfg}} the file will be included as {{ic|(memdisk)/home/user/Desktop/grub.cfg}}. If you pass {{ic|/home/user/Desktop/boot/grub/grub.cfg}} the file will be included as {{ic|(memdisk)/home/user/Desktop/boot/grub/grub.cfg}}. That is the reason for {{ic|cd}}'ing into {{ic|/home/user/Desktop/boot/grub/}} and passing {{ic|boot/grub/grub.cfg}}, to include the file as {{ic|(memdisk)/boot/grub/grub.cfg}}, which is what {{ic|grub.efi}} expects the file to be.

+

GRUB_SAVEDEFAULT=true

−

You need to create a UEFI Boot Manager entry for {{ic|$esp/EFI/arch_grub/grubx64_standalone.efi}} using {{ic|efibootmgr}}. Follow [[#Create GRUB entry in the Firmware Boot Manager]].

You can choose to automatically generate or manually edit {{ic|grub.cfg}}.

+

To change the default selected entry, edit {{ic|/etc/default/grub}} and change the value of {{ic|GRUB_DEFAULT}}:

−

{{Note|

+

Using numbers :

−

* For EFI systems, if GRUB was installed with the {{ic|1=--boot-directory=$esp/EFI}} option set, the {{ic|grub.cfg}} file must be placed in the same directory as {{ic|grubx64.efi}}. Otherwise, the {{ic|grub.cfg}} file goes in {{ic|/boot/grub/}}, just like in GRUB BIOS

+

GRUB_DEFAULT=0

−

* [http://members.iinet.net/~herman546/p20/GRUB2%20Configuration%20File%20Commands.html Here] is a quite complete description of how to configure GRUB

+

Grub identifies entries in generated menu counted from zero. That means 0 for the first entry which is the default value, 1 for the second and so on.

−

}}

−

=== Automatically generating using grub-mkconfig ===

+

Or using menu titles :

+

GRUB_DEFAULT='Arch Linux, with Linux core repo kernel'

−

The GRUB {{ic|menu.lst}} equivalent configuration files are {{ic|/etc/default/grub}} and {{ic|/etc/grub.d/*}}. {{ic|grub-mkconfig}} uses these files to generate {{ic|grub.cfg}}. By default the script outputs to stdout. To generate a {{ic|grub.cfg}} file run the command:

add {{ic|1=cryptdevice=/dev/yourdevice:label}} to {{ic|GRUB_CMDLINE_LINUX}} in {{ic|/etc/default/grub}}.

−

{{ic|/etc/grub.d/10_linux}} is set to automatically add menu items for Arch linux that work out of the box, to any generated configuration. Other operating systems may need to be added manually to {{ic|/etc/grub.d/40_custom}} or {{ic|/boot/grub/custom.cfg}}

+

{{Tip|If you are upgrading from a working GRUB Legacy configuration, check {{ic|/boot/grub/menu.lst.pacsave}} for the correct device/label to add. Look for them after the text {{ic|kernel /vmlinuz-linux}}.}}

−

{{Note|If you're trying to do this in a chroot or systemd-nspawn container, you might notice that it doesn't work, complaining that grub-probe can't get the 'canonical path of /dev/sdaX'. In this case, try using arch-chroot as described [https://bbs.archlinux.org/viewtopic.php?pid&#61;1225067#p1225067 here].}}

+

Example with root mapped to {{ic|/dev/mapper/root}}:

−

==== Additional arguments ====

+

GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda2:root"

−

To pass custom additional arguments to the Linux image, you can set the {{ic|GRUB_CMDLINE_LINUX}} + {{ic|GRUB_CMDLINE_LINUX_DEFAULT}} variables in {{ic|/etc/default/grub}}. The two are appended to each other when generating {{ic|grub.cfg}} for regular boot entries. For the ''recovery'' boot entry, only {{ic|GRUB_CMDLINE_LINUX}} is used in the generation.

+

Also, disable the usage of UUIDs for the rootfs:

−

It is not necessary to use both, but can be useful. For example, you could use {{ic|<nowiki>GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/sdaX</nowiki> quiet"}} where {{ic|sda'''X'''}} is your swap partition to enable resume after hibernation. This would generate a recovery boot entry without the resume and without ''quiet'' suppressing kernel messages during a boot from that menu entry. Though, the other (regular) menu entries would have them as options.

+

GRUB_DISABLE_LINUX_UUID=true

−

For generating the GRUB recovery entry you also have to comment out {{ic|<nowiki>#GRUB_DISABLE_RECOVERY=true</nowiki>}} in {{ic|/etc/default/grub}}.

+

=== Boot non-default entry only once ===

−

You can also use {{ic|<nowiki>GRUB_CMDLINE_LINUX="resume=/dev/disk/by-uuid/${swap_uuid}"</nowiki>}}, where {{ic|${swap_uuid} }} is the [[Persistent_block_device_naming|UUID]] of your swap partition.

+

The command {{ic|grub-reboot}} is very helpful to boot another entry than the default only once. GRUB loads the entry passed in the first command line argument, when the system is rebooted the next time. Most importantly GRUB returns to loading the default entry for all future booting. Changing the configuration file or selecting an entry in the GRUB menu is not necessary.

+

{{Note|This requires {{ic|1=GRUB_DEFAULT=saved}} in {{ic|/etc/default/grub}} (and then regenerating {{ic|grub.cfg}}) or, in case of hand-made {{ic|grub.cfg}}, the line {{ic|1=set default="${saved_entry}"}}.}}

−

Multiple entries are separated by spaces within the double quotes. So, for users who want both resume and systemd it would look like this:

This section covers manual editing of {{ic|grub.cfg}}, writing custom scripts in {{ic|/etc/grub.d/}} and other advanced settings.

=== Manually creating grub.cfg ===

=== Manually creating grub.cfg ===

−

{{Warning|Editing this file is strongly ''not'' recommended. The file is generated by the {{ic|grub-mkconfig}} command, and it is best to edit your {{ic|/etc/default/grub}} or one of the scripts in the {{ic|/etc/grub.d}} folder.}}

+

{{Warning|Editing this file is strongly discouraged. The file is generated by the {{ic|grub-mkconfig}} command, and it is best to edit your {{ic|/etc/default/grub}} or one of the scripts in the {{ic|/etc/grub.d}} folder.}}

* {{ic|1=set root=(hdX,Y)}} sets the boot partition, where the kernel and GRUB modules are stored (boot need not be a separate partition, and may simply be a directory under the "root" partition ({{ic|/}})

+

* {{ic|1=set root=(hd''X'',''Y'')}} sets the boot partition, where the kernel and GRUB modules are stored (boot need not be a separate partition, and may simply be a directory under the "root" partition ({{ic|/}})

An example configuration:

An example configuration:

Line 445:

Line 556:

{{Note|If you want GRUB to automatically search for other systems, you may wish to install {{Pkg|os-prober}}.}}

{{Note|If you want GRUB to automatically search for other systems, you may wish to install {{Pkg|os-prober}}.}}

For example, a typical {{ic|/etc/grub.d/40_custom}} file, could appear similar to the following one, created for [http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&destPage=product&lc=en&product=5402703&tmp_docname= HP Pavilion 15-e056sl Notebook PC], originally with Microsoft Windows 8 preinstalled. Each {{ic|menuentry}} should mantain a structure similar to the following ones. Note that the UEFI partition {{ic|/dev/sda2}} within GRUB is called {{ic|hd0,gpt2}} and {{ic|ahci0,gpt2}} (see [[#Windows Installed in UEFI-GPT Mode menu entry|here]] for more info).

+

+

'''/etc/grub.d/40_custom''':

+

+

{{bc|<nowiki>#!/bin/sh

+

exec tail -n +3 $0

+

# This file provides an easy way to add custom menu entries.&nbsp; Simply type the

+

# menu entries you want to add after this comment.&nbsp; Be careful not to change

Requires that FreeBSD is installed on a single partition with UFS. Assuming it is installed on {{ic|sda4}}:

Requires that FreeBSD is installed on a single partition with UFS. Assuming it is installed on {{ic|sda4}}:

−

menuentry "FreeBSD" {

+

{{bc|<nowiki>menuentry "FreeBSD" {

−

set root=(hd0,4)

+

set root=(hd0,4)

−

chainloader +1

+

chainloader +1

−

}

+

}</nowiki>}}

−

===== With Windows =====

+

===== Windows XP menu entry=====

This assumes that your Windows partition is {{ic|sda3}}. Remember you need to point set root and chainloader to the system reserve partition that windows made when it installed, not the actual partition windows is on. This example works if your system reserve partition is {{ic|sda3}}.

This assumes that your Windows partition is {{ic|sda3}}. Remember you need to point set root and chainloader to the system reserve partition that windows made when it installed, not the actual partition windows is on. This example works if your system reserve partition is {{ic|sda3}}.

−

# (2) Windows XP

+

{{bc|<nowiki># (2) Windows XP

−

menuentry "Windows XP" {

+

menuentry "Windows XP" {

−

set root="(hd0,3)"

+

set root="(hd0,3)"

−

chainloader +1

+

chainloader +1

−

}

+

}</nowiki>}}

If the Windows bootloader is on an entirely different hard drive than GRUB, it may be necessary to trick Windows into believing that it is the first hard drive. This was possible with {{ic|drivemap}}. Assuming GRUB is on {{ic|hd0}} and Windows is on {{ic|hd2}}, you need to add the following after {{ic|set root}}:

If the Windows bootloader is on an entirely different hard drive than GRUB, it may be necessary to trick Windows into believing that it is the first hard drive. This was possible with {{ic|drivemap}}. Assuming GRUB is on {{ic|hd0}} and Windows is on {{ic|hd2}}, you need to add the following after {{ic|set root}}:

−

drivemap -s hd0 hd2

+

{{bc|<nowiki>drivemap -s hd0 hd2</nowiki>}}

−

===== With Windows Installed in UEFI-GPT Mode =====

+

===== Windows Installed in UEFI-GPT Mode menu entry =====

−

menuentry "Microsoft Windows Vista/7/8 x86_64 UEFI-GPT" {

+

{{bc|<nowiki>if [ "${grub_platform}" == "efi" ]; then

−

insmod part_gpt

+

menuentry "Microsoft Windows Vista/7/8 x86_64 UEFI-GPT" {

−

insmod fat

+

insmod part_gpt

−

insmod search_fs_uuid

+

insmod fat

−

insmod chain

+

insmod search_fs_uuid

−

search --fs-uuid --set=root $hints_string $uuid

+

insmod chain

−

chainloader /EFI/Microsoft/Boot/bootmgfw.efi

+

search --fs-uuid --set=root $hints_string $uuid

−

}

+

chainloader /EFI/Microsoft/Boot/bootmgfw.efi

+

}

+

fi</nowiki>}}

where {{ic|$hints_string}} and {{ic|$uuid}} are obtained with the following two commands. {{ic|$uuid}}'s command:

where {{ic|$hints_string}} and {{ic|$uuid}} are obtained with the following two commands. {{ic|$uuid}}'s command:

These two commands assume the ESP Windows uses is mounted at {{ic|$esp}}. There might be case differences in the path to Windows's EFI file, what with being Windows, and all.

These two commands assume the ESP Windows uses is mounted at {{ic|$esp}}. There might be case differences in the path to Windows's EFI file, what with being Windows, and all.

−

==== With Windows via EasyBCD and NeoGRUB ====

+

===== "Shutdown" menu entry =====

−

Since EasyBCD's NeoGRUB currently does not understand the GRUB menu format, chainload to it by replacing the contents of your {{ic|C:\NST\menu.lst}} file with lines similar to the following:

+

{{bc|<nowiki>menuentry "System shutdown" {

+

echo "System shutting down..."

+

halt

+

}</nowiki>}}

−

default 0

+

===== "Restart" menu entry =====

−

timeout 1

−

title Chainload into GRUB v2

+

{{bc|<nowiki>menuentry "System restart" {

−

root (hd0,7)

+

echo "System rebooting..."

−

kernel /boot/grub/i386-pc/core.img

+

reboot

−

Finally, recreate your {{ic|grub.cfg}} using {{ic|grub-mkconfig}}.

+

}</nowiki>}}

−

=== Visual configuration ===

+

===== Windows installed in BIOS-MBR mode =====

−

In GRUB it is possible, by default, to change the look of the menu. Make sure to initialize, if not done already, GRUB graphical terminal, gfxterm, with proper video mode, gfxmode, in GRUB. This can be seen in the section [[#"No suitable mode found" error]]. This video mode is passed by GRUB to the linux kernel via 'gfxpayload' so any visual configurations need this mode in order to be in effect.

+

{{Poor writing|This section does not fit into the others, should be slimmed down a bit.}}

−

==== Setting the framebuffer resolution ====

+

{{Note|GRUB supports booting {{ic|bootmgr}} directly and chainload of partition boot sector is no longer required to boot Windows in a BIOS-MBR setup.}}

−

GRUB can set the framebuffer for both GRUB itself and the kernel. The old {{ic|1=vga=}} way is deprecated. The preferred method is editing {{ic|/etc/default/grub}} as the following sample:

+

{{Warning|It is the '''system partition''' that has {{ic|bootmgr}}, not your "real" Windows partition (usually C:). When showing all UUIDs with blkid, the system partition is the one with {{ic|LABEL&#61;"SYSTEM RESERVED"}} or {{ic|LABEL&#61;"SYSTEM"}} and is only about 100 to 200 MB in size (much like the boot partition for Arch). See [[Wikipedia:System partition and boot partition]] for more info.}}

−

GRUB_GFXMODE=1024x768x32

+

Throughout this section, it is assumed your Windows partition is {{ic|/dev/sda1}}. A different partition will change every instance of hd0,msdos1. First, find the UUID of the NTFS filesystem of the Windows's SYSTEM PARTITION where the {{ic|bootmgr}} and its files reside. For example, if Windows {{ic|bootmgr}} exists at {{ic|/media/SYSTEM_RESERVED/bootmgr}}:

−

GRUB_GFXPAYLOAD_LINUX=keep

−

To generate the changes, run:

+

For Windows Vista/7/8:

−

# grub-mkconfig -o /boot/grub/grub.cfg

−

The {{ic|gfxpayload}} property will make sure the kernel keeps the resolution.

+

# grub-probe --target=fs_uuid /media/SYSTEM_RESERVED/bootmgr

+

69B235F6749E84CE

−

{{Note|

+

# grub-probe --target=hints_string /media/SYSTEM_RESERVED/bootmgr

−

* If this example does not work for you try to replace {{ic|1=gfxmode="1024x768x32"}} by {{ic|1=vbemode="0x105"}}. Remember to replace the specified resolution with one suitable for your screen

* To show all the modes you can use {{ic|1=# hwinfo --framebuffer}} (hwinfo is available in [community]), while at GRUB prompt you can use the {{ic|1=vbeinfo}} command

−

}}

−

If this method does not work for you, the deprecated {{ic|1=vga=}} method will still work. Just

+

{{Note|For Windows XP, replace {{ic|bootmgr}} with {{ic|NTLDR}} in the above commands. And note that there may not be a separate SYSTEM_RESERVED partition; just probe the file NTLDR on your Windows partition.}}

−

add it next to the {{ic|1="GRUB_CMDLINE_LINUX_DEFAULT="}} line in {{ic|/etc/default/grub}}

−

for eg: {{ic|1="GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=792"}} will give you a {{ic|1024x768}} resolution.

−

You can choose one of these resolutions: {{ic|640×480}}, {{ic|800×600}}, {{ic|1024×768}}, {{ic|1280×1024}}, {{ic|1600×1200}}, {{ic|1920×1200}}

+

Then, add the below code to {{ic|/etc/grub.d/40_custom}} or {{ic|/boot/grub/custom.cfg}} and regenerate {{ic|grub.cfg}} with {{ic|grub-mkconfig}} as explained above to boot Windows (XP, Vista, 7 or 8) installed in BIOS-MBR mode:

−

==== 915resolution hack ====

+

For Windows Vista/7/8:

−

Some times for Intel graphic adapters neither {{ic|1=# hwinfo --framebuffer}} nor {{ic|1=vbeinfo}} will show you the desired resolution. In this case you can use {{ic|915resolution}} hack. This hack will temporarily modify video BIOS and add needed resolution. See [http://915resolution.mango-lang.org/ 915resolution's home page]

GRUB comes with support for background images and bitmap fonts in {{ic|pf2}} format. The unifont font is included in the {{Pkg|grub}} package under the filename {{ic|unicode.pf2}}, or, as only ASCII characters under the name {{ic|ascii.pf2}}.

+

{{Note|In some cases, mine I have installed GRUB before a clean Windows 8, you cannot boot Windows having an error with {{ic|\boot\bcd}} (error code {{ic|0xc000000f}}). You can fix it going to Windows Recovery Console (cmd from install disk) and executing:

+

x:\> "bootrec.exe /fixboot"

+

x:\> "bootrec.exe /RebuildBcd".

+

Do '''not''' use {{ic|bootrec.exe /Fixmbr}} because it will wipe GRUB out.}}

{{ic|/etc/grub.d/40_custom}} can be used as a template to create {{ic|/etc/grub.d/nn_custom}}. Where {{ic|nn}} defines the precendence, indicating the order the script is executed. The order scripts are executed determine the placement in the grub boot menu.

−

Make sure you have set up the proper [[#Setting the framebuffer resolution|framebuffer resolution]].

+

{{Note|{{ic|nn}} should be greater than 06 to ensure necessary scripts are executed first.}}

−

Edit {{ic|/etc/default/grub}} like this:

+

==== With Windows via EasyBCD and NeoGRUB ====

−

GRUB_BACKGROUND="/boot/grub/myimage"

−

#GRUB_THEME="/path/to/gfxtheme"

−

GRUB_FONT="/path/to/font.pf2"

−

{{Note|If you have installed GRUB on a separate partition, {{ic|/boot/grub/myimage}} becomes {{ic|/grub/myimage}}.}}

+

{{Merge|NeoGRUB|New page has been created, so this section should be merged there.}}

−

To generate the changes and add the information into {{ic|grub.cfg}}, run:

+

Since EasyBCD's NeoGRUB currently does not understand the GRUB menu format, chainload to it by replacing the contents of your {{ic|C:\NST\menu.lst}} file with lines similar to the following:

−

# grub-mkconfig -o /boot/grub/grub.cfg

−

If adding the splash image was successful, the user will see {{ic|"Found background image..."}} in the terminal as the command is executed.

+

default 0

−

If this phrase is not seen, the image information was probably not incorporated into the {{ic|grub.cfg}} file.

+

timeout 1

−

−

If the image is not displayed, check:

−

* The path and the filename in {{ic|/etc/default/grub}} are correct

−

* The image is of the proper size and format (tga, png, 8-bit jpg)

−

* The image was saved in the RGB mode, and is not indexed

−

* The console mode is not enabled in {{ic|/etc/default/grub}}

−

* The command {{ic|grub-mkconfig}} must be executed to place the background image information into the {{ic|/boot/grub/grub.cfg}} file

−

==== Theme ====

+

title Chainload into GRUB v2

+

root (hd0,7)

+

kernel /boot/grub/i386-pc/core.img

−

Here is an example for configuring Starfield theme which was included in GRUB package.

+

Finally, recreate your {{ic|grub.cfg}} using {{ic|grub-mkconfig}}.

−

Edit {{ic|/etc/default/grub}}

+

=== Booting an ISO directly from GRUB ===

−

GRUB_THEME="/usr/share/grub/themes/starfield/theme.txt"

−

Generate the changes:

+

Edit {{ic|/etc/grub.d/40_custom}} or {{ic|/boot/grub/custom.cfg}} to add an entry for the target ISO. When finished, update the GRUB menu as with the usual {{ic|grub-mkconfig -o /boot/grub/grub.cfg}} (as root).

−

# grub-mkconfig -o /boot/grub/grub.cfg

−

If configuring the theme was successful, you will see {{ic|Found theme: /usr/share/grub/themes/starfield/theme.txt}} in the terminal.

+

==== Arch ISO ====

−

Your splash image will usually not be displayed when using a theme.

−

==== Menu colors ====

+

{{Note|The following examples assume the ISO is in {{ic|/archives}} on {{ic|hd0,6}}.}}

+

{{Tip|For thumbdrives, use something like {{ic|(hd1,$partition)}} and either {{ic|/dev/sdb'''Y'''}} for the {{ic|img_dev}} parameter or [[Persistent block device naming|a persistent name]], e.g. {{ic|img_dev&#61;/dev/disk/by-label/CORSAIR}}.}}

−

You can set the menu colors in GRUB. The available colors for GRUB can be found in [https://www.gnu.org/software/grub/manual/html_node/Theme-file-format.html the GRUB Manual].

One of the unique features of GRUB is hiding/skipping the menu and showing it by holding {{ic|Esc}} when needed. You can also adjust whether you want to see the timeout counter.

+

==== Ubuntu ISO ====

−

Edit {{ic|/etc/default/grub}} as you wish. Here is an example where the comments from the beginning of the two lines have been removed to enable the feature, the timeout has been set to five seconds and to be shown to the user:

+

{{Note|The example assumes that the iso is in {{ic|/archives}} on {{ic|hd0,6}}. Users must adjust the location and hdd/partition in the lines below to match their systems.}}

Users who use NVIDIA proprietary driver might wish to disable GRUB's framebuffer as it can cause problems with the binary driver.

+

==== Other ISOs ====

−

To disable framebuffer, edit {{ic|/etc/default/grub}} and uncomment the following line:

+

Other working configurations from [http://askubuntu.com/questions/141940/how-to-boot-live-iso-images link Source].

−

GRUB_TERMINAL_OUTPUT=console

−

−

and run:

−

# grub-mkconfig -o /boot/grub/grub.cfg

−

−

Another option if you want to keep the framebuffer in GRUB is to revert to text mode just before starting the kernel. To do that modify the variable in {{ic|/etc/default/grub}}:

−

GRUB_GFXPAYLOAD_LINUX=text

−

−

and rebuild the configuration as before.

−

−

=== Other Options ===

−

==== LVM ====

+

=== LVM ===

If you use [[LVM]] for your {{ic|/boot}}, add the following before menuentry lines:

If you use [[LVM]] for your {{ic|/boot}}, add the following before menuentry lines:

Line 670:

Line 821:

}

}

−

==== RAID ====

+

=== RAID ===

GRUB provides convenient handling of RAID volumes. You need to add {{ic|insmod mdraid}} which allows you to address the volume natively. For example, {{ic|/dev/md0}} becomes:

GRUB provides convenient handling of RAID volumes. You need to add {{ic|insmod mdraid}} which allows you to address the volume natively. For example, {{ic|/dev/md0}} becomes:

Line 678:

Line 829:

set root=(md0,1)

set root=(md0,1)

−

To install grub when using raid1 as the /boot partition (or using /boot housed on a raid1 root partition), on devices with GPT ef02/'BIOS boot partition', simply run grub-install on both of the drives, such as:

+

To install grub when using RAID1 as the {{ic|/boot}} partition (or using {{ic|/boot}} housed on a RAID1 root partition), on devices with GPT ef02/'BIOS boot partition', simply run ''grub-install'' on both of the drives, such as:

Where the raid1 array housing /boot is housed on /dev/sda and /dev/sdb.

+

# grub-install --target=i386-pc --recheck --debug /dev/sdb

−

−

==== Persistent block device naming ====

−

One naming scheme for [[Persistent block device naming]] is the use of globally unique UUIDs to detect partitions instead of the "old" {{ic|/dev/sd*}}. Advantages are covered up in the above linked article.

−

Persistent naming via filesystem UUIDs are used by default in GRUB.

+

Where the RAID1 array housing {{ic|/boot}} is housed on {{ic|/dev/sda}} and {{ic|/dev/sdb}}.

−

{{Note|The {{ic|/boot/grub.cfg}} file needs regeneration with the new UUID in {{ic|/etc/default/grub}} every time a relevant filesystem is resized or recreated. Remember this when modifying partitions & filesystems with a Live-CD.}}

+

=== Using labels ===

−

−

Whether to use UUIDs is controlled by an option in {{ic|/etc/default/grub}}:

−

−

# GRUB_DISABLE_LINUX_UUID=true

−

−

Either way, do not forget to generate the changes:

−

# grub-mkconfig -o /boot/grub/grub.cfg

−

−

==== Using Labels ====

It is possible to use labels, human-readable strings attached to filesystems, by using the {{ic|--label}} option to {{ic|search}}. First of all, label your existing partition:

It is possible to use labels, human-readable strings attached to filesystems, by using the {{ic|--label}} option to {{ic|search}}. First of all, label your existing partition:

−

# tune2fs -L <LABEL> <PARTITION>

+

# tune2fs -L ''LABEL'' ''PARTITION''

Then, add an entry using labels. An example of this:

Then, add an entry using labels. An example of this:

Line 709:

Line 848:

}

}

−

==== Recall previous entry ====

+

=== Password protection of GRUB menu ===

−

−

GRUB can remember the last entry you booted from and use this as the default entry to boot from next time. This is useful if you have multiple kernels (i.e., the current Arch one and the LTS kernel as a fallback option) or operating systems. To do this, edit {{ic|/etc/default/grub}} and change the value of {{ic|GRUB_DEFAULT}}:

−

−

GRUB_DEFAULT=saved

−

−

This ensures that GRUB will default to the saved entry. To enable saving the selected entry, add the following line to {{ic|/etc/default/grub}}:

If you want to secure GRUB so it is not possible for anyone to change boot parameters or use the command line, you can add a user/password combination to GRUB's configuration files. To do this, run the command {{ic|grub-mkpasswd-pbkdf2}}. Enter a password and confirm it:

If you want to secure GRUB so it is not possible for anyone to change boot parameters or use the command line, you can add a user/password combination to GRUB's configuration files. To do this, run the command {{ic|grub-mkpasswd-pbkdf2}}. Enter a password and confirm it:

add {{ic|1=cryptdevice=/dev/yourdevice:label}} to {{ic|GRUB_CMDLINE_LINUX}} in {{ic|/etc/default/grub}}.

−

−

{{Tip|If you are upgrading from a working GRUB Legacy configuration, check {{ic|/boot/grub/menu.lst.pacsave}} for the correct device/label to add. Look for them after the text {{ic|kernel /vmlinuz-linux}}.}}

−

−

Example with root mapped to {{ic|/dev/mapper/root}}:

−

−

GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda2:root"

−

−

Also, disable the usage of UUIDs for the rootfs:

−

−

GRUB_DISABLE_LINUX_UUID=true

−

−

Regenerate the configuration.

−

−

==== Boot non-default entry only once ====

−

−

The command {{ic|grub-reboot}} is very helpful to boot another entry than the default only once. GRUB loads the entry passed in the first command line argument, when the system is rebooted the next time. Most importantly GRUB returns to loading the default entry for all future booting. Changing the configuration file or selecting an entry in the GRUB menu is not necessary.

−

{{Note|This requires {{ic|1=GRUB_DEFAULT=saved}} in {{ic|/etc/default/grub}} (and then regenerating {{ic|grub.cfg}}) or, in case of hand-made {{ic|grub.cfg}}, the line {{ic|1=set default="${saved_entry}"}}.}}

−

−

==== Hide GRUB unless the Shift key is held down ====

In order to achieve the fastest possible boot, instead of having GRUB wait for a timeout, it is possible for GRUB to hide the menu, unless the {{ic|Shift}} key is held down during GRUB's start-up.

In order to achieve the fastest possible boot, instead of having GRUB wait for a timeout, it is possible for GRUB to hide the menu, unless the {{ic|Shift}} key is held down during GRUB's start-up.

Line 789:

Line 884:

And the following file should be created:

And the following file should be created:

−

{{hc|/etc/grub.d/31_hold_shift|

+

{{hc|/etc/grub.d/31_hold_shift|<nowiki>

−

<nowiki>

#! /bin/sh

#! /bin/sh

set -e

set -e

Line 816:

Line 910:

export TEXTDOMAIN=grub

export TEXTDOMAIN=grub

export TEXTDOMAINDIR="${datarootdir}/locale"

export TEXTDOMAINDIR="${datarootdir}/locale"

−

+

source "${datarootdir}/grub/grub-mkconfig_lib"

−

. "${datarootdir}/grub/grub-mkconfig_lib"

found_other_os=

found_other_os=

Line 891:

Line 984:

fi

fi

EOF

EOF

−

</nowiki>

+

</nowiki>}}

−

}}

−

=== Booting an ISO directly from GRUB ===

+

=== Combining the use of UUIDs and basic scripting ===

−

Edit {{ic|/etc/grub.d/40_custom}} or {{ic|/boot/grub/custom.cfg}} to add an entry for the target ISO. When finished, update the GRUB menu as with the usual {{ic|grub-mkconfig -o /boot/grub/grub.cfg}} (as root).

+

If you like the idea of using UUIDs to avoid unreliable BIOS mappings or are struggling with GRUB's syntax, here is an example boot menu item that uses UUIDs and a small script to direct GRUB to the proper disk partitions for your system. All you need to do is replace the UUIDs in the sample with the correct UUIDs for your system. The example applies to a system with a boot and root partition. You will obviously need to modify the GRUB configuration if you have additional partitions:

−

==== Arch ISO ====

+

{{bc|<nowiki>

+

menuentry "Arch Linux 64" {

+

# Set the UUIDs for your boot and root partition respectively

+

set the_boot_uuid=ece0448f-bb08-486d-9864-ac3271bd8d07

+

set the_root_uuid=c55da16f-e2af-4603-9e0b-03f5f565ec4a

−

{{Note|The following examples assume the ISO is in {{ic|/archives}} on {{ic|hd0,6}}.}}

+

# (Note: This may be the same as your boot partition)

−

{{Tip|For thumbdrives, use something like {{ic|(hd1,$partition)}} and either {{ic|/dev/sdb'''Y'''}} for the {{ic|img_dev}} parameter or [[Persistent_block_device_naming|a persistent name]], e.g. {{ic|img_dev&#61;/dev/disk/by-label/CORSAIR}}.}}

−

===== x86_64 =====

+

# Get the boot/root devices and set them in the root and grub_boot variables

+

search --fs-uuid $the_root_uuid --set=root

+

search --fs-uuid $the_boot_uuid --set=grub_boot

−

menuentry "Archlinux-2013.05.01-dual.iso" --class iso {

+

# Check to see if boot and root are equal.

−

set isofile="/archives/archlinux-2013.05.01-dual.iso"

+

# If they are, then append /boot to $grub_boot (Since $grub_boot is actually the root partition)

Other working configurations from [http://askubuntu.com/questions/141940/how-to-boot-live-iso-images link Source].

== Using the command shell ==

== Using the command shell ==

Line 964:

Line 1,035:

GRUB supports pager for reading commands that provide long output (like the {{ic|help}} command). This works only in normal shell mode and not in rescue mode. To enable pager, in GRUB command shell type:

GRUB supports pager for reading commands that provide long output (like the {{ic|help}} command). This works only in normal shell mode and not in rescue mode. To enable pager, in GRUB command shell type:

sh:grub> set pager=1

sh:grub> set pager=1

+

+

=== Using the command shell environment to boot operating systems ===

+

+

grub>

+

+

The GRUB's command shell environemnt can be used to boot operating systems.

+

A common scenario may be to boot Windows / Linux stored on a drive/partition via '''chainloading'''.

+

+

''Chainloading'' means to load another boot-loader from the current one, ie, chain-loading.

+

+

The other bootloader may be embedded at the starting of the disk(MBR) or at the starting of a partition.

+

+

==== Chainloading a partition ====

+

+

set root=(hdX,Y)

+

chainloader +1

+

boot

+

+

X=0,1,2...

+

Y=1,2,3...

+

+

For example to chainload Windows stored in the first partiton of the first hard disk,

+

+

set root=(hd0,1)

+

chainloader +1

+

boot

+

+

Similarly GRUB installed to a partition can be chainloaded.

+

+

==== Chainloading a disk/drive ====

+

+

set root=hdX

+

chainloader +1

+

boot

+

+

==== Normal loading ====

+

+

See the examples in [[Grub#Using_the_rescue_console|#Using_the_rescue_console]]

This introduces the {{ic|linux}} and {{ic|initrd}} commands, which should be familiar (see [[#Configuration]]).

+

This introduces the {{ic|linux}} and {{ic|initrd}} commands, which should be familiar (see [[#Advanced configuration]]).

An example, booting Arch Linux:

An example, booting Arch Linux:

Line 1,015:

Line 1,124:

After successfully booting the Arch Linux installation, users can correct {{ic|grub.cfg}} as needed and then reinstall GRUB.

After successfully booting the Arch Linux installation, users can correct {{ic|grub.cfg}} as needed and then reinstall GRUB.

−

To reinstall GRUB and fix the problem completely, changing {{ic|/dev/sda}} if needed. See [[#Bootloader installation]] for details.

+

To reinstall GRUB and fix the problem completely, changing {{ic|/dev/sda}} if needed. See [[#Installation]] for details.

−

−

== Combining the use of UUIDs and basic scripting ==

−

−

If you like the idea of using UUIDs to avoid unreliable BIOS mappings or are struggling with GRUB's syntax, here is an example boot menu item that uses UUIDs and a small script to direct GRUB to the proper disk partitions for your system. All you need to do is replace the UUIDs in the sample with the correct UUIDs for your system. The example applies to a system with a boot and root partition. You will obviously need to modify the GRUB configuration if you have additional partitions:

−

−

menuentry "Arch Linux 64" {

−

# Set the UUIDs for your boot and root partition respectively

−

set the_boot_uuid=ece0448f-bb08-486d-9864-ac3271bd8d07

−

set the_root_uuid=c55da16f-e2af-4603-9e0b-03f5f565ec4a

−

−

# (Note: This may be the same as your boot partition)

−

−

# Get the boot/root devices and set them in the root and grub_boot variables

−

search --fs-uuid $the_root_uuid --set=root

−

search --fs-uuid $the_boot_uuid --set=grub_boot

−

−

# Check to see if boot and root are equal.

−

# If they are, then append /boot to $grub_boot (Since $grub_boot is actually the root partition)

−

if [ $the_boot_uuid == $the_root_uuid ] ; then

−

set grub_boot=($grub_boot)/boot

−

else

−

set grub_boot=($grub_boot)

−

fi

−

−

# $grub_boot now points to the correct location, so the following will properly find the kernel and initrd

Some have reported that other distributions have trouble finding Arch Linux automatically with {{ic|os-prober}}. If this problem arises, it has been reported that detection can be improved with the presence of {{ic|/etc/lsb-release}}. This file and updating tool is available with the package {{pkg|lsb-release}} in the [[Official Repositories|official repositories]].

−

== References ==

+

Some have reported that other distributions have trouble finding Arch Linux automatically with {{ic|os-prober}}. If this problem arises, it has been reported that detection can be improved with the presence of {{ic|/etc/lsb-release}}. This file and updating tool is available with the package {{Pkg|lsb-release}} in the [[official repositories]].

Revision as of 20:00, 25 November 2013

GRUB - not to be confused with GRUB Legacy - is the next generation of the GRand Unified Bootloader. GRUB is derived from PUPA which was a research project to develop the next generation of what is now GRUB Legacy. GRUB has been rewritten from scratch to clean up everything and provide modularity and portability [1].

In brief, the bootloader is the first software program that runs when a computer starts. It is responsible for loading and transferring control to the Linux kernel. The kernel, in turn, initializes the rest of the operating system.

Preface

The name GRUB officially refers to version 2 of the software, see [2]. If you are looking for the article on the legacy version, see GRUB Legacy.

GRUB supports Btrfs as root (without a separate /boot filesystem) compressed with either zlib or LZO

GRUB does not support F2fs as root so you will need a separate /boot with a supported filesystem.

Notes for GRUB Legacy users

Upgrading from GRUB Legacy to GRUB is much the same as freshly installing GRUB. This topic is covered here.

There are differences in the commands of GRUB Legacy and GRUB. Familiarize yourself with GRUB commands before proceeding (e.g. "find" has been replaced with "search").

GRUB is now modular and no longer requires "stage 1.5". As a result, the bootloader itself is limited -- modules are loaded from the hard drive as needed to expand functionality (e.g. for LVM or RAID support).

Device naming has changed between GRUB Legacy and GRUB. Partitions are numbered from 1 instead of 0 while drives are still numbered from 0, and prefixed with partition-table type. For example, /dev/sda1 would be referred to as (hd0,msdos1) (for MBR) or (hd0,gpt1) (for GPT).

GRUB is noticeably bigger than GRUB legacy (occupies ~13 MB in /boot). If you are booting from a separate /boot partition, and this partition is smaller than 32 MB, you will run into disk space issues, and pacman will refuse to install new kernels.

Backup important data

Although a GRUB installation should run smoothly, it is strongly recommended to keep the GRUB Legacy files before upgrading to GRUB v2.

Only 446 bytes of the MBR contain boot code, the next 64 contain the partition table. If you do not want to overwrite your partition table when restoring, it is strongly advised to backup only the MBR boot code:

Preliminary requirements

BIOS systems

GUID Partition Table (GPT) specific instructions

GRUB in BIOS-GPT configuration requires a BIOS boot partition to embed its core.img in the absence of post-MBR gap in GPT partitioned systems (which is taken over by the GPT Primary Header and Primary Partition table). This partition is used by GRUB only in BIOS-GPT setups. No such partition type exists in case of MBR partitioning (at least not for GRUB). This partition is also not required if the system is UEFI based, as no embedding of bootsectors takes place in that case.

For a BIOS-GPT configuration, create a 1007 KiB partition at the beginning of the disk using gdisk, cgdisk or GNU Parted with no filesystem. The size of 1007 KiB will allow for the following partition to be correctly alligned at 1024 KiB. If needed, the partition can also be located somewhere else on the disk, but it should be within the first 2 TiB region. Set the partition type to ef02 in (c)gdisk or set BOOT_PART_NUM bios_grub on in GNU Parted.

The GPT partition also creates a protective MBR partition to stop unsupported tools from modifying it. You may need to set a bootable flag on this protective MBR e.g., using cfdisk, or some BIOSes/EFIs will refuse to boot.

Note:

This partition should be created before grub-install or grub-setup is run

gdisk will only allow you to create this partition on the position which will waste the least amount of space (sector 34-2047) if you create it last, after all the other partitions. This is because gdisk will auto-align partitions to 2048-sector boundaries if possible

Master Boot Record (MBR) specific instructions

Usually the post-MBR gap (after the 512 byte MBR region and before the start of the 1st partition) in many MBR (or msdos disklabel) partitioned systems is 31 KiB when DOS compatibility cylinder alignment issues are satisfied in the partition table. However a post-MBR gap of about 1 to 2 MiB is recommended to provide sufficient room for embedding GRUB's core.img (FS#24103). It is advisable to use a partitioner which supports 1 MiB partition alignment to obtain this space as well as satisfy other non-512 byte sector issues (which are unrelated to embedding of core.img).

UEFI systems

Check if you have GPT and an ESP

An EFI System Partition (ESP) is needed on every disc you wan to boot using EFI. GPT is not strictly necessary, but it is highly recommended and is the only method currently supported in this article. If you are installing Archlinux on an EFI-capable computer with an already-working operating system, like Windows 8 for example, it is very likely that you already have an ESP. To check for GPT and for an ESP, use parted as root to print the partition table of the disk you want to boot from. (We are calling it /dev/sda.)

# parted /dev/sda print

For GPT, you are looking for "Partition Table: GPT". For EFI, you are looking for a small (512 MiB or less) partition with a vfat filesystem and the 'boot' flag enabled. On it, there should be a folder called "EFI". If these criteria are met, this is your ESP. Make note of the partition number. You will need to know which one it is so you can mount it later on while installing GRUB to it.

Installation

BIOS systems

Note: Simply installing the package will not update the /boot/grub/i386-pc/core.img file and the GRUB modules in /boot/grub/i386-pc. You need to update them manually using grub-install as explained below.

Before installing, make sure the correct UUIDs of your disks are inserted into grub.cfg:

Install to disk

Note: The method is specific to installing GRUB to a partitioned (MBR or GPT) disk, with GRUB files installed to /boot/grub and its first stage code installed to the 440-byte MBR boot code region (not to be confused with MBR partition table). For partitionless disk (super-floppy) please refer to #Install to partition or partitionless disk

--target=i386-pc instructs grub-install to install for BIOS systems only. It is recommended to always use this option to remove ambiguity in grub-install.

If you use LVM for your /boot, you can install GRUB on multiple physical disks.

Install to partition or partitionless disk

Note: GRUB does not encourage installation to a partition boot sector or a partitionless disk like GRUB Legacy or Syslinux does. This kind of setup is prone to breakage, especially during updates, and is not supported by Arch devs.

To set up grub to a partition boot sector, to a partitionless disk (also called superfloppy) or to a floppy disk, run (using for example /dev/sdaX as the /boot partition):

--target=i386-pc instructs grub-install to install for BIOS systems only. It is recommended to always use this option to remove ambiguity in grub-install.

You need to use the --force option to allow usage of blocklists and should not use --grub-setup=/bin/true (which is similar to simply generating core.img).

grub-install will give out warnings like which should give you the idea of what might go wrong with this approach:

/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea.
/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists.
However, blocklists are UNRELIABLE and their use is discouraged.

Without --force you may get the below error and grub-setup will not setup its boot code in the partition boot sector:

/sbin/grub-setup: error: will not proceed with blocklists

With --force you should get:

Installation finished. No error reported.

The reason why grub-setup does not by default allow this is because in case of partition or a partitionless disk is that grub relies on embedded blocklists in the partition bootsector to locate the /boot/grub/i386-pc/core.img file and the prefix dir /boot/grub. The sector locations of core.img may change whenever the filesystem in the partition is being altered (files copied, deleted etc.). For more info see https://bugzilla.redhat.com/show_bug.cgi?id=728742 and https://bugzilla.redhat.com/show_bug.cgi?id=730915.

The workaround for this is to set the immutable flag on /boot/grub/i386-pc/core.img (using chattr command as mentioned above) so that the sector locations of the core.img file in the disk is not altered. The immutable flag on /boot/grub/i386-pc/core.img needs to be set only if grub is installed to a partition boot sector or a partitionless disk, not in case of installation to MBR or simple generation of core.img without embedding any bootsector (mentioned above).

Generate core.img alone

To populate the /boot/grub directory and generate a /boot/grub/i386-pc/core.img file without embedding any grub bootsector code in the MBR, post-MBR region, or the partition bootsector, add --grub-setup=/bin/true to grub-install:

--target=i386-pc instructs grub-install to install for BIOS systems only. It is recommended to always use this option to remove ambiguity in grub-install.

You can then chainload GRUB's core.img from GRUB Legacy or syslinux as a Linux kernel or as a multiboot kernel.

UEFI systems

Note: It is well known that different motherboard manufactures implement UEFI differently. Users experiencing problems getting GRUB or EFI to work properly are encouraged to share detailed steps for hardware-specific cases where UEFI booting does not work as described below. In an effort to keep the parent GRUB article neat and tidy, see the GRUB EFI Examples page for these special cases.

First install the grub, dosfstools, and efibootmgr packages, then follow the instructions below. (The last two packages are required for EFI support in grub.)

Note: Simply installing the package will not update the core.efi file and the GRUB modules in the ESP. You need to do this manually using grub-install as explained below.

Install boot files

Recommended method

Note:

The below commands assume you are using installing GRUB for x86_64-efi (for IA32-efi replace x86_64-efi with i386-efi in the below commands)

To do this, you need to boot using UEFI and not BIOS. If you booted by just copying the ISO file to the USB drive, you have booted using BIOS. You will need to create a UEFI bootable USB device and reboot with it or grub-install will show errors.

First, mount the ESP at your preferred mountpoint (usually /boot/efi, hereafter referred to as $esp). On a first install, you will need to mkdir /boot/efi, if that's where you want to mount it.

Now, install the GRUB UEFI application to $esp/EFI/grub and its modules to /boot/grub/x86_64-efi:

Without --target or --directory option, grub-install cannot determine for which firmware to install. In such cases grub-install will print source_dir does not exist. Please specify --target or --directory.

--efi-directory and --bootloader-id are specific to GRUB UEFI. --efi-directory specifies the mountpoint of the ESP. It replaces --root-directory, which is deprecated. --bootloader-id specifies the name of the directory used to store the grubx64.efi file.

If you notice carefully, there is no <device_path> option (Eg: /dev/sda) at the end of the grub-install command unlike the case of setting up GRUB for BIOS systems. Any <device_path> provided will be ignored by the install script, as UEFI bootloaders do not use MBR or Partition boot sectors at all.

GRUB is now installed.

Alternative method

If you want to keep all of the GRUB boot files inside the EFI System Partition itself, add --boot-directory=$esp/EFI to the grub-install command:

This puts the GRUB modules in $esp/EFI/grub. ('/grub' is hard coded onto the end of this path.) Using this method, grub.cfg is kept on the EFI System Partition as well, so make sure you point grub-mkconfig to the right place in the configuration phase:

# grub-mkconfig -o $esp/EFI/grub/grub.cfg

Configuration is otherwise the same.

Create a GRUB entry in the firmware boot manager

grub-install automatically tries to create a menu entry in the boot manager. If it does not, then see Beginners' Guide#GRUB for instructions to use efibootmgr to create a menu entry. However, the problem is likely to be that you have not booted your CD/USB in UEFI mode, as in UEFI#Create UEFI bootable USB from ISO.

GRUB Standalone

Note: Use grub-gitAUR pkg for standalone GRUB EFI image as the grub pkg does not contain various grub-mkstandalone specific fixes (specifically ${cmdpath} support, which is necessary).

It is possible to create a grubx64_standalone.efi application which has all the modules embedded in a tar archive within the UEFI application, thus removing the need for having a separate directory populated with all the GRUB UEFI modules and other related files. This is done using the grub-mkstandalone command (included in grub) as follows"

Note: The option --modules="part_gpt part_msdos" (with the quotes) is necessary for ${cmdpath} feature to work properly.

Then copy the GRUB config file to $esp/EFI/grub/grub.cfg and create a UEFI Boot Manager entry for $esp/EFI/grub/grubx64_standalone.efi using efibootmgr.

GRUB Standalone - Technical Info

The GRUB EFI file always expects its config file to be at ${prefix}/grub.cfg. However in the standalone GRUB EFI file, the ${prefix} is located inside a tar archive and embedded inside the standalone GRUB EFI file itself (inside grub env it is denoted by "(memdisk)", without quotes). This tar archive contains all the files that would be stored normally at /boot/grub in case of a normal GRUB EFI install.

Due to this embedding of /boot/grub contents inside the standalone image itself, it does not rely on actual (external) /boot/grub for anything. Thus in case of standalone GRUB EFI file ${prefix}==(memdisk)/boot/grub and the standalone GRUB EFI file reads expects the config file to be at ${prefix}/grub.cfg==(memdisk)/boot/grub/grub.cfg.

Hence to make sure the standalone GRUB EFI file reads the external grub.cfg located in the same dir as the EFI file (inside grub env it is denoted by ${cmdpath}), we create a simple /tmp/grub.cfg which instructs GRUB to use ${cmdpath}/grub.cfg as its config (configfile ${cmdpath}/grub.cfg command in (memdisk)/boot/grub/grub.cfg). We then instruct grub-mkstandalone to copy this /tmp/grub.cfg file to ${prefix}/grub.cfg (which is actually (memdisk)/boot/grub/grub.cfg) using the option "/boot/grub/grub.cfg=/tmp/grub.cfg".

This way the standalone GRUB EFI file and actual grub.cfg can be stored in any dir inside the EFI System Partition (as long as they are in the same dir), thus making them portable.

Generating main configuration file

After the installation, the main configuration file grub.cfg needs to be generated. The generation process can be influenced by a variety of options in /etc/default/grub and scripts in /etc/grub.d/, this is covered in the #Basic configuration and #Advanced configuration sections.

Note: Remember that grub.cfg has to be re-generated after any change to /etc/default/grub or /etc/grub.d/*.

Use the grub-mkconfig tool to generate grub.cfg:

# grub-mkconfig -o /boot/grub/grub.cfg

Note:

The file path for BIOS systems is /boot/grub/grub.cfg, NOT /boot/grub/i386-pc/grub.cfg.

For EFI systems, if GRUB was installed with the --boot-directory=$esp/EFI option set, the grub.cfg file must be placed in the same directory as grubx64.efi. Otherwise, the grub.cfg file goes in /boot/grub/, just like in BIOS systems.

If you are trying to run grub-mkconfig in a chroot or systemd-nspawn container, you might notice that it does not work, complaining that grub-probe cannot get the "canonical path of /dev/sdaX". In this case, try using arch-chroot as described here.

By default the generation scripts automatically add menu entries for Arch Linux to any generated configuration. However, entries for other operating systems do not work out of the box. On BIOS systems, you may want to install os-prober, which detects other operating systems installed on your machine and adds entries for them into grub.cfg. It can detect only systems on mounted partitions, so mount them before running grub-mkconfig. See #Dual-booting for advanced configuration.

Additional arguments

To pass custom additional arguments to the Linux image, you can set the GRUB_CMDLINE_LINUX + GRUB_CMDLINE_LINUX_DEFAULT variables in /etc/default/grub. The two are appended to each other and passed to kernel when generating regular boot entries. For the recovery boot entry, only GRUB_CMDLINE_LINUX is used in the generation.

It is not necessary to use both, but can be useful. For example, you could use GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/sdaX quiet" where sdaX is your swap partition to enable resume after hibernation. This would generate a recovery boot entry without the resume and without quiet suppressing kernel messages during a boot from that menu entry. Though, the other (regular) menu entries would have them as options.

For generating the GRUB recovery entry you also have to comment out #GRUB_DISABLE_RECOVERY=true in /etc/default/grub.

You can also use GRUB_CMDLINE_LINUX="resume=/dev/disk/by-uuid/${swap_uuid}", where ${swap_uuid} is the UUID of your swap partition.

Multiple entries are separated by spaces within the double quotes. So, for users who want both resume and systemd it would look like this:
GRUB_CMDLINE_LINUX="resume=/dev/sdaX init=/usr/lib/systemd/systemd"

Visual configuration

In GRUB it is possible, by default, to change the look of the menu. Make sure to initialize, if not done already, GRUB graphical terminal, gfxterm, with proper video mode, gfxmode, in GRUB. This can be seen in the section #"No suitable mode found" error. This video mode is passed by GRUB to the linux kernel via 'gfxpayload' so any visual configurations need this mode in order to be in effect.

Setting the framebuffer resolution

GRUB can set the framebuffer for both GRUB itself and the kernel. The old vga= way is deprecated. The preferred method is editing /etc/default/grub as the following sample:

GRUB_GFXMODE=1024x768x32
GRUB_GFXPAYLOAD_LINUX=keep

To generate the changes, run:

# grub-mkconfig -o /boot/grub/grub.cfg

The gfxpayload property will make sure the kernel keeps the resolution.

Note:

If this example does not work for you try to replace gfxmode="1024x768x32" by vbemode="0x105". Remember to replace the specified resolution with one suitable for your screen

To show all the modes you can use # hwinfo --framebuffer (hwinfo is available in [community]), while at GRUB prompt you can use the vbeinfo command

If this method does not work for you, the deprecated vga= method will still work. Just
add it next to the "GRUB_CMDLINE_LINUX_DEFAULT=" line in /etc/default/grub
for eg: "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=792" will give you a 1024x768 resolution.

You can choose one of these resolutions: 640×480, 800×600, 1024×768, 1280×1024, 1600×1200, 1920×1200

915resolution hack

Some times for Intel graphic adapters neither # hwinfo --framebuffer nor vbeinfo will show you the desired resolution. In this case you can use 915resolution hack. This hack will temporarily modify video BIOS and add needed resolution. See 915resolution's home page

First you need to find a video mode which will be modified later. For that we need the GRUB command shell:

Lastly we need to set GRUB_GFXMODE as described earlier, regenerate grub.cfg and reboot to test changes.

Background image and bitmap fonts

GRUB comes with support for background images and bitmap fonts in pf2 format. The unifont font is included in the grub package under the filename unicode.pf2, or, as only ASCII characters under the name ascii.pf2.

Note: If you have installed GRUB on a separate partition, /boot/grub/myimage becomes /grub/myimage.

Re-generategrub.cfg to apply the changes. If adding the splash image was successful, the user will see "Found background image..." in the terminal as the command is executed. If this phrase is not seen, the image information was probably not incorporated into the grub.cfg file.

If the image is not displayed, check:

The path and the filename in /etc/default/grub are correct

The image is of the proper size and format (tga, png, 8-bit jpg)

The image was saved in the RGB mode, and is not indexed

The console mode is not enabled in /etc/default/grub

The command grub-mkconfig must be executed to place the background image information into the /boot/grub/grub.cfg file

Theme

Here is an example for configuring Starfield theme which was included in GRUB package.

Edit /etc/default/grub

GRUB_THEME="/usr/share/grub/themes/starfield/theme.txt"

Re-generategrub.cfg to apply the changes. If configuring the theme was successful, you will see Found theme: /usr/share/grub/themes/starfield/theme.txt in the terminal.

Your splash image will usually not be displayed when using a theme.

Menu colors

You can set the menu colors in GRUB. The available colors for GRUB can be found in the GRUB Manual.
Here is an example:

Hidden menu

One of the unique features of GRUB is hiding/skipping the menu and showing it by holding Esc when needed. You can also adjust whether you want to see the timeout counter.

Edit /etc/default/grub as you wish. Here is an example where the comments from the beginning of the two lines have been removed to enable the feature, the timeout has been set to five seconds and to be shown to the user:

GRUB_HIDDEN_TIMEOUT=5
GRUB_HIDDEN_TIMEOUT_QUIET=false

Disable framebuffer

Users who use NVIDIA proprietary driver might wish to disable GRUB's framebuffer as it can cause problems with the binary driver.

To disable framebuffer, edit /etc/default/grub and uncomment the following line:

GRUB_TERMINAL_OUTPUT=console

Another option if you want to keep the framebuffer in GRUB is to revert to text mode just before starting the kernel. To do that modify the variable in /etc/default/grub:

GRUB_GFXPAYLOAD_LINUX=text

Persistent block device naming

One naming scheme for Persistent block device naming is the use of globally unique UUIDs to detect partitions instead of the "old" /dev/sd*. Advantages are covered up in the above linked article.

Persistent naming via filesystem UUIDs are used by default in GRUB.

Note: The /boot/grub.cfg file needs regeneration with the new UUID in /etc/default/grub every time a relevant filesystem is resized or recreated. Remember this when modifying partitions & filesystems with a Live-CD.

Whether to use UUIDs is controlled by an option in /etc/default/grub:

GRUB_DISABLE_LINUX_UUID=true

Recall previous entry

GRUB can remember the last entry you booted from and use this as the default entry to boot from next time. This is useful if you have multiple kernels (i.e., the current Arch one and the LTS kernel as a fallback option) or operating systems. To do this, edit /etc/default/grub and change the value of GRUB_DEFAULT:

GRUB_DEFAULT=saved

This ensures that GRUB will default to the saved entry. To enable saving the selected entry, add the following line to /etc/default/grub:

Root encryption

Tip: If you are upgrading from a working GRUB Legacy configuration, check /boot/grub/menu.lst.pacsave for the correct device/label to add. Look for them after the text kernel /vmlinuz-linux.

Example with root mapped to /dev/mapper/root:

GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda2:root"

Also, disable the usage of UUIDs for the rootfs:

GRUB_DISABLE_LINUX_UUID=true

Boot non-default entry only once

The command grub-reboot is very helpful to boot another entry than the default only once. GRUB loads the entry passed in the first command line argument, when the system is rebooted the next time. Most importantly GRUB returns to loading the default entry for all future booting. Changing the configuration file or selecting an entry in the GRUB menu is not necessary.

Note: This requires GRUB_DEFAULT=saved in /etc/default/grub (and then regenerating grub.cfg) or, in case of hand-made grub.cfg, the line set default="${saved_entry}".

Advanced configuration

This section covers manual editing of grub.cfg, writing custom scripts in /etc/grub.d/ and other advanced settings.

Manually creating grub.cfg

Warning: Editing this file is strongly discouraged. The file is generated by the grub-mkconfig command, and it is best to edit your /etc/default/grub or one of the scripts in the /etc/grub.d folder.

Dual-booting

Note: If you want GRUB to automatically search for other systems, you may wish to install os-prober.

Automatically generating using /etc/grub.d/40_custom and grub-mkconfig

The best way to add other entries is editing the /etc/grub.d/40_custom or /boot/grub/custom.cfg. The entries in this file will be automatically added when running grub-mkconfig.
After adding the new lines, run:

# grub-mkconfig -o /boot/grub/grub.cfg

or, for UEFI-GPT Mode:

# grub-mkconfig -o /boot/efi/EFI/GRUB/grub.cfg

to generate an updated grub.cfg.

For example, a typical /etc/grub.d/40_custom file, could appear similar to the following one, created for HP Pavilion 15-e056sl Notebook PC, originally with Microsoft Windows 8 preinstalled. Each menuentry should mantain a structure similar to the following ones. Note that the UEFI partition /dev/sda2 within GRUB is called hd0,gpt2 and ahci0,gpt2 (see here for more info).

FreeBSD menu entry

Requires that FreeBSD is installed on a single partition with UFS. Assuming it is installed on sda4:

menuentry "FreeBSD" {
set root=(hd0,4)
chainloader +1
}

Windows XP menu entry

This assumes that your Windows partition is sda3. Remember you need to point set root and chainloader to the system reserve partition that windows made when it installed, not the actual partition windows is on. This example works if your system reserve partition is sda3.

If the Windows bootloader is on an entirely different hard drive than GRUB, it may be necessary to trick Windows into believing that it is the first hard drive. This was possible with drivemap. Assuming GRUB is on hd0 and Windows is on hd2, you need to add the following after set root:

"Restart" menu entry

Windows installed in BIOS-MBR mode

Reason: This section does not fit into the others, should be slimmed down a bit. (Discuss in Talk:GRUB#)

Note: GRUB supports booting bootmgr directly and chainload of partition boot sector is no longer required to boot Windows in a BIOS-MBR setup.

Warning: It is the system partition that has bootmgr, not your "real" Windows partition (usually C:). When showing all UUIDs with blkid, the system partition is the one with LABEL="SYSTEM RESERVED" or LABEL="SYSTEM" and is only about 100 to 200 MB in size (much like the boot partition for Arch). See Wikipedia:System partition and boot partition for more info.

Throughout this section, it is assumed your Windows partition is /dev/sda1. A different partition will change every instance of hd0,msdos1. First, find the UUID of the NTFS filesystem of the Windows's SYSTEM PARTITION where the bootmgr and its files reside. For example, if Windows bootmgr exists at /media/SYSTEM_RESERVED/bootmgr:

Note: In some cases, mine I have installed GRUB before a clean Windows 8, you cannot boot Windows having an error with \boot\bcd (error code 0xc000000f). You can fix it going to Windows Recovery Console (cmd from install disk) and executing:

x:\> "bootrec.exe /fixboot"
x:\> "bootrec.exe /RebuildBcd".

Do not use bootrec.exe /Fixmbr because it will wipe GRUB out.

/etc/grub.d/40_custom can be used as a template to create /etc/grub.d/nn_custom. Where nn defines the precendence, indicating the order the script is executed. The order scripts are executed determine the placement in the grub boot menu.

Note: nn should be greater than 06 to ensure necessary scripts are executed first.

RAID

GRUB provides convenient handling of RAID volumes. You need to add insmod mdraid which allows you to address the volume natively. For example, /dev/md0 becomes:

set root=(md0)

whereas a partitioned RAID volume (e.g. /dev/md0p1) becomes:

set root=(md0,1)

To install grub when using RAID1 as the /boot partition (or using /boot housed on a RAID1 root partition), on devices with GPT ef02/'BIOS boot partition', simply run grub-install on both of the drives, such as:

Password protection of GRUB menu

If you want to secure GRUB so it is not possible for anyone to change boot parameters or use the command line, you can add a user/password combination to GRUB's configuration files. To do this, run the command grub-mkpasswd-pbkdf2. Enter a password and confirm it:

This can be relaxed and further customized with more users as described in the "Security" part of the GRUB manual.

Hide GRUB unless the Shift key is held down

In order to achieve the fastest possible boot, instead of having GRUB wait for a timeout, it is possible for GRUB to hide the menu, unless the Shift key is held down during GRUB's start-up.

In order to achieve this, you should add the following line to /etc/default/grub:

GRUB_FORCE_HIDDEN_MENU="true"

And the following file should be created:

/etc/grub.d/31_hold_shift

#! /bin/sh
set -e
# grub-mkconfig helper script.
# Copyright (C) 2006,2007,2008,2009 Free Software Foundation, Inc.
#
# GRUB is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# GRUB is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with GRUB. If not, see <http://www.gnu.org/licenses/>.
prefix="/usr"
exec_prefix="${prefix}"
datarootdir="${prefix}/share"
export TEXTDOMAIN=grub
export TEXTDOMAINDIR="${datarootdir}/locale"
source "${datarootdir}/grub/grub-mkconfig_lib"
found_other_os=
make_timeout () {
if [ "x${GRUB_FORCE_HIDDEN_MENU}" = "xtrue" ] ; then
if [ "x${1}" != "x" ] ; then
if [ "x${GRUB_HIDDEN_TIMEOUT_QUIET}" = "xtrue" ] ; then
verbose=
else
verbose=" --verbose"
fi
if [ "x${1}" = "x0" ] ; then
cat <<EOF
if [ "x\${timeout}" != "x-1" ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep$verbose --interruptible 3 ; then
set timeout=0
fi
fi
fi
EOF
else
cat << EOF
if [ "x\${timeout}" != "x-1" ]; then
if sleep$verbose --interruptible ${GRUB_HIDDEN_TIMEOUT} ; then
set timeout=0
fi
fi
EOF
fi
fi
fi
}
adjust_timeout () {
if [ "x$GRUB_BUTTON_CMOS_ADDRESS" != "x" ]; then
cat <<EOF
if cmostest $GRUB_BUTTON_CMOS_ADDRESS ; then
EOF
make_timeout "${GRUB_HIDDEN_TIMEOUT_BUTTON}" "${GRUB_TIMEOUT_BUTTON}"
echo else
make_timeout "${GRUB_HIDDEN_TIMEOUT}" "${GRUB_TIMEOUT}"
echo fi
else
make_timeout "${GRUB_HIDDEN_TIMEOUT}" "${GRUB_TIMEOUT}"
fi
}
adjust_timeout
cat <<EOF
if [ "x\${timeout}" != "x-1" ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep$verbose --interruptible 3 ; then
set timeout=0
fi
fi
fi
EOF

Combining the use of UUIDs and basic scripting

If you like the idea of using UUIDs to avoid unreliable BIOS mappings or are struggling with GRUB's syntax, here is an example boot menu item that uses UUIDs and a small script to direct GRUB to the proper disk partitions for your system. All you need to do is replace the UUIDs in the sample with the correct UUIDs for your system. The example applies to a system with a boot and root partition. You will obviously need to modify the GRUB configuration if you have additional partitions:

menuentry "Arch Linux 64" {
# Set the UUIDs for your boot and root partition respectively
set the_boot_uuid=ece0448f-bb08-486d-9864-ac3271bd8d07
set the_root_uuid=c55da16f-e2af-4603-9e0b-03f5f565ec4a
# (Note: This may be the same as your boot partition)
# Get the boot/root devices and set them in the root and grub_boot variables
search --fs-uuid $the_root_uuid --set=root
search --fs-uuid $the_boot_uuid --set=grub_boot
# Check to see if boot and root are equal.
# If they are, then append /boot to $grub_boot (Since $grub_boot is actually the root partition)
if [ $the_boot_uuid == $the_root_uuid ] ; then
set grub_boot=($grub_boot)/boot
else
set grub_boot=($grub_boot)
fi
# $grub_boot now points to the correct location, so the following will properly find the kernel and initrd
linux $grub_boot/vmlinuz-linux root=/dev/disk/by-uuid/$the_root_uuid ro
initrd $grub_boot/initramfs-linux.img
}

Using the command shell

Since the MBR is too small to store all GRUB modules, only the menu and a few basic commands reside there. The majority of GRUB functionality remains in modules in /boot/grub, which are inserted as needed. In error conditions (e.g. if the partition layout changes) GRUB may fail to boot. When this happens, a command shell may appear.

GRUB offers multiple shells/prompts. If there is a problem reading the menu but the bootloader is able to find the disk, you will likely be dropped to the "normal" shell:

sh:grub>

If there is a more serious problem (e.g. GRUB cannot find required files), you may instead be dropped to the "rescue" shell:

grub rescue>

The rescue shell is a restricted subset of the normal shell, offering much less functionality. If dumped to the rescue shell, first try inserting the "normal" module, then starting the "normal" shell:

Using the rescue console

See #Using the command shell first. If unable to activate the standard shell, one possible solution is to boot using a live CD or some other rescue disk to correct configuration errors and reinstall GRUB. However, such a boot disk is not always available (nor necessary); the rescue console is surprisingly robust.

The available commands in GRUB rescue include insmod, ls, set, and unset. This example uses set and insmod. set modifies variables and insmod inserts new modules to add functionality.

Before starting, the user must know the location of their /boot partition (be it a separate partition, or a subdirectory under their root):

grub rescue> set prefix=(hdX,Y)/boot/grub

where X is the physical drive number and Y is the partition number.

To expand console capabilities, insert the linux module:

grub rescue> insmod (hdX,Y)/boot/grub/linux.mod

Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod (hdX,Y)/grub/linux.mod).

After successfully booting the Arch Linux installation, users can correct grub.cfg as needed and then reinstall GRUB.

To reinstall GRUB and fix the problem completely, changing /dev/sda if needed. See #Installation for details.

Troubleshooting

Intel BIOS not booting GPT

Some Intel BIOS's require at least one bootable MBR partition to be present at boot, causing GPT-partitioned boot setups to be unbootable.

This can be circumvented by using (for instance) fdisk to mark one of the GPT partitions (preferably the 1007 KiB partition you have created for GRUB already) bootable in the MBR. This can be achieved, using fdisk, by the following commands: Start fdisk against the disk you are installing, for instance fdisk /dev/sda, then press a and select the partition you wish to mark as bootable (probably #1) by pressing the corresponding number, finally press w to write the changes to the MBR.

Note: The bootable-marking must be done in fdisk or similar, not in GParted or others, as they will not set the bootable flag in the MBR.

Enable debug messages

Add:

set pager=1
set debug=all

to grub.cfg.

"No suitable mode found" error

If you get this error when booting any menuentry:

error: no suitable mode found
Booting however

Then you need to initialize GRUB graphical terminal (gfxterm) with proper video mode (gfxmode) in GRUB. This video mode is passed by GRUB to the linux kernel via 'gfxpayload'. In case of UEFI systems, if the GRUB video mode is not initialized, no kernel boot messages will be shown in the terminal (atleast until KMS kicks in).

Copy /usr/share/grub/unicode.pf2 to ${GRUB_PREFIX_DIR} (/boot/grub/ in case of BIOS and UEFI systems). If GRUB UEFI was installed with --boot-directory=$esp/EFI set, then the directory is $esp/EFI/grub/:

# cp /usr/share/grub/unicode.pf2 ${GRUB_PREFIX_DIR}

If /usr/share/grub/unicode.pf2 does not exist, install bdf-unifont, create the unifont.pf2 file and then copy it to ${GRUB_PREFIX_DIR}:

# grub-mkfont -o unicode.pf2 /usr/share/fonts/misc/unifont.bdf

Then, in the grub.cfg file, add the following lines to enable GRUB to pass the video mode correctly to the kernel, without of which you will only get a black screen (no output) but booting (actually) proceeds successfully without any system hang.

BIOS systems:

insmod vbe

UEFI systems:

insmod efi_gop
insmod efi_uga

After that add the following code (common to both BIOS and UEFI):

insmod font

if loadfont ${prefix}/fonts/unicode.pf2
then
insmod gfxterm
set gfxmode=auto
set gfxpayload=keep
terminal_output gfxterm
fi

As you can see for gfxterm (graphical terminal) to function properly, unicode.pf2 font file should exist in ${GRUB_PREFIX_DIR}.

msdos-style error message

grub-setup: warn: This msdos-style partition label has no post-MBR gap; embedding will not be possible!
grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists.
However, blocklists are UNRELIABLE and its use is discouraged.
grub-setup: error: If you really want blocklists, use --force.

This error may occur when you try installing GRUB in a VMware container. Read more about it here. It happens when the first partition starts just after the MBR (block 63), without the usual space of 1 MiB (2048 blocks) before the first partition. Read #Master Boot Record (MBR) specific instructions

GRUB UEFI drops to shell

If GRUB loads but drops you into the rescue shell with no errors, it may be because of a missing or misplaced grub.cfg. This will happen if GRUB UEFI was installed with --boot-directory and grub.cfg is missing OR if the partition number of the boot partition changed (which is hard-coded into the grubx64.efi file).

If the screen only goes black for a second and the next boot option is tried afterwards, according to this post, moving GRUB to the partition root can help. The boot option has to be deleted and recreated afterwards. The entry for GRUB should look like this then:

grub-mkconfig should now mention all found boot options, including Windows. If it works, remove /boot/grub/device.map-old.

Boot freezes

If booting gets stuck without any error message after GRUB loading the kernel and the initial ramdisk, try removing the add_efi_memmap kernel parameter.

Restore GRUB Legacy

Move GRUB v2 files out of the way:

# mv /boot/grub /boot/grub.nonfunctional

Copy GRUB Legacy back to /boot:

# cp -af /boot/grub-legacy /boot/grub

Replace MBR and next 62 sectors of sda with backed up copy

Warning: This command also restores the partition table, so be careful of overwriting a modified partition table with the old one. It will mess up your system.

# dd if=/path/to/backup/first-sectors of=/dev/sdX bs=512 count=1

A safer way is to restore only the MBR boot code use:

# dd if=/path/to/backup/mbr-boot-code of=/dev/sdX bs=446 count=1

Arch not found from other OS

Some have reported that other distributions have trouble finding Arch Linux automatically with os-prober. If this problem arises, it has been reported that detection can be improved with the presence of /etc/lsb-release. This file and updating tool is available with the package lsb-release in the official repositories.