{"id":167,"date":"2014-01-13T19:18:21","date_gmt":"2014-01-13T11:18:21","guid":{"rendered":"http:\/\/www.datarelab.com\/blog\/?p=167"},"modified":"2014-01-13T19:18:21","modified_gmt":"2014-01-13T11:18:21","slug":"grub2%20%e9%83%a8%e5%88%86%e4%bb%8b%e7%bb%8d","status":"publish","type":"post","link":"https:\/\/www.datarelab.com\/blog\/Technical_literature\/167.html","title":{"rendered":"GRUB2 \u90e8\u5206\u4ecb\u7ecd"},"content":{"rendered":"<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a class=\"external text\" href=\"https:\/\/www.gnu.org\/software\/grub\/\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">GRUB2<\/a>&nbsp;is the next generation of the GRand Unified Bootloader (GRUB). GRUB2 is derived from&nbsp;<a class=\"external text\" href=\"http:\/\/www.nongnu.org\/pupa\/\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">PUPA<\/a>&nbsp;which was a research project to investigate the next generation of GRUB. GRUB2 has been rewritten from scratch to clean up everything and provide modularity and portability&nbsp;<a class=\"external autonumber\" href=\"https:\/\/www.gnu.org\/software\/grub\/grub-faq.html#q1\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">[1]<\/a>.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIn brief, the&nbsp;<em>bootloader<\/em>&nbsp;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.\n<\/p>\n<table class=\"toc \" id=\"toc\" style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;background-color:#FFFFFF;\">\n<tbody>\n<tr>\n<td>\n<div id=\"toctitle\">\n<h2 style=\"margin:0px;padding:0px;\">\n\t\t\t\t\t\t<a name=\"t0\"><\/a>Contents<br \/>\n\t\t\t\t\t<\/h2>\n<\/p><\/div>\n<ul>\n<li class=\"toclevel-1 tocsection-1\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Preface\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">1<\/span>&nbsp;<span class=\"toctext\">Preface<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-2 tocsection-2\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Notes_for_current_GRUB_Legacy_users\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">1.1<\/span>&nbsp;<span class=\"toctext\">Notes for current GRUB Legacy users<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-3\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Preliminary_Requirements_for_GRUB2\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">1.2<\/span>&nbsp;<span class=\"toctext\">Preliminary Requirements for GRUB2<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-3 tocsection-4\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#BIOS_systems\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">1.2.1<\/span>&nbsp;<span class=\"toctext\">BIOS systems<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-4 tocsection-5\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#GUID_Partition_Table_.28GPT.29_specific_instructions\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">1.2.1.1<\/span>&nbsp;<span class=\"toctext\">GUID Partition Table (GPT) specific instructions<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-4 tocsection-6\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Master_Boot_Record_.28MBR.29_specific_instructions\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">1.2.1.2<\/span>&nbsp;<span class=\"toctext\">Master Boot Record (MBR) specific instructions<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-3 tocsection-7\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#UEFI_systems\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">1.2.2<\/span>&nbsp;<span class=\"toctext\">UEFI systems<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-4 tocsection-8\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Create_and_Mount_the_UEFI_System_Partition\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">1.2.2.1<\/span>&nbsp;<span class=\"toctext\">Create and Mount the UEFI System Partition<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-1 tocsection-9\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Installation\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2<\/span>&nbsp;<span class=\"toctext\">Installation<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-2 tocsection-10\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#BIOS_systems_2\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1<\/span>&nbsp;<span class=\"toctext\">BIOS systems<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-3 tocsection-11\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Backup_Important_Data\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.1<\/span>&nbsp;<span class=\"toctext\">Backup Important Data<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-12\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_grub-bios_package\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.2<\/span>&nbsp;<span class=\"toctext\">Install grub-bios package<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-13\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_grub-bios_boot_files\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.3<\/span>&nbsp;<span class=\"toctext\">Install grub-bios boot files<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-4 tocsection-14\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_to_440-byte_MBR_boot_code_region\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.3.1<\/span>&nbsp;<span class=\"toctext\">Install to 440-byte MBR boot code region<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-4 tocsection-15\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_to_GPT_BIOS_Boot_Partition\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.3.2<\/span>&nbsp;<span class=\"toctext\">Install to GPT BIOS Boot Partition<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-4 tocsection-16\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_to_Partition_or_Partitionless_Disk\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.3.3<\/span>&nbsp;<span class=\"toctext\">Install to Partition or Partitionless Disk<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-4 tocsection-17\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Generate_core.img_alone\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.3.4<\/span>&nbsp;<span class=\"toctext\">Generate core.img alone<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-3 tocsection-18\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Generate_GRUB2_BIOS_Config_file\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.4<\/span>&nbsp;<span class=\"toctext\">Generate GRUB2 BIOS Config file<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-19\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Multiboot_in_BIOS\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.5<\/span>&nbsp;<span class=\"toctext\">Multiboot in BIOS<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-4 tocsection-20\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Boot_Microsoft_Windows_installed_in_BIOS-MBR_mode\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.1.5.1<\/span>&nbsp;<span class=\"toctext\">Boot Microsoft Windows installed in BIOS-MBR mode<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-2 tocsection-21\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#UEFI_systems_2\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2<\/span>&nbsp;<span class=\"toctext\">UEFI systems<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-3 tocsection-22\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Hardware-Specific_UEFI_Examples\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2.1<\/span>&nbsp;<span class=\"toctext\">Hardware-Specific UEFI Examples<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-23\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_grub-uefi_package\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2.2<\/span>&nbsp;<span class=\"toctext\">Install grub-uefi package<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-24\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_grub-uefi_boot_files\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2.3<\/span>&nbsp;<span class=\"toctext\">Install grub-uefi boot files<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-4 tocsection-25\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_to_UEFI_System_Partition\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2.3.1<\/span>&nbsp;<span class=\"toctext\">Install to UEFI System Partition<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-3 tocsection-26\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Generate_GRUB2_UEFI_Config_file\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2.4<\/span>&nbsp;<span class=\"toctext\">Generate GRUB2 UEFI Config file<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-27\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Create_GRUB2_entry_in_the_Firmware_Boot_Manager\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2.5<\/span>&nbsp;<span class=\"toctext\">Create GRUB2 entry in the Firmware Boot Manager<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-28\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Create_GRUB2_Standalone_UEFI_Application\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2.6<\/span>&nbsp;<span class=\"toctext\">Create GRUB2 Standalone UEFI Application<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-29\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Multiboot_in_UEFI\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2.7<\/span>&nbsp;<span class=\"toctext\">Multiboot in UEFI<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-4 tocsection-30\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Chainload_Microsoft_Windows_x86_64_UEFI-GPT\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">2.2.7.1<\/span>&nbsp;<span class=\"toctext\">Chainload Microsoft Windows x86_64 UEFI-GPT<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-1 tocsection-31\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Configuration\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3<\/span>&nbsp;<span class=\"toctext\">Configuration<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-2 tocsection-32\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Automatically_generating_using_grub-mkconfig_.28Recommended.29\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.1<\/span>&nbsp;<span class=\"toctext\">Automatically generating using grub-mkconfig (Recommended)<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-3 tocsection-33\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Additional_arguments\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.1.1<\/span>&nbsp;<span class=\"toctext\">Additional arguments<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-2 tocsection-34\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Manually_creating_grub.cfg\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.2<\/span>&nbsp;<span class=\"toctext\">Manually creating grub.cfg<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-35\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Dual-booting\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.3<\/span>&nbsp;<span class=\"toctext\">Dual-booting<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-3 tocsection-36\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Using_grub-mkconfig\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.3.1<\/span>&nbsp;<span class=\"toctext\">Using grub-mkconfig<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-4 tocsection-37\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#With_GNU.2FLinux\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.3.1.1<\/span>&nbsp;<span class=\"toctext\">With GNU\/Linux<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-4 tocsection-38\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#With_FreeBSD\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.3.1.2<\/span>&nbsp;<span class=\"toctext\">With FreeBSD<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-4 tocsection-39\">\n\t\t\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#With_Windows\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.3.1.3<\/span>&nbsp;<span class=\"toctext\">With Windows<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-3 tocsection-40\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#With_Windows_via_EasyBCD_and_NeoGRUB\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.3.2<\/span>&nbsp;<span class=\"toctext\">With Windows via EasyBCD and NeoGRUB<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-2 tocsection-41\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Visual_Configuration\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.4<\/span>&nbsp;<span class=\"toctext\">Visual Configuration<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-3 tocsection-42\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Setting_the_framebuffer_resolution\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.4.1<\/span>&nbsp;<span class=\"toctext\">Setting the framebuffer resolution<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-43\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#915resolution_hack\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.4.2<\/span>&nbsp;<span class=\"toctext\">915resolution hack<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-44\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Background_image_and_bitmap_fonts\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.4.3<\/span>&nbsp;<span class=\"toctext\">Background image and bitmap fonts<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-45\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Theme\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.4.4<\/span>&nbsp;<span class=\"toctext\">Theme<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-46\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Menu_colors\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.4.5<\/span>&nbsp;<span class=\"toctext\">Menu colors<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-47\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Hidden_menu\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.4.6<\/span>&nbsp;<span class=\"toctext\">Hidden menu<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-48\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Disable_framebuffer\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.4.7<\/span>&nbsp;<span class=\"toctext\">Disable framebuffer<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-2 tocsection-49\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Other_Options\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.5<\/span>&nbsp;<span class=\"toctext\">Other Options<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-3 tocsection-50\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#LVM\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.5.1<\/span>&nbsp;<span class=\"toctext\">LVM<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-51\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#RAID\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.5.2<\/span>&nbsp;<span class=\"toctext\">RAID<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-52\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Persistent_block_device_naming\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.5.3<\/span>&nbsp;<span class=\"toctext\">Persistent block device naming<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-53\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Using_Labels\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.5.4<\/span>&nbsp;<span class=\"toctext\">Using Labels<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-54\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Recall_previous_entry\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.5.5<\/span>&nbsp;<span class=\"toctext\">Recall previous entry<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-55\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Security\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.5.6<\/span>&nbsp;<span class=\"toctext\">Security<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-56\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Root_Encryption\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.5.7<\/span>&nbsp;<span class=\"toctext\">Root Encryption<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-57\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Boot_non-default_entry_only_once\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.5.8<\/span>&nbsp;<span class=\"toctext\">Boot non-default entry only once<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-2 tocsection-58\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Booting_an_ISO_Directly_From_GRUB2\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.6<\/span>&nbsp;<span class=\"toctext\">Booting an ISO Directly From GRUB2<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-3 tocsection-59\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Arch_ISO\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.6.1<\/span>&nbsp;<span class=\"toctext\">Arch ISO<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-60\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Ubuntu_ISO\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.6.2<\/span>&nbsp;<span class=\"toctext\">Ubuntu ISO<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-3 tocsection-61\">\n\t\t\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Other_ISOs\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">3.6.3<\/span>&nbsp;<span class=\"toctext\">Other ISOs<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-1 tocsection-62\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Using_the_command_shell\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">4<\/span>&nbsp;<span class=\"toctext\">Using the command shell<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-2 tocsection-63\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Pager_support\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">4.1<\/span>&nbsp;<span class=\"toctext\">Pager support<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-1 tocsection-64\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#GUI_configuration_tools\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">5<\/span>&nbsp;<span class=\"toctext\">GUI configuration tools<\/span><\/a>\n\t\t\t\t\t<\/li>\n<li class=\"toclevel-1 tocsection-65\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#parttool_for_hide.2Funhide\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">6<\/span>&nbsp;<span class=\"toctext\">parttool for hide\/unhide<\/span><\/a>\n\t\t\t\t\t<\/li>\n<li class=\"toclevel-1 tocsection-66\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Using_the_rescue_console\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">7<\/span>&nbsp;<span class=\"toctext\">Using the rescue console<\/span><\/a>\n\t\t\t\t\t<\/li>\n<li class=\"toclevel-1 tocsection-67\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Combining_the_use_of_UUIDs_and_basic_scripting\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">8<\/span>&nbsp;<span class=\"toctext\">Combining the use of UUIDs and basic scripting<\/span><\/a>\n\t\t\t\t\t<\/li>\n<li class=\"toclevel-1 tocsection-68\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Troubleshooting\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9<\/span>&nbsp;<span class=\"toctext\">Troubleshooting<\/span><\/a><\/p>\n<ul>\n<li class=\"toclevel-2 tocsection-69\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Intel_BIOS_not_booting_GPT\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9.1<\/span>&nbsp;<span class=\"toctext\">Intel BIOS not booting GPT<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-70\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Enable_GRUB2_debug_messages\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9.2<\/span>&nbsp;<span class=\"toctext\">Enable GRUB2 debug messages<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-71\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Correct_GRUB2_No_Suitable_Mode_Found_Error\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9.3<\/span>&nbsp;<span class=\"toctext\">Correct GRUB2 No Suitable Mode Found Error<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-72\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#msdos-style_error_message\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9.4<\/span>&nbsp;<span class=\"toctext\">msdos-style error message<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-73\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#UEFI_GRUB2_drops_to_shell\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9.5<\/span>&nbsp;<span class=\"toctext\">UEFI GRUB2 drops to shell<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-74\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#UEFI_GRUB2_not_loaded\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9.6<\/span>&nbsp;<span class=\"toctext\">UEFI GRUB2 not loaded<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-75\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Invalid_signature\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9.7<\/span>&nbsp;<span class=\"toctext\">Invalid signature<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-76\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Boot_freezes\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9.8<\/span>&nbsp;<span class=\"toctext\">Boot freezes<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<li class=\"toclevel-2 tocsection-77\">\n\t\t\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Restore_GRUB_Legacy\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">9.9<\/span>&nbsp;<span class=\"toctext\">Restore GRUB Legacy<\/span><\/a>\n\t\t\t\t\t\t\t<\/li>\n<\/ul>\n<\/li>\n<li class=\"toclevel-1 tocsection-78\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#References\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">10<\/span>&nbsp;<span class=\"toctext\">References<\/span><\/a>\n\t\t\t\t\t<\/li>\n<li class=\"toclevel-1 tocsection-79\">\n\t\t\t\t\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#External_Links\" style=\"color:#336699;text-decoration:none;\"><span class=\"tocnumber\">11<\/span>&nbsp;<span class=\"toctext\">External Links<\/span><\/a>\n\t\t\t\t\t<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t1\"><\/a><span class=\"mw-headline\" id=\"Preface\">Preface<\/span><br \/>\n<\/h2>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tHere is some information that needs to be clarified:\n<\/p>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tThe name&nbsp;<em>GRUB<\/em>&nbsp;officially refers to version&nbsp;<em>2<\/em>&nbsp;of the software, see&nbsp;<a class=\"external autonumber\" href=\"https:\/\/www.gnu.org\/software\/grub\/\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">[2]<\/a>. If you are looking for the article on the legacy version, see&nbsp;<a title=\"GRUB Legacy\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB_Legacy\" style=\"color:#336699;text-decoration:none;\">GRUB Legacy<\/a>.\n\t<\/li>\n<\/ul>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tFrom 1.99-6 onwards, GRUB2 supports&nbsp;<a title=\"Btrfs\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Btrfs\" style=\"color:#336699;text-decoration:none;\">Btrfs<\/a>&nbsp;as root (without a separate&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>&nbsp;filesystem) compressed with either zlib or LZO.\n\t<\/li>\n<\/ul>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tFor GRUB2 UEFI info, it is recommended to read the&nbsp;<a title=\"Unified Extensible Firmware Interface\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Unified_Extensible_Firmware_Interface\" style=\"color:#336699;text-decoration:none;\">UEFI<\/a>,&nbsp;<a title=\"GUID Partition Table\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GUID_Partition_Table\" style=\"color:#336699;text-decoration:none;\">GPT<\/a>&nbsp;and&nbsp;<a title=\"UEFI Bootloaders\" href=\"https:\/\/wiki.archlinux.org\/index.php\/UEFI_Bootloaders\" style=\"color:#336699;text-decoration:none;\">UEFI Bootloaders<\/a>&nbsp;pages before reading this page.\n\t<\/li>\n<\/ul>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t2\"><\/a><span class=\"mw-headline\" id=\"Notes_for_current_GRUB_Legacy_users\">Notes for current GRUB Legacy users<\/span><br \/>\n<\/h3>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tUpgrade from&nbsp;<a title=\"GRUB Legacy\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB_Legacy\" style=\"color:#336699;text-decoration:none;\">GRUB Legacy<\/a>&nbsp;to GRUB2 is the much same as fresh installing GRUB2 which is covered<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Installation\" style=\"color:#336699;text-decoration:none;\">below<\/a>.\n\t<\/li>\n<\/ul>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tThere are differences in the commands of GRUB and GRUB2. Familiarize yourself with&nbsp;<a class=\"external text\" href=\"https:\/\/www.gnu.org\/software\/grub\/manual\/grub.html#Commands\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">GRUB2 commands<\/a>&nbsp;before proceeding (e.g. \"find\" has been replaced with \"search\").\n\t<\/li>\n<\/ul>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tGRUB2 is now&nbsp;<em>modular<\/em>&nbsp;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&nbsp;<a title=\"LVM\" href=\"https:\/\/wiki.archlinux.org\/index.php\/LVM\" style=\"color:#336699;text-decoration:none;\">LVM<\/a>&nbsp;or RAID support).\n\t<\/li>\n<\/ul>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tDevice naming has changed between GRUB and GRUB2. Partitions are numbered from 1 instead of 0 while drives are still numbered from 0, and prefixed with partition-table type. For example,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/sda1<\/code>would be referred to as&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">(hd0,msdos1)<\/code>&nbsp;(for MBR) or&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">(hd0,gpt1)<\/code>&nbsp;(for GPT) using GRUB2.\n\t<\/li>\n<\/ul>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t3\"><\/a><span class=\"mw-headline\" id=\"Preliminary_Requirements_for_GRUB2\">Preliminary Requirements for GRUB2<\/span><br \/>\n<\/h3>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t4\"><\/a><span class=\"mw-headline\" id=\"BIOS_systems\">BIOS systems<\/span><br \/>\n<\/h4>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t5\"><\/a><span class=\"mw-headline\" id=\"GUID_Partition_Table_.28GPT.29_specific_instructions\"><a title=\"GUID Partition Table\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GUID_Partition_Table\" style=\"color:#336699;text-decoration:none;\">GUID Partition Table<\/a>&nbsp;(GPT) specific instructions<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGRUB2 in BIOS-GPT configuration requires a&nbsp;<a class=\"external text\" href=\"http:\/\/www.gnu.org\/software\/grub\/manual\/html_node\/BIOS-installation.html\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">BIOS Boot Partition<\/a>&nbsp;to embed its&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">core.img<\/code>&nbsp;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 GRUB2 only in BIOS-GPT setups. No such partition type exists in case of MBR partitioning (at least not for GRUB2). This partition is also not required if the system is UEFI based, as no embedding of bootsectors takes place in that case. Syslinux does not require this partition.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFor a BIOS-GPT configuration, create a 1007 KiB partition at the beginning of the disk using 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&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">0xEF02<\/code>&nbsp;in gdisk,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">EF02<\/code>&nbsp;in cgdisk or&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">set &lt;BOOT_PART_NUM&gt; bios_grub on<\/code>&nbsp;in GNU Parted.\n<\/p>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>This partition should be created before&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>&nbsp;or&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-setup<\/code>&nbsp;is run.\n<\/div>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>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.\n<\/div>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t6\"><\/a><span class=\"mw-headline\" id=\"Master_Boot_Record_.28MBR.29_specific_instructions\"><a title=\"Master Boot Record\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Master_Boot_Record\" style=\"color:#336699;text-decoration:none;\">Master Boot Record<\/a>&nbsp;(MBR) specific instructions<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tUsually 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 GRUB2's&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">core.img<\/code>&nbsp;(<a class=\"external text\" href=\"https:\/\/bugs.archlinux.org\/task\/24103\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">FS#24103<\/a>). 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&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">core.img<\/code>).\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tMBR partitioning has better support in other operating systems, such as Microsoft Windows (up to Windows 7) and Haiku, than GPT partitioning. If you dual boot another operating system, consider using MBR partitioning.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tA MBR disk may be convertible to GPT if there is a small amount of extra space available. See&nbsp;<a title=\"GUID Partition Table\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GUID_Partition_Table#Convert_from_MBR_to_GPT\" style=\"color:#336699;text-decoration:none;\">GUID Partition Table#Convert from MBR to GPT<\/a>\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t7\"><\/a><span class=\"mw-headline\" id=\"UEFI_systems\">UEFI systems<\/span><br \/>\n<\/h4>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>It is recommended to read and understand the&nbsp;<a title=\"Unified Extensible Firmware Interface\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Unified_Extensible_Firmware_Interface\" style=\"color:#336699;text-decoration:none;\">UEFI<\/a>,&nbsp;<a title=\"GUID Partition Table\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GUID_Partition_Table\" style=\"color:#336699;text-decoration:none;\">GPT<\/a>&nbsp;and&nbsp;<a title=\"UEFI Bootloaders\" href=\"https:\/\/wiki.archlinux.org\/index.php\/UEFI_Bootloaders\" style=\"color:#336699;text-decoration:none;\">UEFI Bootloaders<\/a>&nbsp;pages.\n<\/div>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t8\"><\/a><span class=\"mw-headline\" id=\"Create_and_Mount_the_UEFI_System_Partition\">Create and Mount the UEFI System Partition<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFollow&nbsp;<a title=\"Unified Extensible Firmware Interface\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Unified_Extensible_Firmware_Interface#EFI_System_Partition\" style=\"color:#336699;text-decoration:none;\">Unified Extensible Firmware Interface#EFI System Partition<\/a>&nbsp;for instructions on creating a UEFI SYSTEM PARTITION. Then mount the UEFI SYSTEM PARTITION at&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/efi<\/code>. If you have mounted the UEFISYS partition in some other mountpoint, replace&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/efi<\/code>&nbsp;in the below instructions with that mountpoint:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># mkdir -p \/boot\/efi\r\n# mount -t vfat &lt;UEFISYS_PART_DEVICE&gt; \/boot\/efi\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tCreate a &lt;UEFI_SYSTEM_PARTITION&gt;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/EFI<\/code>&nbsp;directory, if it does not exist:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># mkdir -p \/boot\/efi\/EFI\r\n<\/pre>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t9\"><\/a><span class=\"mw-headline\" id=\"Installation\">Installation<\/span><br \/>\n<\/h2>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t10\"><\/a><span class=\"mw-headline\" id=\"BIOS_systems_2\">BIOS systems<\/span><br \/>\n<\/h3>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t11\"><\/a><span class=\"mw-headline\" id=\"Backup_Important_Data\">Backup Important Data<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAlthough a GRUB(2) installation should run smoothly, it is strongly recommended to keep the GRUB Legacy files before installing&nbsp;<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/www.archlinux.org\/packages\/?name=grub-bios\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">grub-bios<\/a><\/span>.\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># mv \/boot\/grub \/boot\/grub-legacy\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tBackup the MBR which contains the boot code and partition table (Replace&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/sd<strong>X<\/strong><\/code>&nbsp;with your actual disk path)\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># dd if=\/dev\/sdX of=\/path\/to\/backup\/mbr_backup bs=512 count=1\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tOnly 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:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># dd if=\/dev\/sdX of=\/path\/to\/backup\/bootcode_backup bs=446 count=1\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf unable to install GRUB2 correctly, see&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Restore_GRUB_Legacy\" style=\"color:#336699;text-decoration:none;\">#Restore GRUB Legacy<\/a>.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t12\"><\/a><span class=\"mw-headline\" id=\"Install_grub-bios_package\">Install grub-bios package<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe GRUB(2) packages can be installed with pacman (and will replace&nbsp;<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/www.archlinux.org\/packages\/?name=grub-legacy\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">grub-legacy<\/a><\/span>&nbsp;or&nbsp;<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/www.archlinux.org\/packages\/?name=grub\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">grub<\/a><\/span>, if it is installed):\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># pacman -S grub-bios\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>Simply installing the package won't update the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc\/core.img<\/code>&nbsp;file and the GRUB(2) modules in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc<\/code>. You need to update them manually using&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>&nbsp;as explained below.\n<\/div>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t13\"><\/a><span class=\"mw-headline\" id=\"Install_grub-bios_boot_files\">Install grub-bios boot files<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThere are 3 ways to install GRUB(2) boot files in BIOS booting:\n<\/p>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_to_GPT_BIOS_Boot_Partition\" style=\"color:#336699;text-decoration:none;\">#Install to GPT BIOS Boot Partition<\/a>&nbsp;(recommended with&nbsp;<a title=\"GPT\" class=\"mw-redirect\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GPT\" style=\"color:#336699;text-decoration:none;\">GPT<\/a>)\n\t<\/li>\n<li>\n\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_to_440-byte_MBR_boot_code_region\" style=\"color:#336699;text-decoration:none;\">#Install to 440-byte MBR boot code region<\/a>&nbsp;(recommended with&nbsp;<a title=\"MBR\" class=\"mw-redirect\" href=\"https:\/\/wiki.archlinux.org\/index.php\/MBR\" style=\"color:#336699;text-decoration:none;\">MBR<\/a>)\n\t<\/li>\n<li>\n\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Install_to_Partition_or_Partitionless_Disk\" style=\"color:#336699;text-decoration:none;\">#Install to Partition or Partitionless Disk<\/a>&nbsp;(not recommended)\n\t<\/li>\n<li>\n\t\t<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Generate_core.img_alone\" style=\"color:#336699;text-decoration:none;\">#Generate core.img alone<\/a>&nbsp;(safest method, but requires another BIOS bootloader like&nbsp;<a title=\"Grub-legacy\" class=\"mw-redirect\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Grub-legacy\" style=\"color:#336699;text-decoration:none;\">grub-legacy<\/a>&nbsp;or<a title=\"Syslinux\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Syslinux\" style=\"color:#336699;text-decoration:none;\">syslinux<\/a>&nbsp;to be installed to chainload&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc\/core.img<\/code>)\n\t<\/li>\n<\/ul>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>See&nbsp;<a class=\"external free\" href=\"http:\/\/www.gnu.org\/software\/grub\/manual\/html_node\/BIOS-installation.html\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">http:\/\/www.gnu.org\/software\/grub\/manual\/html_node\/BIOS-installation.html<\/a>&nbsp;for additional documentation.\n<\/div>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t14\"><\/a><span class=\"mw-headline\" id=\"Install_to_440-byte_MBR_boot_code_region\">Install to 440-byte MBR boot code region<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo setup&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-bios<\/code>&nbsp;in the 440-byte Master Boot Record boot code region, populate the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub<\/code>directory, generate the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc\/core.img<\/code>&nbsp;file, embed it in the 31 KiB (minimum size - varies depending on partition alignment) post-MBR gap, and generate the configuration file, run:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># modprobe dm-mod\r\n# grub-install --recheck \/dev\/sda\r\n# grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\twhere&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/sda<\/code>&nbsp;is the destination of the installation (in this case the MBR of the first SATA disk). If you use<a title=\"LVM\" href=\"https:\/\/wiki.archlinux.org\/index.php\/LVM\" style=\"color:#336699;text-decoration:none;\">LVM<\/a>&nbsp;for your&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>, you can install GRUB2 on multiple physical disks.\n<\/p>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong><code style=\"padding:0.1em 0.3em;display:inline-block;\">--no-floppy<\/code>&nbsp;has been removed from&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>&nbsp;in 2.00~beta2 upstream release, and replaced with&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--allow-floppy<\/code>.\n<\/div>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #DDBBBB;overflow:hidden;background-color:#FFDDDD;\">\n\t<strong>Warning:&nbsp;<\/strong>Make sure to check the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>&nbsp;directory if you use the latter. Sometimes the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">boot-directory<\/code>parameter creates another&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>&nbsp;folder inside of&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>. A wrong install would look like:&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/boot\/grub\/<\/code>.\n<\/div>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t15\"><\/a><span class=\"mw-headline\" id=\"Install_to_GPT_BIOS_Boot_Partition\">Install to GPT BIOS Boot Partition<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a title=\"GUID Partition Table\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GUID_Partition_Table\" style=\"color:#336699;text-decoration:none;\">GUID Partition Table<\/a>&nbsp;disks do not have a reserved \"boot track\".&nbsp; Therefore you must create a BIOS Boot Partition (0xEF02) to hold the GRUB core image.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tUsing GNU Parted, you can set this using a command such as the following:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># parted \/dev\/disk set &lt;partition-number&gt; bios_grub on\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you are using gdisk, set the partition type to&nbsp;<code style=\"padding:0.1em 0.3em;font-weight:bold;display:inline-block;background-color:#EBF1F5;\">0xEF02<\/code>. With partitioning programs that require setting the GUID directly, it should be&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\u201821686148-6449-6e6f-744e656564454649\u2019<\/code>&nbsp;(stored on disk as&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\"!haHdInotNeedEFI\"<\/code>&nbsp;if interpreted as ASCII).\n<\/p>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #DDBBBB;overflow:hidden;background-color:#FFDDDD;\">\n\t<strong>Warning:&nbsp;<\/strong>Be very careful which partition you select when marking it as a BIOS Boot Partition. When GRUB finds a BIOS Boot Partition during installation, it will automatically overwrite part of it. Make sure that the partition does not contain any other data.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo setup&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-bios<\/code>&nbsp;on a GPT disk, populate the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub<\/code>&nbsp;directory, generate the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc\/core.img<\/code>&nbsp;file, and embed it in the BIOS Boot Partition, run:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># modprobe dm-mod\r\n# grub-install --target=i386-pc --recheck --debug \/dev\/sda\r\n# mkdir -p \/boot\/grub\/locale\r\n# cp \/usr\/share\/locale\/en\\@quot\/LC_MESSAGES\/grub.mo \/boot\/grub\/locale\/en.mo\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\twhere&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/sda<\/code>&nbsp;is the destination of the installation.\n<\/p>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t16\"><\/a><span class=\"mw-headline\" id=\"Install_to_Partition_or_Partitionless_Disk\">Install to Partition or Partitionless Disk<\/span><br \/>\n<\/h5>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong><code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-bios<\/code>&nbsp;(any version - including upstream Bazaar repo) 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.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo set up&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-bios<\/code>&nbsp;to a partition boot sector, to a partitionless disk (also called superfloppy) or to a floppy disk, run (using for example&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/sdaX<\/code>&nbsp;as the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>&nbsp;partition):\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># modprobe dm-mod \r\n# grub-install --target=i386-pc --recheck --debug --force \/dev\/sdaX\r\n# chattr -i \/boot\/grub\/i386-pc\/core.img\r\n# mkdir -p \/boot\/grub\/locale\r\n# cp \/usr\/share\/locale\/en@quot\/LC_MESSAGES\/grub.mo \/boot\/grub\/locale\/en.mo\r\n# chattr +i \/boot\/grub\/i386-pc\/core.img\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tYou need to use the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--force<\/code>&nbsp;option to allow usage of blocklists and should not use&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--grub-setup=\/bin\/true<\/code>&nbsp;(which is similar to simply generating&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">core.img<\/code>).\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>&nbsp;will give out warnings like which should give you the idea of what might go wrong with this approach:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">\/sbin\/grub-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea.\r\n\/sbin\/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. \r\n                        However, blocklists are UNRELIABLE and their use is discouraged.\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tWithout&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--force<\/code>&nbsp;you may get the below error and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-setup<\/code>&nbsp;will not setup its boot code in the partition boot sector:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">\/sbin\/grub-setup: error: will not proceed with blocklists\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tWith&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--force<\/code>&nbsp;you should get:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">Installation finished. No error reported.\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe reason why&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-setup<\/code>&nbsp;does not by default allow this is because in case of partition or a partitionless disk is that&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-bios<\/code>&nbsp;relies on embedded blocklists in the partition bootsector to locate the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc\/core.img<\/code>&nbsp;file and the prefix dir&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub<\/code>. The sector locations of&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">core.img<\/code>may change whenever the filesystem in the partition is being altered (files copied, deleted etc.). For more info see&nbsp;<a class=\"external free\" href=\"https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=728742\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=728742<\/a>&nbsp;and&nbsp;<a class=\"external free\" href=\"https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=730915\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=730915<\/a>.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe workaround for this is to set the immutable flag on&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc\/core.img<\/code>&nbsp;(using chattr command as mentioned above) so that the sector locations of the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">core.img<\/code>&nbsp;file in the disk is not altered. The immutable flag on&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc\/core.img<\/code>&nbsp;needs to be set only if&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-bios<\/code>&nbsp;is installed to a partition boot sector or a partitionless disk, not in case of installation to MBR or simple generation of&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">core.img<\/code>&nbsp;without embedding any bootsector (mentioned above).\n<\/p>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t17\"><\/a><span class=\"mw-headline\" id=\"Generate_core.img_alone\">Generate core.img alone<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo populate the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub<\/code>&nbsp;directory and generate a&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc\/core.img<\/code>&nbsp;file&nbsp;<strong>without<\/strong>embedding any&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-bios<\/code>&nbsp;bootsector code in the MBR, post-MBR region, or the partition bootsector, add&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--grub-setup=\/bin\/true<\/code>&nbsp;to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># modprobe dm-mod\r\n# grub-install --target=i386-pc --grub-setup=\/bin\/true --recheck --debug \/dev\/sda\r\n# mkdir -p \/boot\/grub\/locale\r\n# cp \/usr\/share\/locale\/en@quot\/LC_MESSAGES\/grub.mo \/boot\/grub\/locale\/en.mo\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tYou can then chainload GRUB2's&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">core.img<\/code>&nbsp;from GRUB Legacy or syslinux as a Linux kernel or a multiboot kernel.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t18\"><\/a><span class=\"mw-headline\" id=\"Generate_GRUB2_BIOS_Config_file\">Generate GRUB2 BIOS Config file<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFinally, generate a configuration for GRUB2 (this is explained in greater detail in the Configuration section):\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>The file path is&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/grub.cfg<\/code>, NOT&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/i386-pc\/grub.cfg<\/code>.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf grub(2) complains about \"no suitable mode found\" while booting, go to&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Correct_GRUB2_No_Suitable_Mode_Found_Error\" style=\"color:#336699;text-decoration:none;\">#Correct GRUB2 No Suitable Mode Found Error<\/a>.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkconfig<\/code>&nbsp;fails, convert your&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/menu.lst<\/code>&nbsp;file to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/grub.cfg<\/code>&nbsp;using:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-menulst2cfg \/boot\/grub\/menu.lst \/boot\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFor example:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;padding-bottom:0.8em;margin-bottom:0px;border-bottom-color:currentcolor;border-bottom-width:medium;border-bottom-style:none;\">\/boot\/grub\/menu.lst<\/pre>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;padding-top:0.8em;margin-top:0px;border-top-style:dashed;\">default=0\r\ntimeout=5\r\n\r\ntitle  Arch Linux Stock Kernel\r\nroot   (hd0,0)\r\nkernel \/vmlinuz-linux root=\/dev\/sda2 ro\r\ninitrd \/initramfs-linux.img\r\n\r\ntitle  Arch Linux Stock Kernel Fallback\r\nroot   (hd0,0)\r\nkernel \/vmlinuz-linux root=\/dev\/sda2 ro\r\ninitrd \/initramfs-linux-fallback.img\r\n<\/pre>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;padding-bottom:0.8em;margin-bottom:0px;border-bottom-color:currentcolor;border-bottom-width:medium;border-bottom-style:none;\">\/boot\/grub\/grub.cfg<\/pre>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;padding-top:0.8em;margin-top:0px;border-top-style:dashed;\">set default='0'; if [ x\"$default\" = xsaved ]; then load_env; set default=\"$saved_entry\"; fi\r\nset timeout=5\r\n\r\nmenuentry 'Arch Linux Stock Kernel' {\r\n  set root='(hd0,1)'; set legacy_hdbias='0'\r\n  legacy_kernel   '\/vmlinuz-linux' '\/vmlinuz-linux' 'root=\/dev\/sda2' 'ro'\r\n  legacy_initrd '\/initramfs-linux.img' '\/initramfs-linux.img'\r\n  \r\n}\r\n\r\nmenuentry 'Arch Linux Stock Kernel Fallback' {\r\n  set root='(hd0,1)'; set legacy_hdbias='0'\r\n  legacy_kernel   '\/vmlinuz-linux' '\/vmlinuz-linux' 'root=\/dev\/sda2' 'ro'\r\n  legacy_initrd '\/initramfs-linux-fallback.img' '\/initramfs-linux-fallback.img'\r\n}\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you forgot to create a GRUB2&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/grub.cfg<\/code>&nbsp;config file and simply rebooted into GRUB2 Command Shell, type:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">sh:grub&gt; insmod legacycfg\r\nsh:grub&gt; legacy_configfile ${prefix}\/menu.lst\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tBoot into Arch and re-create the proper GRUB2&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/grub.cfg<\/code>&nbsp;config file.\n<\/p>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>This option works only in BIOS systems, not in UEFI systems.\n<\/div>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t19\"><\/a><span class=\"mw-headline\" id=\"Multiboot_in_BIOS\">Multiboot in BIOS<\/span><br \/>\n<\/h4>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t20\"><\/a><span class=\"mw-headline\" id=\"Boot_Microsoft_Windows_installed_in_BIOS-MBR_mode\">Boot Microsoft Windows installed in BIOS-MBR mode<\/span><br \/>\n<\/h5>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>GRUB(2) supports booting&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">bootmgr<\/code>&nbsp;directly and chainload of partition boot sector is no longer required to boot Windows in a BIOS-MBR setup.\n<\/div>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #DDBBBB;overflow:hidden;background-color:#FFDDDD;\">\n\t<strong>Warning:&nbsp;<\/strong>Take note that it is the&nbsp;<strong>system partition<\/strong>&nbsp;that has&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">bootmgr<\/code>, not your \"real\" Windows partition (usually C:). When showing all UUIDs with blkid, the system partition is the one with&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">LABEL=\"SYSTEM RESERVED\"<\/code>&nbsp;and is only about 100 MB in size (much like the boot partition for Arch). See<a class=\"external free\" href=\"http:\/\/en.wikipedia.org\/wiki\/System_partition_and_boot_partition\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">http:\/\/en.wikipedia.org\/wiki\/System_partition_and_boot_partition<\/a>&nbsp;for more info.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFind the UUID of the NTFS filesystem of the Windows's SYSTEM PARTITION where the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">bootmgr<\/code>&nbsp;and its files reside. For example, if Windows&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">bootmgr<\/code>&nbsp;exists at&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/media\/SYSTEM_RESERVED\/bootmgr<\/code>:\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFor Windows Vista\/7\/8:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-probe --target=fs_uuid \/media\/SYSTEM_RESERVED\/bootmgr\r\n69B235F6749E84CE\r\n<\/pre>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-probe --target=hints_string \/media\/SYSTEM_RESERVED\/bootmgr\r\n--hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong><code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-probe<\/code>&nbsp;should be run as root.\n<\/div>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>For Windows XP, replace&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">bootmgr<\/code>&nbsp;with&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">ntldr<\/code>&nbsp;in the above commands.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThen, add the below code to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/40_custom<\/code>&nbsp;or&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/custom.cfg<\/code>&nbsp;and regenerate&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;with&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkconfig<\/code>&nbsp;as explained above to boot Windows (XP, Vista, 7 or 8) installed in BIOS-MBR mode:\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFor Windows Vista\/7\/8:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">menuentry \"Microsoft Windows Vista\/7\/8 BIOS-MBR\" {\r\n    insmod part_msdos\r\n    insmod ntfs\r\n    insmod search_fs_uuid\r\n    insmod ntldr     \r\n    search --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 69B235F6749E84CE\r\n    ntldr \/bootmgr\r\n}<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFor Windows XP:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">menuentry \"Microsoft Windows XP\" {\r\n    insmod part_msdos\r\n    insmod ntfs\r\n    insmod search_fs_uuid\r\n    insmod ntldr     \r\n    search --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 69B235F6749E84CE\r\n    ntldr \/ntldr\r\n}\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/40_custom<\/code>&nbsp;can be used as a template to create&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/nn_custom<\/code>.&nbsp; Where nn defines the precendence, indicating the order the script is executed.&nbsp; The order scripts are executed determine the placement in the grub boot menu.\n<\/p>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>nn should be greater than 06 to ensure necessary scripts are executed first.\n<\/div>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t21\"><\/a><span class=\"mw-headline\" id=\"UEFI_systems_2\">UEFI systems<\/span><br \/>\n<\/h3>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>It is recommended to read the&nbsp;<a title=\"Unified Extensible Firmware Interface\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Unified_Extensible_Firmware_Interface\" style=\"color:#336699;text-decoration:none;\">UEFI<\/a>,&nbsp;<a title=\"GUID Partition Table\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GUID_Partition_Table\" style=\"color:#336699;text-decoration:none;\">GPT<\/a>&nbsp;and&nbsp;<a title=\"UEFI Bootloaders\" href=\"https:\/\/wiki.archlinux.org\/index.php\/UEFI_Bootloaders\" style=\"color:#336699;text-decoration:none;\">UEFI Bootloaders<\/a>&nbsp;pages before reading this part.\n<\/div>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t22\"><\/a><span class=\"mw-headline\" id=\"Hardware-Specific_UEFI_Examples\">Hardware-Specific UEFI Examples<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIt is well know that different motherboard manufactures implement UEFI differently.&nbsp; Users experiencing problems getting Grub\/EFI to work properly are encouraged to share detailed steps for hardware-specific cases where UEFI booting does not work as described below.&nbsp; In an effort to keep the parent&nbsp;<a title=\"GRUB\" class=\"mw-redirect\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB\" style=\"color:#336699;text-decoration:none;\">GRUB<\/a>&nbsp;article neat and tidy, see the&nbsp;<a title=\"GRUB EFI Examples\" href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB_EFI_Examples\" style=\"color:#336699;text-decoration:none;\">GRUB EFI Examples<\/a>&nbsp;page for these special cases.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t23\"><\/a><span class=\"mw-headline\" id=\"Install_grub-uefi_package\">Install grub-uefi package<\/span><br \/>\n<\/h4>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>Unless specified as EFI 1.x , EFI and UEFI terms are used interchangeably to denote UEFI 2.x firmware. Also unless stated explicitly, the instructions are general and not Mac specific. Some of them may not work or may be different in Macs. Apple's EFI implementation is neither a EFI 1.x version nor UEFI 2.x version but mixes up both. This kind of firmware does not fall under any one UEFI Specification version and is therefore not a standard UEFI firmware.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGRUB(2) UEFI bootloader is available in Arch Linux only from version 1.99~rc1. To install, first&nbsp;<a title=\"Unified Extensible Firmware Interface\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Unified_Extensible_Firmware_Interface#Detecting_UEFI_Firmware_Arch\" style=\"color:#336699;text-decoration:none;\">detect which UEFI firmware arch<\/a>&nbsp;you have (either x86_64 or i386).\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tDepending on that, install the appropriate package\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFor 64-bit aka x86_64 UEFI firmware:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># pacman -S grub-efi-x86_64\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFor 32-bit aka i386 UEFI firmware:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># pacman -S grub-efi-i386\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>Simply installing the package will not update the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">core.efi<\/code>&nbsp;file and the GRUB(2) modules in the UEFI System Partition. You need to do this manually using&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>&nbsp;as explained below.\n<\/div>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t24\"><\/a><span class=\"mw-headline\" id=\"Install_grub-uefi_boot_files\">Install grub-uefi boot files<\/span><br \/>\n<\/h4>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t25\"><\/a><span class=\"mw-headline\" id=\"Install_to_UEFI_System_Partition\">Install to UEFI System Partition<\/span><br \/>\n<\/h5>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>The below commands assume you are using&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-efi-x86_64<\/code>&nbsp;(for&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-efi-i386<\/code>&nbsp;replace&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">x86_64<\/code>&nbsp;with&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">i386<\/code>&nbsp;in the below commands).\n<\/div>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>To do this, you need to boot using UEFI and not the BIOS. If you booted by just copying the ISO file to the USB drive, you will need to follow&nbsp;<a title=\"Unified Extensible Firmware Interface\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Unified_Extensible_Firmware_Interface#Create_UEFI_bootable_USB_from_ISO\" style=\"color:#336699;text-decoration:none;\">this guide<\/a>&nbsp;or grub-install will show errors.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe UEFI system partition will need to be mounted at&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/efi\/<\/code>&nbsp;for the GRUB(2) install script to detect it:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># mkdir -p \/boot\/efi\r\n# mount -t vfat \/dev\/sdXY \/boot\/efi\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tInstall GRUB UEFI application to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/efi\/EFI\/arch_grub<\/code>&nbsp;and its modules to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/x86_64-efi<\/code>&nbsp;(recommended) using:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># modprobe dm-mod\r\n# grub-install --target=x86_64-efi --efi-directory=\/boot\/efi --bootloader-id=arch_grub --recheck --debug\r\n# mkdir -p \/boot\/grub\/locale\r\n# cp \/usr\/share\/locale\/en\\@quot\/LC_MESSAGES\/grub.mo \/boot\/grub\/locale\/en.mo\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>Without&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--target<\/code>&nbsp;or&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--directory<\/code>&nbsp;option, grub-install cannot determine for which firmware grub(2) is being installed. In such cases grub-install will show&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">source_dir doesn't exist. Please specify --target or --directory<\/code>&nbsp;message.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you want to install grub(2) modules and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;at the directory&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/efi\/EFI\/grub<\/code>&nbsp;and the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grubx64.efi<\/code>&nbsp;application at&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/efi\/EFI\/arch_grub<\/code>&nbsp;(ie. all the grub(2) uefi files inside the UEFISYS partition itself) use:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># modprobe dm-mod \r\n# grub-install --target=x86_64-efi --efi-directory=\/boot\/efi --bootloader-id=arch_grub --boot-directory=\/boot\/efi\/EFI --recheck --debug\r\n# mkdir -p \/boot\/efi\/EFI\/grub\/locale\r\n# cp \/usr\/share\/locale\/en\\@quot\/LC_MESSAGES\/grub.mo \/boot\/efi\/EFI\/grub\/locale\/en.mo\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--efi-directory<\/code>&nbsp;option mentions the mountpoint of UEFI SYSTEM PARTITION ,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--bootloader-id<\/code>mentions the name of the directory used to store the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grubx64.efi<\/code>&nbsp;file and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--boot-directory<\/code>&nbsp;mentions the directory wherein the actual modules will be installed (and into which&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;should be created).\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe actual paths are:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">&lt;efi-directory&gt;\/&lt;EFI or efi&gt;\/&lt;bootloader-id&gt;\/grubx64.efi\r\n<\/pre>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">&lt;boot-directory&gt;\/grub\/x86_64-efi\/&lt;all modules, grub.efi, core.efi, grub.cfg&gt;\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--bootloader-id<\/code>&nbsp;option does not change&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">&lt;boot-directory&gt;\/grub<\/code>, i.e. you cannot install the modules to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">&lt;boot-directory&gt;\/&lt;bootloader-id&gt;<\/code>, the path is hard-coded to be&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">&lt;boot-directory&gt;\/grub<\/code>.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIn&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--efi-directory=\/boot\/efi --boot-directory=\/boot\/efi\/EFI --bootloader-id=grub<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">&lt;efi-directory&gt;\/&lt;EFI or efi&gt;\/&lt;bootloader-id&gt; == &lt;boot-directory&gt;\/grub == \/boot\/efi\/EFI\/grub\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIn&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--efi-directory=\/boot\/efi --boot-directory=\/boot\/efi\/EFI --bootloader-id=arch_grub<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">&lt;efi-directory&gt;\/&lt;EFI or efi&gt;\/&lt;bootloader-id&gt; == \/boot\/efi\/EFI\/arch_grub\r\n&lt;boot-directory&gt;\/grub == \/boot\/efi\/EFI\/grub\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIn&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--efi-directory=\/boot\/efi --boot-directory=\/boot --bootloader-id=arch_grub<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">&lt;efi-directory&gt;\/&lt;EFI or efi&gt;\/&lt;bootloader-id&gt; == \/boot\/efi\/EFI\/arch_grub\r\n&lt;boot-directory&gt;\/grub == \/boot\/grub\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIn&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--efi-directory=\/boot\/efi --boot-directory=\/boot --bootloader-id=grub<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">&lt;efi-directory&gt;\/&lt;EFI or efi&gt;\/&lt;bootloader-id&gt; == \/boot\/efi\/EFI\/grub\r\n&lt;boot-directory&gt;\/grub == \/boot\/grub\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">&lt;efi-directory&gt;\/&lt;EFI or efi&gt;\/&lt;bootloader-id&gt;\/grubx64.efi<\/code>&nbsp;is an exact copy of&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">&lt;boot-directory&gt;\/grub\/x86_64-efi\/core.efi<\/code>.\n<\/p>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>In GRUB 2.00, the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>&nbsp;option&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--efi-directory<\/code>&nbsp;replaces&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--root-directory<\/code>&nbsp;and the latter is deprecated.\n<\/div>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>The options&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--efi-directory<\/code>&nbsp;and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--bootloader-id<\/code>&nbsp;are specific to GRUB(2) UEFI.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIn all the cases the UEFI SYSTEM PARTITION should be mounted for&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>&nbsp;to install&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grubx64.efi<\/code>&nbsp;in it, which will be launched by the firmware (using the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">efibootmgr<\/code>&nbsp;created boot entry in non-Mac systems).\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you notice carefully, there is no &lt;device_path&gt; option (Eg:&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/sda<\/code>) at the end of the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>command unlike the case of setting up GRUB(2) for BIOS systems. Any &lt;device_path&gt; provided will be ignored by the install script as UEFI bootloaders do not use MBR or Partition boot sectors at all.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tYou may now be able to UEFI boot your system by creating a&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;file by following&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Generate_GRUB2_UEFI_Config_file\" style=\"color:#336699;text-decoration:none;\">#Generate GRUB2 UEFI Config file<\/a>&nbsp;and&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Create_GRUB2_entry_in_the_Firmware_Boot_Manager\" style=\"color:#336699;text-decoration:none;\">#Create GRUB2 entry in the Firmware Boot Manager<\/a>.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t26\"><\/a><span class=\"mw-headline\" id=\"Generate_GRUB2_UEFI_Config_file\">Generate GRUB2 UEFI Config file<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFinally, generate a configuration for GRUB(2) (this is explained in greater detail in the Configuration section):\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o &lt;boot-directory&gt;\/grub\/grub.cfg\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>The file path is&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">&lt;boot-directory&gt;\/grub\/grub.cfg<\/code>, NOT&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">&lt;boot-directory&gt;\/grub\/x86_64-efi\/grub.cfg<\/code>.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you used&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--boot-directory=\/boot<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you used&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--boot-directory=\/boot\/efi\/EFI<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/efi\/EFI\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThis is independent of the value of&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--bootloader-id<\/code>&nbsp;option.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf GRUB2 complains about \"no suitable mode found\" while booting, try&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Correct_GRUB2_No_Suitable_Mode_Found_Error\" style=\"color:#336699;text-decoration:none;\">#Correct GRUB2 No Suitable Mode Found Error<\/a>.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t27\"><\/a><span class=\"mw-headline\" id=\"Create_GRUB2_entry_in_the_Firmware_Boot_Manager\">Create GRUB2 entry in the Firmware Boot Manager<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAs of grub-efi-x86_64 version 2.00,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-install<\/code>&nbsp;automatically tries to create a menu entry in the boot manager. If it doesn't, then see&nbsp;<a title=\"Beginners' Guide\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Beginners%27_Guide#GRUB\" style=\"color:#336699;text-decoration:none;\">Beginners' Guide#GRUB<\/a>&nbsp;for instructions to use&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">efibootmgr<\/code>&nbsp;to create a menu entry. However, the problem is likely to be that you haven't booted your CD\/USB in UEFI mode, as in<a title=\"Unified Extensible Firmware Interface\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Unified_Extensible_Firmware_Interface#Create_UEFI_bootable_USB_from_ISO\" style=\"color:#336699;text-decoration:none;\">Unified Extensible Firmware Interface#Create UEFI bootable USB from ISO<\/a>.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t28\"><\/a><span class=\"mw-headline\" id=\"Create_GRUB2_Standalone_UEFI_Application\">Create GRUB2 Standalone UEFI Application<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIt is possible to create a&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grubx64_standalone.efi<\/code>&nbsp;application which has all the modules embeddded in a memdisk within the uefi application, thus removing the need for having a separate directory populated with all the GRUB2 uefi modules and other related files. This is done using the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkstandalone<\/code>&nbsp;command which is included in&nbsp;<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/www.archlinux.org\/packages\/?name=grub-common\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">grub-common<\/a><\/span>&nbsp;&gt;= 1:1.99-6 package.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe easiest way to do this would be with the install command already mentioned before, but specifying the modules to include. For example:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkstandalone --directory=\"\/usr\/lib\/grub\/x86_64-efi\/\" --format=\"x86_64-efi\" --compression=\"xz\" \\\r\n--output=\"\/boot\/efi\/EFI\/arch_grub\/grubx64_standalone.efi\" &lt;any extra files you want to include&gt;\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grubx64_standalone.efi<\/code>&nbsp;file expects&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;to be within its $prefix which is&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">(memdisk)\/boot\/grub<\/code>. The memdisk is embedded within the efi app. The&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkstandlone<\/code>&nbsp;script allow passing files to be included in the memdisk image to be as the arguments to the script (in &lt;any extra files you want to include&gt;).\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you have the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;at&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/home\/user\/Desktop\/grub.cfg<\/code>, then create a temporary&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/home\/user\/Desktop\/boot\/grub\/<\/code>&nbsp;directory, copy the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/home\/user\/Desktop\/grub.cfg<\/code>&nbsp;to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/home\/user\/Desktop\/boot\/grub\/grub.cfg<\/code>, cd into&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/home\/user\/Desktop\/boot\/grub\/<\/code>&nbsp;and run:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkstandalone --directory=\"\/usr\/lib\/grub\/x86_64-efi\/\" --format=\"x86_64-efi\" --compression=\"xz\" \\\r\n--output=\"\/boot\/efi\/EFI\/arch_grub\/grubx64_standalone.efi\" \"boot\/grub\/grub.cfg\"\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe reason to cd into&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/home\/user\/Desktop\/boot\/grub\/<\/code>&nbsp;and to pass the file path as&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">boot\/grub\/grub.cfg<\/code>&nbsp;(notice the lack of a leading slash - boot\/ vs \/boot\/ ) is because&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">dir1\/dir2\/file<\/code>&nbsp;is included as&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">(memdisk)\/dir1\/dir2\/file<\/code>&nbsp;by the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkstandalone<\/code>&nbsp;script.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you pass&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/home\/user\/Desktop\/grub.cfg<\/code>&nbsp;the file will be included as&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">(memdisk)\/home\/user\/Desktop\/grub.cfg<\/code>. If you pass&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/home\/user\/Desktop\/boot\/grub\/grub.cfg<\/code>the file will be included as&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">(memdisk)\/home\/user\/Desktop\/boot\/grub\/grub.cfg<\/code>. That is the reason for cd'ing into&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/home\/user\/Desktop\/boot\/grub\/<\/code>&nbsp;and passing&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">boot\/grub\/grub.cfg<\/code>, to include the file as&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">(memdisk)\/boot\/grub\/grub.cfg<\/code>, which is what&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.efi<\/code>&nbsp;expects the file to be.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tYou need to create an UEFI Boot Manager entry for&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/efi\/EFI\/arch_grub\/grubx64_standalone.efi<\/code>&nbsp;using&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">efibootmgr<\/code>. Follow&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Create_GRUB2_entry_in_the_Firmware_Boot_Manager\" style=\"color:#336699;text-decoration:none;\">#Create GRUB2 entry in the Firmware Boot Manager<\/a>.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t29\"><\/a><span class=\"mw-headline\" id=\"Multiboot_in_UEFI\">Multiboot in UEFI<\/span><br \/>\n<\/h4>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t30\"><\/a><span class=\"mw-headline\" id=\"Chainload_Microsoft_Windows_x86_64_UEFI-GPT\">Chainload Microsoft Windows x86_64 UEFI-GPT<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFind the UUID of the FAT32 filesystem in the UEFI SYSTEM PARTITION where the Windows UEFI Bootloader files reside. For example, if Windows&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">bootmgfw.efi<\/code>&nbsp;exists at&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/efi\/EFI\/Microsoft\/Boot\/bootmgfw.efi<\/code>&nbsp;(ignore the upper-lower case differences since that is immaterial in FAT filesystem):\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-probe --target=fs_uuid \/boot\/efi\/EFI\/Microsoft\/Boot\/bootmgfw.efi\r\n1ce5-7f28\r\n<\/pre>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-probe --target=hints_string \/boot\/efi\/EFI\/Microsoft\/Boot\/bootmgfw.efi\r\n--hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong><code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-probe<\/code>&nbsp;should be run as root.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThen, add this code to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/40_custom<\/code>&nbsp;to chainload Windows x86_64 (Vista SP1+, 7 or 8) installed in UEFI-GPT mode:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">menuentry \"Microsoft Windows Vista\/7\/8 x86_64 UEFI-GPT\" {\r\n    insmod part_gpt\r\n    insmod fat\r\n    insmod search_fs_uuid\r\n    insmod chain\r\n    search --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 1ce5-7f28\r\n    chainloader \/efi\/Microsoft\/Boot\/bootmgfw.efi\r\n}\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAfterwards remake&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/grub.cfg<\/code>\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t31\"><\/a><span class=\"mw-headline\" id=\"Configuration\">Configuration<\/span><br \/>\n<\/h2>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tYou can also choose to automatically generate or manually edit&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>.\n<\/p>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>For EFI systems, if GRUB2 was installed with the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--boot-directory<\/code>&nbsp;option set, the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;file must be placed in the same directory as&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grubx64.efi<\/code>. Otherwise, the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;file goes in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/<\/code>, just like in the BIOS version of GRUB2.\n<\/div>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>Here is a quite complete description of how to configure GRUB2:<a class=\"external free\" href=\"http:\/\/members.iinet.net\/~herman546\/p20\/GRUB2%20Configuration%20File%20Commands.html\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">http:\/\/members.iinet.net\/~herman546\/p20\/GRUB2%20Configuration%20File%20Commands.html<\/a>\n<\/div>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t32\"><\/a><span class=\"mw-headline\" id=\"Automatically_generating_using_grub-mkconfig_.28Recommended.29\">Automatically generating using grub-mkconfig (Recommended)<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe GRUB2&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">menu.lst<\/code>&nbsp;equivalent configuration files are&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>&nbsp;and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/*<\/code>.&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkconfig<\/code>&nbsp;uses these files to generate&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>. By default the script outputs to stdout. To generate a&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;file run the command:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/10_linux<\/code>&nbsp;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&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/40_custom<\/code>&nbsp;or&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/custom.cfg<\/code>\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t33\"><\/a><span class=\"mw-headline\" id=\"Additional_arguments\">Additional arguments<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo pass custom additional arguments to the Linux image, you can set the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">GRUB_CMDLINE_LINUX<\/code>&nbsp;variable in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFor example, use&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">GRUB_CMDLINE_LINUX=\"resume=\/dev\/sdaX\"<\/code>&nbsp;where&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">sda<strong>X<\/strong><\/code>&nbsp;is your swap partition to enable resume after hibernation.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tYou can also use&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">GRUB_CMDLINE_LINUX=\"resume=\/dev\/disk\/by-uuid\/${swap_uuid}\"<\/code>, where&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">${swap_uuid}<\/code>is the&nbsp;<a title=\"Persistent block device naming\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Persistent_block_device_naming\" style=\"color:#336699;text-decoration:none;\">UUID<\/a>&nbsp;of your swap partition.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tMultiple entries are separated by spaces within the double quotes.&nbsp; So, for users who want both resume and systemd it would look like this:<code style=\"padding:0.1em 0.3em;display:inline-block;\">GRUB_CMDLINE_LINUX=\"resume=\/dev\/sdaX init=\/usr\/lib\/systemd\/systemd\"<\/code>\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tSee&nbsp;<a title=\"Kernel parameters\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Kernel_parameters\" style=\"color:#336699;text-decoration:none;\">Kernel parameters<\/a>&nbsp;for more info.\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t34\"><\/a><span class=\"mw-headline\" id=\"Manually_creating_grub.cfg\">Manually creating grub.cfg<\/span><br \/>\n<\/h3>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #DDBBBB;overflow:hidden;background-color:#FFDDDD;\">\n\t<strong>Warning:&nbsp;<\/strong>Editing this file is strongly&nbsp;<em>not<\/em>&nbsp;recommended. The file is generated by the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkconfig<\/code>command, and it is best to edit your&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>&nbsp;or one of the scripts in the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d<\/code>folder.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tA basic GRUB config file uses the following options\n<\/p>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\t<code style=\"padding:0.1em 0.3em;display:inline-block;\">(hdX,Y)<\/code>&nbsp;is the partition&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">Y<\/code>&nbsp;on disk&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">X<\/code>, partition numbers starting at 1, disk numbers starting at 0\n\t<\/li>\n<li>\n\t\t<code style=\"padding:0.1em 0.3em;display:inline-block;\">set default=N<\/code>&nbsp;is the default boot entry that is chosen after timeout for user action\n\t<\/li>\n<li>\n\t\t<code style=\"padding:0.1em 0.3em;display:inline-block;\">set timeout=M<\/code>&nbsp;is the time&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">M<\/code>&nbsp;to wait in seconds for a user selection before default is booted\n\t<\/li>\n<li>\n\t\t<code style=\"padding:0.1em 0.3em;display:inline-block;\">menuentry \"title\" {entry options}<\/code>&nbsp;is a boot entry titled&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">title<\/code>\n\t<\/li>\n<li>\n\t\t<code style=\"padding:0.1em 0.3em;display:inline-block;\">set root=(hdX,Y)<\/code>&nbsp;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 (<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/<\/code>)\n\t<\/li>\n<\/ul>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAn example configuration:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;padding-bottom:0.8em;margin-bottom:0px;border-bottom-color:currentcolor;border-bottom-width:medium;border-bottom-style:none;\">\/boot\/grub\/grub.cfg\r\n<\/pre>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;padding-top:0.8em;margin-top:0px;border-top-style:dashed;\"># Config file for GRUB2 - The GNU GRand Unified Bootloader\r\n# \/boot\/grub\/grub.cfg\r\n\r\n# DEVICE NAME CONVERSIONS\r\n#\r\n#  Linux           Grub\r\n# -------------------------\r\n#  \/dev\/fd0        (fd0)\r\n#  \/dev\/sda        (hd0)\r\n#  \/dev\/sdb2       (hd1,2)\r\n#  \/dev\/sda3       (hd0,3)\r\n#\r\n\r\n# Timeout for menu\r\nset timeout=5\r\n\r\n# Set default boot entry as Entry 0\r\nset default=0\r\n\r\n# (0) Arch Linux\r\nmenuentry \"Arch Linux\" {\r\n    set root=(hd0,1)\r\n    linux \/vmlinuz-linux root=\/dev\/sda3 ro\r\n    initrd \/initramfs-linux.img\r\n}\r\n\r\n## (1) Windows\r\n#menuentry \"Windows\" {\r\n#set root=(hd0,3)\r\n#chainloader +1\r\n#}\r\n<\/pre>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t35\"><\/a><span class=\"mw-headline\" id=\"Dual-booting\">Dual-booting<\/span><br \/>\n<\/h3>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>If you want GRUB2 to automatically search for other systems, you may wish to install&nbsp;<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/www.archlinux.org\/packages\/?name=os-prober\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">os-prober<\/a><\/span>.\n<\/div>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t36\"><\/a><span class=\"mw-headline\" id=\"Using_grub-mkconfig\">Using grub-mkconfig<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe best way to add other entries is editing the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/40_custom<\/code>&nbsp;or&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/custom.cfg<\/code>&nbsp;. The entries in this file will be automatically added when running&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkconfig<\/code>.After adding the new lines, run:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/grub\/grub.cfg \r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tto generate an updated&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>.\n<\/p>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t37\"><\/a><span class=\"mw-headline\" id=\"With_GNU.2FLinux\">With GNU\/Linux<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAssuming that the other distro is on partition&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">sda2<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">menuentry \"Other Linux\" {\r\nset root=(hd0,2)\r\nlinux \/boot\/vmlinuz (add other options here as required)\r\ninitrd \/boot\/initrd.img (if the other kernel uses\/needs one)\r\n}\r\n<\/pre>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t38\"><\/a><span class=\"mw-headline\" id=\"With_FreeBSD\">With FreeBSD<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tRequires that FreeBSD is installed on a single partition with UFS. Assuming it is installed on&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">sda4<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">menuentry \"FreeBSD\" {\r\nset root=(hd0,4)\r\nchainloader +1\r\n}\r\n<\/pre>\n<h5 style=\"color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t39\"><\/a><span class=\"mw-headline\" id=\"With_Windows\">With Windows<\/span><br \/>\n<\/h5>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThis assumes that your Windows partition is&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">sda3<\/code>. 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&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">sda3<\/code>.\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># (2) Windows XP\r\nmenuentry \"Windows XP\" {\r\n    set root=(hd0,3)\r\n    chainloader (hd0,3)+1\r\n}\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf 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&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">drivemap<\/code>. Assuming GRUB is on&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">hd0<\/code>&nbsp;and Windows is on&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">hd2<\/code>, you need to add the following after&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">set root<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">drivemap -s hd0 hd2\r\n<\/pre>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t40\"><\/a><span class=\"mw-headline\" id=\"With_Windows_via_EasyBCD_and_NeoGRUB\">With Windows via EasyBCD and NeoGRUB<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tSince EasyBCD's NeoGRUB currently does not understand the GRUB2 menu format, chainload to it by replacing the contents of your&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">C:\\NST\\menu.lst<\/code>&nbsp;file with lines similar to the following:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">default 0\r\ntimeout 1\r\n<\/pre>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">title       Chainload into GRUB v2\r\nroot        (hd0,7)\r\nkernel      \/boot\/grub\/i386-pc\/core.img\r\n<\/pre>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t41\"><\/a><span class=\"mw-headline\" id=\"Visual_Configuration\">Visual Configuration<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIn GRUB2 it is possible, by default, to change the look of the menu. Make sure to initialize, if not done already, GRUB2 graphical terminal, gfxterm, with proper video mode, gfxmode, in GRUB2. This can be seen in the section&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Correct_GRUB2_No_Suitable_Mode_Found_Error\" style=\"color:#336699;text-decoration:none;\">#Correct_GRUB2_No_Suitable_Mode_Found_Error<\/a>. This video mode is passed by GRUB2 to the linux kernel via 'gfxpayload' so any visual configurations need this mode in order to be in effect.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t42\"><\/a><span class=\"mw-headline\" id=\"Setting_the_framebuffer_resolution\">Setting the framebuffer resolution<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGRUB2 can set the framebuffer for both GRUB2 itself and the kernel. The old&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">vga=<\/code>&nbsp;way is deprecated. The preferred method is editing&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>&nbsp;as the following sample:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_GFXMODE=1024x768x32\r\nGRUB_GFXPAYLOAD_LINUX=keep\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo generate the changes, run:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">gfxpayload<\/code>&nbsp;property will make sure the kernel keeps the resolution.\n<\/p>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>If this example does not work for you try to replace&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">gfxmode=\"1024x768x32\"<\/code>&nbsp;by&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">vbemode=\"0x105\"<\/code>. Remember to replace the specified resolution with one suitable for your screen.\n<\/div>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>To show all the modes you can use&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\"># hwinfo --framebuffer<\/code>&nbsp;(hwinfo is available in [community]), while at GRUB2 prompt you can use the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">vbeinfo<\/code>&nbsp;command.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf this method does not work for you, the deprecated&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">vga=<\/code>&nbsp;method will still work. Justadd it next to the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\"GRUB_CMDLINE_LINUX_DEFAULT=\"<\/code>&nbsp;line in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>for eg:&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\"GRUB_CMDLINE_LINUX_DEFAULT=\"quiet splash vga=792\"<\/code>&nbsp;will give you a&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">1024x768<\/code>&nbsp;resolution.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tYou can choose one of these resolutions:&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">640\u00d7480<\/code>,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">800\u00d7600<\/code>,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">1024\u00d7768<\/code>,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">1280\u00d71024<\/code>,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">1600\u00d71200<\/code>,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">1920\u00d71200<\/code>\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t43\"><\/a><span class=\"mw-headline\" id=\"915resolution_hack\">915resolution hack<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tSome times for Intel graphic adapters neither&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\"># hwinfo --framebuffer<\/code>&nbsp;nor&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">vbeinfo<\/code>&nbsp;will show you the desired resolution. In this case you can use&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">915resolution<\/code>&nbsp;hack. This hack will temporarily modify video BIOS and add needed resolution. See&nbsp;<a class=\"external text\" href=\"http:\/\/915resolution.mango-lang.org\/\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">915resolution's home page<\/a>\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIn the following I will proceed with the example for my system. Please adjust the recipe for your needs. First you need to find a video mode which will be modified later. For that, run&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">915resolution<\/code>&nbsp;in GRUB2 command shell:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">915resolution -l\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe output will be something like:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">Intel 800\/900 Series VBIOS Hack&nbsp;: version 0.5.3\r\n...\r\nMode 30&nbsp;: 640x480, 8 bits\/pixel\r\n...\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tNext, our purpose is to overwrite mode 30. (You can choose what ever mode you want.) In the file&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/00_header<\/code>&nbsp;just before the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">set gfxmode=${GRUB_GFXMODE<\/code>} line insert:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">915resolution 30 1440 900\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tHere we are overwriting the mode&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">30<\/code>&nbsp;with&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">1440x900<\/code>&nbsp;resolution. Lastly we need to set&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">GRUB_GFXMODE<\/code>&nbsp;as described earlier, regenerate GRUB2 configuration file and reboot to test changes:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n# reboot\r\n<\/pre>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t44\"><\/a><span class=\"mw-headline\" id=\"Background_image_and_bitmap_fonts\">Background image and bitmap fonts<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGRUB2 comes with support for background images and bitmap fonts in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">pf2<\/code>&nbsp;format. The unifont font is included in the&nbsp;<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/www.archlinux.org\/packages\/?name=grub-common\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">grub-common<\/a><\/span>&nbsp;package under the filename&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">unicode.pf2<\/code>, or, as only ASCII characters under the name&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">ascii.pf2<\/code>.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tImage formats supported include tga, png and jpeg, providing the correct modules are loaded. The maximum supported resolution depends on your hardware.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tMake sure you have set up the proper&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Setting_the_framebuffer_resolution\" style=\"color:#336699;text-decoration:none;\">framebuffer resolution<\/a>.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tEdit&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>&nbsp;like this:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_BACKGROUND=\"\/boot\/grub\/myimage\"\r\n#GRUB_THEME=\"\/path\/to\/gfxtheme\"\r\nGRUB_FONT=\"\/path\/to\/font.pf2\"\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>If you have installed GRUB on a separate partition,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/myimage<\/code>&nbsp;becomes&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/grub\/myimage<\/code>.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo generate the changes and add the information into&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>, run:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf adding the splash image was successful, the user will see&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\"Found background image...\"<\/code>&nbsp;in the terminal as the command is executed. If this phrase is not seen, the image information was probably not incorporated into the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;file.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf the image is not displayed, check:\n<\/p>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tThe path and the filename in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>&nbsp;are correct.\n\t<\/li>\n<li>\n\t\tThe image is of the proper size and format (tga, png, 8-bit jpg).\n\t<\/li>\n<li>\n\t\tThe image was saved in the RGB mode, and is not indexed.\n\t<\/li>\n<li>\n\t\tThe console mode is not enabled in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>.\n\t<\/li>\n<li>\n\t\tThe command&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkconfig<\/code>&nbsp;must be executed to place the background image information into the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/grub.cfg<\/code>&nbsp;file.\n\t<\/li>\n<\/ul>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t45\"><\/a><span class=\"mw-headline\" id=\"Theme\">Theme<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tHere is an example for configuring Starfield theme which was included in GRUB2 package.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tEdit&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_THEME=\"\/usr\/share\/grub\/themes\/starfield\/theme.txt\"\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGenerate the changes:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf configuring the theme was successful, you'll see&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">Found theme: \/usr\/share\/grub\/themes\/starfield\/theme.txt<\/code>&nbsp;in the terminal.Your splash image will usually not be displayed when using a theme.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t46\"><\/a><span class=\"mw-headline\" id=\"Menu_colors\">Menu colors<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tYou can set the menu colors in GRUB2. The available colors for GRUB2 can be found in&nbsp;<a class=\"external text\" href=\"https:\/\/www.gnu.org\/software\/grub\/manual\/html_node\/Theme-file-format.html\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">the GRUB Manual<\/a>.Here is an example:\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tEdit&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_COLOR_NORMAL=\"light-blue\/black\"\r\nGRUB_COLOR_HIGHLIGHT=\"light-cyan\/blue\"\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGenerate the changes:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t47\"><\/a><span class=\"mw-headline\" id=\"Hidden_menu\">Hidden menu<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tOne of the unique features of GRUB2 is hiding\/skipping the menu and showing it by holding&nbsp;<code style=\"padding:0.1em 0.3em;font-weight:bold;display:inline-block;background-color:#EBF1F5;\">Esc<\/code>&nbsp;when needed. You can also adjust whether you want to see the timeout counter.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tEdit&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>&nbsp;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:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_HIDDEN_TIMEOUT=5\r\nGRUB_HIDDEN_TIMEOUT_QUIET=false\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tand run:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t48\"><\/a><span class=\"mw-headline\" id=\"Disable_framebuffer\">Disable framebuffer<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tUsers who use NVIDIA proprietary driver might wish to disable GRUB2's framebuffer as it can cause problems with the binary driver.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo disable framebuffer, edit&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>&nbsp;and uncomment the following line:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_TERMINAL_OUTPUT=console\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tand run:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAnother option if you want to keep the framebuffer in GRUB2 is to revert to text mode just before starting the kernel. To do that modify the variable in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_GFXPAYLOAD_LINUX=text\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tand rebuild the configuration as before.\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t49\"><\/a><span class=\"mw-headline\" id=\"Other_Options\">Other Options<\/span><br \/>\n<\/h3>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t50\"><\/a><span class=\"mw-headline\" id=\"LVM\">LVM<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you use&nbsp;<a title=\"LVM\" href=\"https:\/\/wiki.archlinux.org\/index.php\/LVM\" style=\"color:#336699;text-decoration:none;\">LVM<\/a>&nbsp;for your&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>, add the following before menuentry lines:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">insmod lvm\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tand specify your root in the menuentry as:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">set root=lvm\/<em>lvm_group_name<\/em>-<em>lvm_logical_boot_partition_name<\/em> <\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tExample:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># (0) Arch Linux\r\nmenuentry \"Arch Linux\" {\r\ninsmod lvm\r\nset root=lvm\/VolumeGroup-lv_boot\r\n# you can only set following two lines\r\nlinux \/vmlinuz-linux root=\/dev\/mapper\/VolumeGroup-root ro\r\ninitrd \/initramfs-linux.img\r\n}\r\n<\/pre>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t51\"><\/a><span class=\"mw-headline\" id=\"RAID\">RAID<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGRUB2 provides convenient handling of RAID volumes. You need to add&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">insmod mdraid<\/code>&nbsp;which allows you to address the volume natively. For example,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/md0<\/code>&nbsp;becomes:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">set root=(md0)\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\twhereas a partitioned RAID volume (e.g.&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/md0p1<\/code>) becomes:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">set root=(md0,1)\r\n<\/pre>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t52\"><\/a><span class=\"mw-headline\" id=\"Persistent_block_device_naming\">Persistent block device naming<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tOne naming scheme for&nbsp;<a title=\"Persistent block device naming\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Persistent_block_device_naming\" style=\"color:#336699;text-decoration:none;\">Persistent block device naming<\/a>&nbsp;is the use of globally unique UUIDs to detect partitions instead of the \"old\"&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/sd*<\/code>. Advantages are covered up in the above linked article.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tPersistent naming via filesystem UUIDs are used by default in GRUB2.\n<\/p>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>The&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub.cfg<\/code>&nbsp;file needs regeneration with the new UUID in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>&nbsp;every time a relevant filesystem is resized or recreated. Remember this when modifying partitions &amp; filesystems with a Live-CD.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tWhether to use UUIDs is controlled by an option in \/etc\/default\/grub:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># GRUB_DISABLE_LINUX_UUID=true<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tEither way, do not forget to generate the changes:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkconfig -o \/boot\/grub\/grub.cfg<\/pre>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t53\"><\/a><span class=\"mw-headline\" id=\"Using_Labels\">Using Labels<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIt is possible to use labels, human-readable strings attached to filesystems, by using the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--label<\/code>&nbsp;option to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">search<\/code>. First of all, label your existing partition:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># tune2fs -L &lt;LABEL&gt; &lt;PARTITION&gt;\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThen, add an entry using labels. An example of this:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">menuentry \"Arch Linux, session texte\" {\r\n    search --label --set=root archroot\r\n    linux \/boot\/vmlinuz-linux root=\/dev\/disk\/by-label\/archroot ro\r\n    initrd \/boot\/initramfs-linux.img\r\n}\r\n<\/pre>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t54\"><\/a><span class=\"mw-headline\" id=\"Recall_previous_entry\">Recall previous entry<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGRUB2 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&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>&nbsp;and change the setting of&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">GRUB_DEFAULT<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_DEFAULT=saved\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThis ensures that GRUB will default to the saved entry. To enable saving the selected entry, add the following line to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_SAVEDEFAULT=true\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>Manually added menu items, eg Windows in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/40_custom<\/code>&nbsp;or&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/custom.cfg<\/code>&nbsp;, will need&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">savedefault<\/code>&nbsp;added. Remember to regenerate your configuration file.\n<\/div>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t55\"><\/a><span class=\"mw-headline\" id=\"Security\">Security<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you want to secure GRUB2 so it is not possible for anyone to change boot parameters or use the command line, you can add a user\/password combination to GRUB2's configuration files. To do this, run the command&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkpasswd-pbkdf2<\/code>. Enter a password and confirm it. The output will look like this:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">Your PBKDF2 is grub.pbkdf2.sha512.10000.C8ABD3E93C4DFC83138B0C7A3D719BC650E6234310DA069E6FDB0DD4156313DA3D0D9BFFC2846C21D5A2DDA515114CF6378F8A064C94198D0618E70D23717E82.509BFA8A4217EAD0B33C87432524C0B6B64B34FBAD22D3E6E6874D9B101996C5F98AB1746FE7C7199147ECF4ABD8661C222EEEDB7D14A843261FFF2C07B1269A<\/pre>\n<p><span style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">Then, add the following to&nbsp;<\/span><code style=\"color:#333333;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/00_header<\/code><span style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">:<\/span> <\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">cat &lt;&lt; EOF\r\n\r\nset superusers=\"username\"\r\npassword_pbkdf2 username &lt;password&gt;\r\n\r\nEOF<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\twhere&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">&lt;password&gt;<\/code>&nbsp;is the string generated by&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkpasswd_pbkdf2<\/code>.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tRegenerate your configuration file. Your GRUB2 command line, boot parameters and all boot entries are now protected.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThis can be relaxed and further customized with more users as described in the \"Security\" part of&nbsp;<a class=\"external text\" href=\"https:\/\/www.gnu.org\/software\/grub\/manual\/grub.html#Security\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">the GRUB manual<\/a>.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t56\"><\/a><span class=\"mw-headline\" id=\"Root_Encryption\">Root Encryption<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo let GRUB2 automatically add the kernel parameters for root encryption,add&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">cryptdevice=\/dev\/yourdevice:label<\/code>&nbsp;to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">GRUB_CMDLINE_LINUX<\/code>&nbsp;in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/default\/grub<\/code>.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tExample with root mapped to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/mapper\/root<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_CMDLINE_LINUX=\"cryptdevice=\/dev\/sda2:root\"\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAlso, disable the usage of UUIDs for the rootfs:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">GRUB_DISABLE_LINUX_UUID=true\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tRegenerate the configuration.\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t57\"><\/a><span class=\"mw-headline\" id=\"Boot_non-default_entry_only_once\">Boot non-default entry only once<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe command&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-reboot<\/code>&nbsp;is very helpful to boot another entry than the default only once. GRUB2 loads the entry passed in the first command line argument, when the system is rebooted the next time. Most importantly GRUB2 returns to loading the default entry for all future booting. Changing the configuration file or selecting an entry in the GRUB2 menu is not necessary.\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t58\"><\/a><span class=\"mw-headline\" id=\"Booting_an_ISO_Directly_From_GRUB2\">Booting an ISO Directly From GRUB2<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tEdit&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/etc\/grub.d\/40_custom<\/code>&nbsp;or&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/custom.cfg<\/code>&nbsp;to add an entry for the target ISO. When finished, update the GRUB menu as with the usual&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkconfig -o \/boot\/grub\/grub.cfg<\/code>&nbsp;(as root).\n<\/p>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t59\"><\/a><span class=\"mw-headline\" id=\"Arch_ISO\">Arch ISO<\/span><br \/>\n<\/h4>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>The example assumes that the iso is in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/archives<\/code>&nbsp;on&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">hd0,6<\/code>. Users must adjust the location and hdd\/partition in ALL of the lines below to match their systems. However, if booting the ISO from USB on a computer which also has one internal HDD, then it needs to be&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">hd0,Y<\/code>&nbsp;with&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">sdbY<\/code>, instead of&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">sdaY<\/code>.\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<strong>Example using x86_64<\/strong>\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">menuentry \"Archlinux-2013.01.04-dual.iso\" --class iso {\r\n  set isofile=\"\/archives\/archlinux-2013.01.04-dual.iso\"\r\n  loopback loop (hd0,6)$isofile\r\n  linux (loop)\/arch\/boot\/x86_64\/vmlinuz archisolabel=ARCH_201301 img_dev=\/dev\/sda6 img_loop=$isofile earlymodules=loop\r\n  initrd (loop)\/arch\/boot\/x86_64\/archiso.img\r\n}\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<strong>Example using i686<\/strong>\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">menuentry \"Archlinux-2013.01.04-dual.iso\" --class iso {\r\n  set isofile=\"\/archives\/archlinux-2013.01.04-dual.iso\"\r\n  loopback loop (hd0,6)$isofile\r\n  linux (loop)\/arch\/boot\/i686\/vmlinuz archisolabel=ARCH_201301 img_dev=\/dev\/sda6 img_loop=$isofile earlymodules=loop\r\n  initrd (loop)\/arch\/boot\/i686\/archiso.img\r\n}\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBDDBB;overflow:hidden;background-color:#DDFFDD;\">\n\t<strong>Tip:&nbsp;<\/strong>For thumbdrives, use&nbsp;<a title=\"Persistent block device naming\" href=\"https:\/\/wiki.archlinux.org\/index.php\/Persistent_block_device_naming\" style=\"color:#336699;text-decoration:none;\">Persistent block device names<\/a>&nbsp;for the \"img_dev\" kernel parameter.&nbsp;<strong>Ex:<\/strong>img_dev=\/dev\/disk\/by-label\/CORSAIR\n<\/div>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t60\"><\/a><span class=\"mw-headline\" id=\"Ubuntu_ISO\">Ubuntu ISO<\/span><br \/>\n<\/h4>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>The example assumes that the iso is in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/archives<\/code>&nbsp;on&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">hd0,6<\/code>. Users must adjust the location and hdd\/partition in the lines below to match their systems.\n<\/div>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">menuentry \"ubuntu-12.04-desktop-amd64.iso\" {\r\n    set isofile=\"\/archives\/ubuntu-12.04-desktop-amd64.iso\"\r\n    loopback loop (hd0,6)$isofile\r\n    linux (loop)\/casper\/vmlinuz boot=casper iso-scan\/filename=$isofile quiet noeject noprompt splash --\r\n    initrd (loop)\/casper\/initrd.lz\r\n}\r\n<\/pre>\n<h4 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t61\"><\/a><span class=\"mw-headline\" id=\"Other_ISOs\">Other ISOs<\/span><br \/>\n<\/h4>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tOther working configurations from&nbsp;<a class=\"external text\" href=\"http:\/\/askubuntu.com\/questions\/141940\/how-to-boot-live-iso-images\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">link Source<\/a>.\n<\/p>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t62\"><\/a><span class=\"mw-headline\" id=\"Using_the_command_shell\">Using the command shell<\/span><br \/>\n<\/h2>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tSince the MBR is too small to store all GRUB2 modules, only the menu and a few basic commands reside there. The majority of GRUB2 functionality remains in modules in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub<\/code>, which are inserted as needed. In error conditions (e.g. if the partition layout changes) GRUB2 may fail to boot. When this happens, a command shell may appear.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGRUB2 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:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">sh:grub&gt;\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf there is a more serious problem (e.g. GRUB cannot find required files), you may instead be dropped to the \"rescue\" shell:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">grub rescue&gt;\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe 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:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">grub rescue&gt; set prefix=(hdX,Y)\/boot\/grub\r\ngrub rescue&gt; insmod (hdX,Y)\/boot\/grub\/i386-pc\/normal.mod\r\nrescue:grub&gt; normal\r\n<\/pre>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t63\"><\/a><span class=\"mw-headline\" id=\"Pager_support\">Pager support<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tGRUB2 supports pager for reading commands that provide long output (like the help command). This works only in normal shell mode and not in rescue mode. To enable pager, in GRUB2 command shell type:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">sh:grub&gt; set pager=1\r\n<\/pre>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t64\"><\/a><span class=\"mw-headline\" id=\"GUI_configuration_tools\">GUI configuration tools<\/span><br \/>\n<\/h2>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tFollowing package may be installed from&nbsp;<a title=\"AUR\" class=\"mw-redirect\" href=\"https:\/\/wiki.archlinux.org\/index.php\/AUR\" style=\"color:#336699;text-decoration:none;\">AUR<\/a>\n<\/p>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\t<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/aur.archlinux.org\/packages\/grub-customizer\/\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">grub-customizer<\/a><\/span>&nbsp;(requires gettext gksu gtkmm hicolor-icon-theme openssl)<\/p>\n<dl>\n<dd>\n\t\t\t\tCustomize the bootloader (GRUB2 or BURG)\n\t\t\t<\/dd>\n<\/dl>\n<\/li>\n<li>\n\t\t<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/aur.archlinux.org\/packages\/grub2-editor\/\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">grub2-editor<\/a><\/span>&nbsp;(requires kdelibs)<\/p>\n<dl>\n<dd>\n\t\t\t\tA KDE4 control module for configuring the GRUB2 bootloader\n\t\t\t<\/dd>\n<\/dl>\n<\/li>\n<li>\n\t\t<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/aur.archlinux.org\/packages\/kcm-grub2\/\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">kcm-grub2<\/a><\/span>&nbsp;(requires kdelibs python2-qt kdebindings-python)<\/p>\n<dl>\n<dd>\n\t\t\t\tThis Kcm module manages the most common settings of Grub2.\n\t\t\t<\/dd>\n<\/dl>\n<\/li>\n<li>\n\t\t<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/aur.archlinux.org\/packages\/startupmanager\/\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">startupmanager<\/a><\/span>&nbsp;(requires gnome-python imagemagick yelp python2 xorg-xrandr)<\/p>\n<dl>\n<dd>\n\t\t\t\tGUI app for changing the settings of GRUB, GRUB2, Usplash and Splashy\n\t\t\t<\/dd>\n<\/dl>\n<\/li>\n<\/ul>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t65\"><\/a><span class=\"mw-headline\" id=\"parttool_for_hide.2Funhide\">parttool for hide\/unhide<\/span><br \/>\n<\/h2>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you have a Windows 9x paradigm with hidden C:\\ disks GRUB can hide\/unhide it using&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">parttool<\/code>. For example, to boot the third C:\\ disk of three Windows 9x installations on the CLI enter the CLI and:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">parttool hd0,1 hidden+ boot-\r\nparttool hd0,2 hidden+ boot-\r\nparttool hd0,3 hidden- boot+\r\nset root=hd0,3\r\nchainloader +1\r\nboot\r\n<\/pre>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t66\"><\/a><span class=\"mw-headline\" id=\"Using_the_rescue_console\">Using the rescue console<\/span><br \/>\n<\/h2>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tSee&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Using_the_command_shell\" style=\"color:#336699;text-decoration:none;\">#Using the command shell<\/a>&nbsp;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.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThe available commands in GRUB rescue include&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">insmod<\/code>,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">ls<\/code>,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">set<\/code>, and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">unset<\/code>. This example uses&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">set<\/code>and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">insmod<\/code>.&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">set<\/code>&nbsp;modifies variables and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">insmod<\/code>&nbsp;inserts new modules to add functionality.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tBefore starting, the user must know the location of their&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>&nbsp;partition (be it a separate partition, or a subdirectory under their root):\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">grub rescue&gt; set prefix=(hdX,Y)\/boot\/grub\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\twhere X is the physical drive number and Y is the partition number.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tTo expand console capabilities, insert the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">linux<\/code>&nbsp;module:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">grub rescue&gt; insmod (hdX,Y)\/boot\/grub\/linux.mod\r\n<\/pre>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #BBBBDD;overflow:hidden;background-color:#DDDDFF;\">\n\t<strong>Note:&nbsp;<\/strong>With a separate boot partition, omit&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>&nbsp;from the path, (i.e. type&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">set prefix=(hdX,Y)\/grub<\/code>and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">insmod (hdX,Y)\/grub\/linux.mod<\/code>).\n<\/div>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThis introduces the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">linux<\/code>&nbsp;and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">initrd<\/code>&nbsp;commands, which should be familiar (see&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Configuration\" style=\"color:#336699;text-decoration:none;\">#Configuration<\/a>).\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAn example, booting Arch Linux:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">set root=(hd0,5)\r\nlinux \/boot\/vmlinuz-linux root=\/dev\/sda5\r\ninitrd \/boot\/initramfs-linux.img\r\nboot\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tWith a separate boot partition, again change the lines accordingly:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">set root=(hd0,5)\r\nlinux \/vmlinuz-linux root=\/dev\/sda6\r\ninitrd \/initramfs-linux.img\r\nboot\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAfter successfully booting the Arch Linux installation, users can correct&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;as needed and then reinstall GRUB2.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tto reinstall GRUB2 and fix the problem completely, changing&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/dev\/sda<\/code>&nbsp;if needed. See&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Bootloader_installation\" style=\"color:#336699;text-decoration:none;\">#Bootloader installation<\/a>&nbsp;for details.\n<\/p>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t67\"><\/a><span class=\"mw-headline\" id=\"Combining_the_use_of_UUIDs_and_basic_scripting\">Combining the use of UUIDs and basic scripting<\/span><br \/>\n<\/h2>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf 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:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"> menuentry \"Arch Linux 64\" {\r\n     # Set the UUIDs for your boot and root partition respectively\r\n     set the_boot_uuid=ece0448f-bb08-486d-9864-ac3271bd8d07\r\n     set the_root_uuid=c55da16f-e2af-4603-9e0b-03f5f565ec4a\r\n   \r\n     # (Note: This may be the same as your boot partition)\r\n   \r\n     # Get the boot\/root devices and set them in the root and grub_boot variables\r\n     search --fs-uuid --set=root $the_root_uuid\r\n     search --fs-uuid --set=grub_boot $the_boot_uuid\r\n   \r\n     # Check to see if boot and root are equal.\r\n     # If they are, then append \/boot to $grub_boot (Since $grub_boot is actually the root partition)\r\n     if [ $the_boot_uuid == $the_root_uuid]&nbsp;; then\r\n         set grub_boot=$grub_boot\/boot\r\n     fi\r\n   \r\n     # $grub_boot now points to the correct location, so the following will properly find the kernel and initrd\r\n     linux ($grub_boot)\/vmlinuz-linux root=\/dev\/disk\/by-uuid\/$uuid_os_root ro\r\n     initrd ($grub_boot)\/initramfs-linux.img\r\n }\r\n<\/pre>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t68\"><\/a><span class=\"mw-headline\" id=\"Troubleshooting\">Troubleshooting<\/span><br \/>\n<\/h2>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAny troubleshooting should be added here.\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t69\"><\/a><span class=\"mw-headline\" id=\"Intel_BIOS_not_booting_GPT\">Intel BIOS not booting GPT<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tSome Intel BIOS's require at least one bootable MBR partition to be present at boot, causing GPT-partitioned boot setups to be unbootable.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThis can be circumvented by using (for instance) fdisk to mark one of the GPT partitions (preferably the 1007KiB partition you've created for GRUB2 already) bootable in the MBR. This can be achieved, using fdisk, by the following commands: Start fdisk against the disk you're 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.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tNote that 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.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tMore information is available&nbsp;<a class=\"external text\" href=\"http:\/\/www.rodsbooks.com\/gdisk\/bios.html\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">here<\/a>\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t70\"><\/a><span class=\"mw-headline\" id=\"Enable_GRUB2_debug_messages\">Enable GRUB2 debug messages<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAdd:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">set pager=1\r\nset debug=all\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tto&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>.\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t71\"><\/a><span class=\"mw-headline\" id=\"Correct_GRUB2_No_Suitable_Mode_Found_Error\">Correct GRUB2 No Suitable Mode Found Error<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf you get this error when booting any menuentry:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">error: no suitable mode found\r\nBooting however\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThen you need to initialize GRUB2 graphical terminal (<code style=\"padding:0.1em 0.3em;display:inline-block;\">gfxterm<\/code>) with proper video mode (<code style=\"padding:0.1em 0.3em;display:inline-block;\">gfxmode<\/code>) in GRUB2. This video mode is passed by GRUB2 to the linux kernel via 'gfxpayload'. In case of UEFI systems, if the GRUB2 video mode is not initialized, no kernel boot messages will be shown in the terminal (atleast until KMS kicks in).\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tCopy&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/usr\/share\/grub\/unicode.pf2<\/code>&nbsp;to ${GRUB2_PREFIX_DIR} (<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/<\/code>&nbsp;in case of BIOS and UEFI systems). If GRUB2 UEFI was installed with&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--boot-directory=\/boot\/efi\/EFI<\/code>&nbsp;set, then the directory is&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/efi\/EFI\/grub\/<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># cp \/usr\/share\/grub\/unicode.pf2 ${GRUB2_PREFIX_DIR}\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/usr\/share\/grub\/unicode.pf2<\/code>&nbsp;does not exist, install&nbsp;<span style=\"font-family:monospace;\"><a class=\"external text\" href=\"https:\/\/www.archlinux.org\/packages\/?name=bdf-unifont\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">bdf-unifont<\/a><\/span>, create the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">unifont.pf2<\/code>&nbsp;file and then copy it to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">${GRUB2_PREFIX_DIR}<\/code>:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># grub-mkfont -o unicode.pf2 \/usr\/share\/fonts\/misc\/unifont.bdf\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThen, in the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;file, add the following lines to enable GRUB2 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.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tBIOS systems:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">insmod vbe\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tUEFI systems:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">insmod efi_gop\r\ninsmod efi_uga\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAfter that add the following code (common to both BIOS and UEFI):\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">insmod font\r\n<\/pre>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">if loadfont ${prefix}\/fonts\/unicode.pf2\r\nthen\r\n    insmod gfxterm\r\n    set gfxmode=auto\r\n    set gfxpayload=keep\r\n    terminal_output gfxterm\r\nfi\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tAs you can see for gfxterm (graphical terminal) to function properly,&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">unicode.pf2<\/code>&nbsp;font file should exist in&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">${GRUB2_PREFIX_DIR}<\/code>.\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t72\"><\/a><span class=\"mw-headline\" id=\"msdos-style_error_message\">msdos-style error message<\/span><br \/>\n<\/h3>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">grub-setup: warn: This msdos-style partition label has no post-MBR gap; embedding won't be possible!\r\ngrub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists.\r\n            However, blocklists are UNRELIABLE and its use is discouraged.\r\ngrub-setup: error: If you really want blocklists, use --force.\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tThis error may occur when you try installing GRUB2 in a VMware container. Read more about it&nbsp;<a class=\"external text\" href=\"https:\/\/bbs.archlinux.org\/viewtopic.php?pid=581760#p581760\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">here<\/a>. 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&nbsp;<a href=\"https:\/\/wiki.archlinux.org\/index.php\/GRUB2#Master_Boot_Record_.28MBR.29_specific_instructions\" style=\"color:#336699;text-decoration:none;\">#Master Boot Record (MBR) specific instructions<\/a>\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t73\"><\/a><span class=\"mw-headline\" id=\"UEFI_GRUB2_drops_to_shell\">UEFI GRUB2 drops to shell<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf GRUB loads but drops you into the rescue shell with no errors, it may be because of a missing or misplaced&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>. This will happen if GRUB2 UEFI was installed with&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">--boot-directory<\/code>&nbsp;and&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub.cfg<\/code>&nbsp;is missing OR if the partition number of the boot partition changed (which is hard-coded into the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">grubx64.efi<\/code>file).\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t74\"><\/a><span class=\"mw-headline\" id=\"UEFI_GRUB2_not_loaded\">UEFI GRUB2 not loaded<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIn some cases the EFI may fail to load GRUB correctly. Provided everything is set up correctly, the output of:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">efibootmgr -v\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tmight look something like this:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">BootCurrent: 0000\r\nTimeout: 3 seconds\r\nBootOrder: 0000,0001,0002\r\nBoot0000* Grub\tHD(1,800,32000,23532fbb-1bfa-4e46-851a-b494bfe9478c)File(\\efi\\grub\\grub.efi)\r\nBoot0001* Shell\tHD(1,800,32000,23532fbb-1bfa-4e46-851a-b494bfe9478c)File(\\EfiShell.efi)\r\nBoot0002* Festplatte\tBIOS(2,0,00)P0: SAMSUNG HD204UI\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf everything works correctly, the EFI would now automatically load GRUB.\n<\/p>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf the screen only goes black for a second and the next boot option is tried afterwards, according to&nbsp;<a class=\"external text\" href=\"https:\/\/bbs.archlinux.org\/viewtopic.php?pid=981560#p981560\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">this post<\/a>, 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:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\">Boot0000* Grub\tHD(1,800,32000,23532fbb-1bfa-4e46-851a-b494bfe9478c)File(\\grub.efi)\r\n<\/pre>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t75\"><\/a><span class=\"mw-headline\" id=\"Invalid_signature\">Invalid signature<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf trying to boot Windows results in an \"invalid signature\" error, e.g. after reconfiguring partitions or adding additional hard drives, (re)move GRUB's device configuration and let it reconfigure:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># mv \/boot\/grub\/device.map \/boot\/grub\/device.map-old\r\n# grub-mkconfig -o \/boot\/grub\/grub.cfg\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<code style=\"padding:0.1em 0.3em;display:inline-block;\">grub-mkconfig<\/code>&nbsp;should now mention all found boot options, including Windows. If it works, remove&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot\/grub\/device.map-old<\/code>.\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t76\"><\/a><span class=\"mw-headline\" id=\"Boot_freezes\">Boot freezes<\/span><br \/>\n<\/h3>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tIf booting gets stuck without any error message after grub2 loading the kernel and the initial ramdisk, try removing the&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">add_efi_memmap<\/code>&nbsp;kernel parameter.\n<\/p>\n<h3 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t77\"><\/a><span class=\"mw-headline\" id=\"Restore_GRUB_Legacy\">Restore GRUB Legacy<\/span><br \/>\n<\/h3>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tMove GRUB2 files out of the way:\n\t<\/li>\n<\/ul>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># mv \/boot\/grub \/boot\/grub.nonfunctional\r\n<\/pre>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tCopy GRUB Legacy back to&nbsp;<code style=\"padding:0.1em 0.3em;display:inline-block;\">\/boot<\/code>:\n\t<\/li>\n<\/ul>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># cp -af \/boot\/grub-legacy \/boot\/grub\r\n<\/pre>\n<ul style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tReplace MBR and next 62 sectors of sda with backed up copy\n\t<\/li>\n<\/ul>\n<div style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;margin:0.5em 0px;padding:5px;border:thin solid #DDBBBB;overflow:hidden;background-color:#FFDDDD;\">\n\t<strong>Warning:&nbsp;<\/strong>This command also restores the partition table, so be careful of overwriting a modified partition table with the old one. It&nbsp;<strong>will<\/strong>&nbsp;mess up your system.\n<\/div>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># dd if=\/path\/to\/backup\/first-sectors of=\/dev\/sdX bs=512 count=1\r\n<\/pre>\n<p style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\tA safer way is to restore only the MBR boot code use:\n<\/p>\n<pre style=\"white-space:pre-wrap;word-wrap:break-word;color:#333333;font-size:14px;line-height:26px;background-color:#FFFFFF;\"># dd if=\/path\/to\/backup\/mbr-boot-code of=\/dev\/sdX bs=446 count=1\r\n<\/pre>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t78\"><\/a><span class=\"mw-headline\" id=\"References\">References<\/span><br \/>\n<\/h2>\n<ol style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\tOfficial GRUB2 Manual -&nbsp;<a class=\"external free\" href=\"https:\/\/www.gnu.org\/software\/grub\/manual\/grub.html\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">https:\/\/www.gnu.org\/software\/grub\/manual\/grub.html<\/a>\n\t<\/li>\n<li>\n\t\tUbuntu wiki page for GRUB2 -&nbsp;<a class=\"external free\" href=\"https:\/\/help.ubuntu.com\/community\/Grub2\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">https:\/\/help.ubuntu.com\/community\/Grub2<\/a>\n\t<\/li>\n<li>\n\t\tGRUB2 wiki page describing steps to compile for UEFI systems -<a class=\"external free\" href=\"https:\/\/help.ubuntu.com\/community\/UEFIBooting\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">https:\/\/help.ubuntu.com\/community\/UEFIBooting<\/a>\n\t<\/li>\n<li>\n\t\tWikipedia's page on&nbsp;<a title=\"wikipedia:BIOS Boot partition\" class=\"extiw\" href=\"http:\/\/en.wikipedia.org\/wiki\/BIOS_Boot_partition\" style=\"color:#336699;text-decoration:none;\">BIOS Boot partition<\/a>\n\t<\/li>\n<\/ol>\n<h2 style=\"margin:0px;padding:0px;color:#333333;font-family:Arial;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n\t<a name=\"t79\"><\/a><span class=\"mw-headline\" id=\"External_Links\">External Links<\/span><br \/>\n<\/h2>\n<ol style=\"color:#333333;font-family:Arial;font-size:14px;line-height:26px;white-space:normal;background-color:#FFFFFF;\">\n<li>\n\t\t<a class=\"external text\" href=\"https:\/\/github.com\/the-ridikulus-rat\/My_Shell_Scripts\/blob\/master\/grub\/grub_bios.sh\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">A Linux Bash Shell script to compile and install GRUB(2) for BIOS from BZR Source<\/a>\n\t<\/li>\n<li>\n\t\t<a class=\"external text\" href=\"https:\/\/github.com\/the-ridikulus-rat\/My_Shell_Scripts\/blob\/master\/grub\/grub_uefi.sh\" rel=\"nofollow\" style=\"color:#336699;text-decoration:none;\">A Linux Bash Shell script to compile and install GRUB(2) for UEFI from BZR Source<\/a>\n\t<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>GRUB2&nbsp;is the next generation of the GRand Unified  [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[147],"class_list":["post-167","post","type-post","status-publish","format-standard","hentry","category-Technical_literature","tag-grub2"],"views":1814,"_links":{"self":[{"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/posts\/167","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/comments?post=167"}],"version-history":[{"count":0,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/posts\/167\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/media?parent=167"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/categories?post=167"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/tags?post=167"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}