GRUB2
| Özet |
|---|
| Yeni nesil GRand Unified Bootloader (GRUB2) ile ilgili çeşitli konuları içerir.
|
| Genel Bakış |
| Arch Linux' u başlatabilmek için GRUB, GRUB2, LILO veya Syslinux gibi bir Linux uyumlu önyükleyicinin sabit diskin MBR kaydına veya GUID Bölümlendirme Tablosuna kurulu olması gerekir. Bir önyükleyici, önyükleme süreci başlamadan önce çekirdeği ve birincil ram diski yüklemekten sorumludur.
|
| Kaynaklar |
| GNU GRUB -- GNU Project |
GRUB2, GRand Unified Bootloader (GRUB) önyükleyicisinin yeni nesil sürümüdür. GRUB2, GRUB' un geleceği hakkında yapılan bir araştırma projesi olan PUPA temel alınarak oluşturulmuştur. GRUB2, temiz bir kod oluşturmak, taşınabilirliği ve modülerliği sağlamak için sıfırdan yazılmıştır. [1].
Hazırlık
Her ne kadar, GRUB (örneğin 0.9x sürümü) Arch Linux' un öntanımlı önyükleyicisi ise de proje geliştiricileri tarafından eski olarak nitelendirilmektedir. GRUB bir çok dağıtımda yerini GRUB2 ve Syslinux önyükleyicilerine bırakmıştır. Proje geliştiricileri GRUB yerine GRUB2 >=1.99 sürümünün kullanılmasını önermektedirler.
GRUB kullanıcıları için notlar
- GRUB ve GRUB2 komutları arasında belirgin farklılıklar vardır. GRUB2 ile yolunuza devam etmeden önce henüz İngilizce olan GRUB2 komutları yazısını inceleyin (mesela "find" komutu "search" ile değişmiştir).
- GRUB2 artıkmodülerr yapıda olup "stage 1.5" gerektirmemektedir. Bunun neticesinde önyükleyicinin kendisi sınırlı yetenekler sahiptir. Ancak, işlevsellik (mesela LVM veya RAID desteği) sabit diskteki modüllerin yüklenmesiyle genişletilebilmektedir.
- GRUB ve GRUB2 arasında aygıtların isimlendirilmesi farklıdır. Öncekine nazaran GRUB2' de disk bölümleri 0 yerine 1 ile isimlendirilmeye başlanmaktadır. Ancak sabit diskler hala 0' dan isimlendirilmeye başlanmak ve bölümlendirme tablosu türünde önek taşımaktadırlar. Mesela,
/dev/sda1disk bölümü(hd0,msdos1)(MBR için) veya(hd0,gpt1)(GPT için) olarak adlandırılır.
GRUB2 için öncelikli gereksinimler
BIOS sistemleri
GPT' ye özgü yönergeler
BIOS-GPT yapılandırmasındaki GRUB2; GPT bölümlendirmesi kullanan sistemlerde post-MBR açıklığının yokluğunda kendi core.img dosyasını gömebilmek için bir BIOS Önyükleme Bölümüne gereksinim duyar (ki GPT Birincil Başlığı ve Birincil Bölümlendirme Tablosu tarafından devranılır.). Bu disk bölümü BIOS-GPT kurulumlarında sadece GRUB2 tarafından kullanılır. MBR disk bölümlendirilmesine böyle bir disk bölümü yoktur (En azından GRUB2 için). Bu disk bölümü, sistem UEFI temelliyse gereksizdir. Çünkü bu durumda gömülmesi gereken önyükleme sektörleri yoktur. Syslinux da bu disk bölümünü gerektirmez.
Bir BIOS-GPT yapılandırması için cgdisk veya GNU Parted kullanarak dosya sistemi içermeyen bir 2MiB disk bölümü oluşturun. Disk bölümünün bölümlendirme tablosundaki yeri önemli değildir ancak sabit diskin ilk 2TB boyutundaki kesimi içinde olmalıdır. Önerilen, /boot disk bölümünden önce diskin başlarında bir yerde oluşturulmasıdır. Disk bölümü türünü cgdisk aracında "EF02" veya GNU Parted aracında set <BOOT_PART_NUM> bios_grub on olarak ayarlayın.
MBR (msdos) disk bölümlendirmesine özgü yönergeler
Bir çok MBR (veya msdos disk etiketli) bölümlendirmeye sahip sistemde MBR sonrası bölüm (512 bitlik MBR bölümü sonrası ve ilk disk bölümü öncesi olan kısım), disk bölümlendirme tablosunda DOS uyumlu silindir hizalama sağlanmışsa 32 KiB boyutundadır. Ancak, GRUB2' nin core.img dosyasını gömebilmek için 1-2 MiB boyutunda bir MBR sonrası bölüm ayarlanması önerilir ([2]). Hem bu alanı elde etmek hem de diğer 512 bit olmayan sektör sorunlarının (ki bu sorunlar core.img gömülmesi ile ilgili değildir) önüne geçmek için 1 MiB disk bölümü hizalamayı destekleyen bir disk bölümlendirme aracı kullanılması önerilir.
BIOS sistemlerde herhangi bir MS Windows ile ikili önyükleme yapmıyorsanız GPT disk bölümlendirmeye geçmeniz önerilir. - [Guid Bölümledirme Tablosu#MBR biçiminden GPT biçimine dönüştürme]]
UEFI sistemler
UEFI SİSTEM DİSK BÖLÜMÜNÜ Oluşturun ve Bağlayın
Bir UEFI Sistem Disk Bölümünü oluşturmak için bu ArchWiki yazısındaki yönergeleri izleyin. Daha sonra UEFI Sistem Disk Bölümünü /boot/efi dizinine bağlayın. UEFISYS disk bölümünü bir başka bağlama noktasına bağladıysanız aşağıdaki yönergelerde bulunan /boot/efi ibaresini o bağlama noktası ile değiştirin:
# mkdir -p /boot/efi # mount -t vfat <UEFISYS_PART_DEVICE> /boot/efi
Mevcut değilse bir <UEFI_SYSTEM_PARTITION>/EFI dizini oluşturun:
# mkdir -p /boot/efi/EFI
Kurulum
Arch Linux kurulumu sırasında
- Önyükleyici Kurulumu aşamasını atlayın ve kurulum aracından çıkın.
- Ağı yapılandırın:
# aif -p partial-configure-network
Bu komut bir sorgu gönderecektir, kullanılacak ağ arayüzünü (mesela eth0) seçin ve kolay yapılandırma için DHCP kullanın.
- Kurduğunuz sistemin
/etc/resolv.confdosyasını kurulum sırasında (mesela DHCP' nin daha sonra onu üretmesini tercih etmişseniz) yapılandırmadığınız takdirde; AIF tarafından ağ yapılandırıldığında üretilen dosyayı kopyalamanız gerekecektir:
# cp /etc/resolv.conf /mnt/etc/resolv.conf
- Aşağıdaki pacman güncellemesi adımı sırasında ağ sorunları yaşarsanız net-tools paketini kurmanız gerekebilir.
- device-mapper çekirdek (
dm_mod) modülünün yüklenmiş olduğunu denetleyin. Yüklenmemişse elle yükleyin (grub2-bios paketine gereksinim duyabilirsiniz):
# lsmod | grep dm_mod # modprobe dm-mod
- Kurulum aracının çalışan ortam kabuğunda kurulu sisteme chroot ile girin:
# mount -o bind /dev /mnt/dev # mount -t proc /proc /mnt/proc/ # mount -t sysfs /sys /mnt/sys/ # chroot /mnt bash
- Pacman veritabanını güncelleyin:
# pacman-db-upgrade
- Paket listesini (paket listesi güncel görünse bile ek bir
-yanahtarı kullanın):
# pacman -Syy
- #Kurulu bir Arch Linux sisteminde anlatıldığı gibi GRUB2 paketini kurun. (
dm-modmodülü yukarıdaki aşamalardan sonra zaten yüklü olacaktır yeniden yüklemeye gerek yoktur).
Kurulu bir Arch Linux sisteminde
BIOS sistemler
Önemli verileri yedekleyin
Bir GRUB2 kurulumunun sorunsuz olacağı varsayılsa da eski GRUB dosyalarını her ihtimale karşı grub2-bios kurulumundan önce yedekleyin:
mv /boot/grub /boot/grub-legacy
Önyükleme kodunu ve disk bölümlendirme tablosunu içeren MBR kaydını yedekleyin (/dev/sdX ibaresini sizin disk konumunuz ile değiştirin):
# dd if=/dev/sdX of=/path/to/backup/mbr_backup bs=512 count=1
MBR' nin sadece 446 baytlık kısmı önyükleme kodunu içermektedir. Diğer 64 baytlık kısım ise disk bölümlendirme tablosunu barındırır. Geri yükleme yaparken disk bölümlendirme tablosunun üzerine yazmak istemiyorsanız, sadece MBR önyükleme kodunu yedekleyin:
# dd if=/dev/sdX of=/path/to/backup/mbr-boot-code bs=440 count=1
GRUB2' yi düzgün olarak yüklemeyi başaramıyorsanız eski GRUB önyükleyicisine dönüş yapabilirsiniz.
# dd if=/dev/sdX of=/path/to/backup/bootcode_backup bs=446 count=1
GRUB2' yi düzgün olarak yüklemeyi başaramıyorsanız eski GRUB önyükleyicisine dönüş yapabilirsiniz.
grub2-bios paketini kurun
GRUB2' yi kurmak için grub paketinin yerini alacak olan grub2-bios paketini kurun:
# pacman -S grub2-bios
Ayrıca device-mapper çekirdek modülünü de yükleyin; çünkü her zaman grub-probe güvenilir biçimde sabit diskleri ve disk bölümlerini algılamayabilir:
# modprobe dm-mod
grub2-bios önyükleme dosyalarını kurun
There are 3 ways to install GRUB2 boot files in BIOS booting:
- #Install_to_440-byte_MBR_boot_code_region (recommended) ,
- #Install_to_Partition_or_Partitionless_Disk (not recommended),
- #Generate_core.img_alone (safest method, but requires another BIOS bootloader like grub-legacy or syslinux to be installed to chainload
/boot/grub/i386-pc/core.img).
Install to 440-byte MBR boot code region
To setup grub2-bios in the 440-byte Master Boot Record boot code region, populate the /boot/grub directory, generate the /boot/grub/i386-pc/core.img file, and embed it in the 32 KiB (minimum size - varies depending on partition alignment) post-MBR gap (MBR disks) or in BIOS Boot Partition (GPT disks), run:
# grub-install --directory=/usr/lib/grub/i386-pc --target=i386-pc --boot-directory=/boot --recheck --debug /dev/sda # mkdir -p /boot/grub/locale # cp /usr/share/locale/tr/LC_MESSAGES/grub.mo /boot/grub/locale/tr.mo
where /dev/sda is the destination of the installation (in this case the MBR of the first SATA disk). If you use LVM for your /boot, you can install GRUB2 on multiple physical disks.
The --no-floppy tells grub2-bios utilities not to search for any floppy devices which reduces the overall execution time of grub-install on many systems (it will also prevent the issue below from occurring). Otherwise you get an error that looks like this:
grub-probe: error: Cannot get the real path of '/dev/fd0' Auto-detection of a filesystem module failed. Please specify the module with the option '--modules' explicitly.
Install to Partition or Partitionless Disk
To set up grub2-bios to a partition boot sector, to a partitionless disk (also called superfloppy) or to a floppy disk, run (using for example /dev/sdaX as the /boot partition):
# chattr -i /boot/grub/i386-pc/core.img # grub-install --directory=/usr/lib/grub/i386-pc --target=i386-pc --boot-directory=/boot --recheck --force --debug /dev/sdaX # mkdir -p /boot/grub/locale # cp /usr/share/locale/tr/LC_MESSAGES/grub.mo /boot/grub/locale/tr.mo # chattr +i /boot/grub/i386-pc/core.img
You need to use the --force option to allow usage of blocklists and should not use --grub-setup=/bin/true (which is similar to simply generating core.img).
grub-install will give out warnings like which should give you the idea of what might go wrong with this approach:
/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea.
/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists.
However, blocklists are UNRELIABLE and their use is discouraged.
Without --force you may get the below error and grub-setup will not setup its boot code in the partition boot sector:
/sbin/grub-setup: error: will not proceed with blocklists
With --force you should get:
Installation finished. No error reported.
The reason why grub-setup does not by default allow this is because in case of partition or a partitionless disk is that grub2-bios relies on embedded blocklists in the partition bootsector to locate the /boot/grub/i386-pc/core.img file and the prefix dir /boot/grub. The sector locations of core.img may change whenever the filesystem in the partition is being altered (files copied, deleted etc.). For more info see https://bugzilla.redhat.com/show_bug.cgi?id=728742 and https://bugzilla.redhat.com/show_bug.cgi?id=730915.
The workaround for this is to set the immutable flag on /boot/grub/i386-pc/core.img (using chattr command as mentioned above) so that the sector locations of the core.img file in the disk is not altered. The immutable flag on /boot/grub/i386-pc/core.img needs to be set only if grub2-bios is installed to a partition boot sector or a partitionless disk, not in case of installtion to MBR or simple generation of core.img without embedding any bootsector (mentioned above).
Generate core.img alone
To populate the /boot/grub directory and generate a /boot/grub/i386-pc/core.img file without embedding any grub2-bios bootsector code in the MBR, post-MBR region, or the partition bootsector, add --grub-setup=/bin/true to grub-install:
# grub-install --directory=/usr/lib/grub/i386-pc --target=i386-pc --grub-setup=/bin/true --boot-directory=/boot --recheck --debug /dev/sda
You can then chainload GRUB2's core.img from GRUB Legacy or syslinux as a Linux kernel or a multiboot kernel.
Generate GRUB2 BIOS Config file
Finally, generate a configuration for GRUB2 (this is explained in greater detail in the Configuration section):
# grub-mkconfig -o /boot/grub/grub.cfg
If grub2 complains about "no suitable mode found" while booting, go to #Correct_GRUB2_No_Suitable_Mode_Found_Error.
If grub-mkconfig fails, convert your /boot/grub/menu.lst file to /boot/grub/grub.cfg using:
# grub-menulst2cfg /boot/grub/menu.lst /boot/grub/grub.cfg
For example:
/boot/grub/menu.lst
default=0 timeout=5 title Arch Linux Stock Kernel root (hd0,0) kernel /vmlinuz-linux root=/dev/sda2 ro initrd /initramfs-linux.img title Arch Linux Stock Kernel Fallback root (hd0,0) kernel /vmlinuz-linux root=/dev/sda2 ro initrd /initramfs-linux-fallback.img
/boot/grub/grub.cfg
set default='0'; if [ x"$default" = xsaved ]; then load_env; set default="$saved_entry"; fi
set timeout=5
menuentry 'Arch Linux Stock Kernel' {
set root='(hd0,1)'; set legacy_hdbias='0'
legacy_kernel '/vmlinuz-linux' '/vmlinuz-linux' 'root=/dev/sda2' 'ro'
legacy_initrd '/initramfs-linux.img' '/initramfs-linux.img'
}
menuentry 'Arch Linux Stock Kernel Fallback' {
set root='(hd0,1)'; set legacy_hdbias='0'
legacy_kernel '/vmlinuz-linux' '/vmlinuz-linux' 'root=/dev/sda2' 'ro'
legacy_initrd '/initramfs-linux-fallback.img' '/initramfs-linux-fallback.img'
}
If you forgot to create a GRUB2 /boot/grub/grub.cfg config file and simply rebooted into GRUB2 Command Shell, type:
sh:grub> insmod legacycfg
sh:grub> legacy_configfile ${prefix}/menu.lst
Boot into Arch and re-create the proper GRUB2 /boot/grub/grub.cfg config file.
Multiboot in BIOS
Boot Microsoft Windows installed in BIOS-MBR mode
Find the UUID of the NTFS filesystem of the Windows's SYSTEM PARTITION where the bootmgr and its files reside. For example, if Windows bootmgr exists at /media/Windows/bootmgr:
# grub-probe --target=fs_uuid /media/Windows/bootmgr 69B235F6749E84CE
Then, add the below code to /etc/grub.d/40_custom and regenerate grub.cfg with grub-mkconfig as explained above to boot Windows (Vista, 7 or 8) installed in BIOS-MBR mode:
menuentry "Microsoft Windows 7 BIOS-MBR" {
insmod part_msdos
insmod ntfs
insmod search_fs_uuid
insmod ntldr
search --fs-uuid --no-floppy --set=root 69B235F6749E84CE
ntldr /bootmgr
}
For Windows XP:
menuentry "Microsoft Windows XP" {
insmod part_msdos
insmod ntfs
insmod search_fs_uuid
insmod ntldr
search --fs-uuid --no-floppy --set=root 69B235F6749E84CE
ntldr /ntldr
}
UEFI systems
Install grub2-uefi package
GRUB2 UEFI bootloader is available in Arch Linux only from version 1.99~rc1. To install, first Detect which UEFI firmware arch you have (either x86_64 or i386).
Depending on that, install the appropriate package
For 64-bit aka x86_64 UEFI firmware:
# pacman -S grub2-efi-x86_64
For 32-bit aka i386 UEFI firmware:
# pacman -S grub2-efi-i386
Also load the device-mapper kernel module without which grub-probe does not reliably detect disks and partitions:
# modprobe dm-mod
Install grub2-uefi boot files
Install to UEFI SYSTEM PARTITION
The UEFI system partition will need to be mounted at /boot/efi/ for the GRUB2 install script to detect it:
# mkdir -p /boot/efi # mount -t vfat /dev/sdXY /boot/efi
Install GRUB UEFI application to /boot/efi/EFI/arch_grub and its modules to /boot/grub/x86_64-efi (recommended) using:
# grub-install --directory=/usr/lib/grub/x86_64-efi --target=x86_64-efi --efi-directory=/boot/efi \ --bootloader-id=arch_grub --boot-directory=/boot --recheck --debug # mkdir -p /boot/grub/locale # cp /usr/share/locale/tr/LC_MESSAGES/grub.mo /boot/efi/EFI/grub/locale/tr.mo
If you want to install grub2 modules and grub.cfg at the directory /boot/efi/EFI/grub and the grubx64.efi application at /boot/efi/EFI/arch_grub use:
# grub-install --directory=/usr/lib/grub/x86_64-efi --target=x86_64-efi --efi-directory=/boot/efi \ --bootloader-id=arch_grub --boot-directory=/boot/efi/EFI --recheck --debug
In this case grub2-efi-x86_64 will be installed into /boot/grub, making the behavior consistent with the BIOS verion of GRUB2, but this is not recommended if you use both grub2-bios and grub2-efi-x86_64 in your system, as this will overwrite grub2-biosmodules in /boot/grub.
The --efi-directory option mentions the mountpoint of UEFI SYSTEM PARTITION , --bootloader-id mentions the name of the directory used to store the grubx64.efi file and --boot-directory mentions the directory wherein the actual modules will be installed (and into which grub.cfg should be created).
The actual paths are:
<efi-directory>/<efi or EFI>/<bootloader-id>/grubx64.efi
<boot-directory>/grub/x86_64-efi/<all modules, grub.efi, core.efi, grub.cfg>
In --efi-directory=/boot/efi --boot-directory=/boot/efi/EFI --bootloader-id=grub:
<efi-directory>/<efi or EFI>/<bootloader-id> == <boot-directory>/grub == /boot/efi/EFI/grub
In --efi-directory=/boot/efi --boot-directory=/boot/efi/EFI --bootloader-id=arch_grub:
<efi-directory>/<efi or EFI>/<bootloader-id> == /boot/efi/EFI/arch_grub <boot-directory>/grub == /boot/efi/EFI/grub
In --efi-directory=/boot/efi --boot-directory=/boot --bootloader-id=arch_grub:
<efi-directory>/<efi or EFI>/<bootloader-id> == /boot/efi/EFI/arch_grub <boot-directory>/grub == /boot/grub
In --efi-directory=/boot/efi --boot-directory=/boot --bootloader-id=grub:
<efi-directory>/<efi or EFI>/<bootloader-id> == /boot/efi/EFI/grub <boot-directory>/grub == /boot/grub
The <efi-directory>/<efi or EFI>/<bootloader-id>/grubx64.efi is an exact copy of <boot-directory>/grub/x86_64-efi/core.efi.
In all the cases the UEFI SYSTEM PARTITION should be mounted for grub-install to install grubx64.efi in it, which will be launched by the firmware (using the efibootmgr created boot entry in non-Mac systems).
If you notice carefully, there is no <device_path> option (Eg: /dev/sda) at the end of the grub-install command unlike the case of setting up GRUB2 for BIOS systems. Any <device_path> provided will be ignored by the install script as UEFI bootloaders do not use MBR or Partition boot sectors at all.
You may now be able to UEFI boot your system by creating a grub.cfg file by following #Generate_GRUB2_UEFI_Config_file and #Create_GRUB2_entry_in_the_Firmware_Boot_Manager.
Create GRUB2 entry in the Firmware Boot Manager
Non-Mac UEFI systems
grub-install will ensure that /boot/efi/EFI/arch_grub/grubx64.efi is launched by default if it detects efibootmgr and if it is able to access UEFI Runtime Services. Follow Unified_Extensible_Firmware_Interface#efibootmgr for more info.
If you have problems running GRUB2 in UEFI mode you can try the following (worked on an ASUS Z68 mainboard):
# cp /boot/efi/EFI/arch_grub/grubx64.efi /boot/efi/shellx64.efi
or
# cp /boot/efi/EFI/arch_grub/grubx64.efi /boot/efi/EFI/shellx64.efi
or
# cp /boot/efi/EFI/arch_grub/grubx64.efi /boot/efi/EFI/tools/shellx64.efi
After this launch the UEFI Shell from the UEFI setup/menu (in ASUS UEFI BIOS, switch to advanced mode, press Exit in the top right corner and choose "Launch EFI shell from filesystem device"). The GRUB2 menu will show up and you can boot into your system. Afterwards you can use efibootmgr to setup a menu entry (see above).
Apple Mac EFI systems
Use bless command from within Mac OS X to set grubx64.efi as the default boot option. You can also boot from the Mac OS X install disc and launch a Terminal there if you only have Linux installed. In the Terminal, create a directory and mount the EFI System Partition:
# cd /Volumes # mkdir efi # mount -t msdos /dev/disk0s1 /Volumes/efi
Then run bless on grub.efi and on the EFI partition to set them as the default boot options.
# bless --folder=/Volumes/efi --file=/Volumes/efi/efi/arch_grub/grubx64.efi --setBoot # bless --mount=/Volumes/efi --file=/Volumes/efi/efi/arch_grub/grubx64.efi --setBoot
More info at https://help.ubuntu.com/community/UEFIBooting#Apple_Mac_EFI_systems_.28both_EFI_architecture.29.
Generate GRUB2 UEFI Config file
Finally, generate a configuration for GRUB2 (this is explained in greater detail in the Configuration section):
# grub-mkconfig -o <boot-directory>/grub/grub.cfg
If you used --boot-directory=/boot:
# grub-mkconfig -o /boot/grub/grub.cfg
If you used --boot-directory=/boot/efi/EFI:
# grub-mkconfig -o /boot/efi/EFI/grub/grub.cfg
This is independent of the value of --bootloader-id option.
If GRUB2 complains about "no suitable mode found" while booting, try #Correct_GRUB2_No_Suitable_Mode_Found_Error.
Create GRUB2 Standalone UEFI Application
It is possible to create a grubx64_standalone.efi 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 grub-mkstandalone command which is included in grub2-common >= 1:1.99-6 package.
The easiest way to do this would be with the install command already mentioned before, but specifying the modules to include. For example:
# grub-mkstandalone --directory="/usr/lib/grub/x86_64-efi/" --format="x86_64-efi" --compression="xz" \ --output="/boot/efi/EFI/arch_grub/grubx64_standalone.efi" <any extra files you want to include>
The grubx64_standalone.efi file expects grub.cfg to be within its $prefix which is (memdisk)/boot/grub. The memdisk is embedded within the efi app. The grub-mkstandlone script allow passing files to be included in the memdisk image to be as the arguments to the script (in <any extra files you want to include>).
If you have the grub.cfg at /home/user/Desktop/grub.cfg, then create a temporary /home/user/Desktop/boot/grub/ directory, copy the /home/user/Desktop/grub.cfg to /home/user/Desktop/boot/grub/grub.cfg, cd into /home/user/Desktop/boot/grub/ and run:
# grub-mkstandalone --directory="/usr/lib/grub/x86_64-efi/" --format="x86_64-efi" --compression="xz" \ --output="/boot/efi/EFI/arch_grub/grubx64_standalone.efi" "boot/grub/grub.cfg"
The reason to cd into /home/user/Desktop/boot/grub/ and to pass the file path as boot/grub/grub.cfg (notice the lack of a leading slash - boot/ vs /boot/ ) is because dir1/dir2/file is included as (memdisk)/dir1/dir2/file by the grub-mkstandalone script.
If you pass /home/user/Desktop/grub.cfg the file will be included as (memdisk)/home/user/Desktop/grub.cfg. If you pass /home/user/Desktop/boot/grub/grub.cfg the file will be included as (memdisk)/home/user/Desktop/boot/grub/grub.cfg. That is the reason for cd'ing into /home/user/Desktop/boot/grub/ and passing boot/grub/grub.cfg, to includ the file as (memdisk)/boot/grub/grub.cfg, which is what grub.efi expects the file to be.
You need to create an UEFI Boot Manager entry for /boot/efi/EFI/arch_grub/grubx64_standalone.efi using efibootmgr. Follow #Create GRUB2 entry in the Firmware Boot Manager.
Multiboot in UEFI
Chainload Microsoft Windows x86_64 UEFI-GPT
Find the UUID of the FAT32 filesystem in the UEFI SYSTEM PARTITION where the Windows UEFI Bootloader files reside. For example, if Windows bootmgfw.efi exists at /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi (ignore the upper-lower case differences since that is immaterial in FAT filesystem):
# grub-probe --target=fs_uuid /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi 1ce5-7f28
# grub-probe --target=hints_string /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
Then, add this code to /boot/grub/grub.cfg OR /boot/efi/EFI/grub/grub.cfg to chainload Windows x86_64 (Vista SP1+, 7 or 8) installed in UEFI-GPT mode:
menuentry "Microsoft Windows x86_64 UEFI-GPT" {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --fs-uuid --no-floppy --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 1ce5-7f28
chainloader /efi/Microsoft/Boot/bootmgfw.efi
}
Configuration
You can also choose to automatically generate or manually edit grub.cfg.
Automatically generating using grub-mkconfig (Recommended)
The GRUB2 menu.lst equivalent configuration files are /etc/default/grub and /etc/grub.d/*. grub-mkconfig uses these files to generate grub.cfg. By default the script outputs to stdout. To generate a grub.cfg file run the command:
# grub-mkconfig -o /boot/grub/grub.cfg
/etc/grub.d/10_linux is set to automatically add menu items for Arch linux that work out of the box, to any generated configuration. Other operating systems may need to be added manually by editing /etc/grub.d/40_custom
Additional arguments
To pass custom additional arguments to the linux image, you can set the GRUB_CMDLINE_LINUX variable in /etc/default/grub. This is analogous to adding commands to the kernel line in legacy GRUB.
For example, use GRUB_CMDLINE_LINUX="resume=/dev/sdaX" where sdaX is your swap partition to enable resume after hibernation.
You can also use GRUB_CMDLINE_LINUX="resume=/dev/disk/by-uuid/${swap_uuid}", where ${swap_uuid} is the uuid of your swap partition.
Manually creating grub.cfg
A basic GRUB config file uses the following options
-
(hdX,Y)is the partitionYon diskX, partition numbers starting at 1, disk numbers starting at 0 -
set default=Nis the default boot entry that is chosen after timeout for user action -
set timeout=Mis the timeMto wait in seconds for a user selection before default is booted -
menuentry "title" {entry options}is a boot entry titledtitle -
set root=(hdX,Y)sets the boot partition, where the kernel and GRUB modules are stored (boot need not be a separate partition, and may simply be a directory under the "root" partition (/)
An example configuration:
/boot/grub/grub.cfg
# Config file for GRUB2 - The GNU GRand Unified Bootloader
# /boot/grub/grub.cfg
# DEVICE NAME CONVERSIONS
#
# Linux Grub
# -------------------------
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,2)
# /dev/sda3 (hd0,3)
#
# Timeout for menu
set timeout=5
# Set default boot entry as Entry 0
set default=0
# (0) Arch Linux
menuentry "Arch Linux" {
set root=(hd0,1)
linux /vmlinuz-linux root=/dev/sda3 ro
initrd /initramfs-linux.img
}
## (1) Windows
#menuentry "Windows" {
#set root=(hd0,3)
#chainloader +1
#}
Dual-booting
Using grub-mkconfig
The best way to add other entries is editing the /etc/grub.d/40_custom. The entries in this file will be automatically added when running grub-mkconfig.
After adding the new lines, run:
# grub-mkconfig -o /boot/grub/grub.cfg
to generate an updated grub.cfg.
With GNU/Linux
Assuming that the other distro is on partition sda2:
menuentry "Other Linux" {
set root=(hd0,2)
linux /boot/vmlinuz (add other options here as required)
initrd /boot/initrd.img (if the other kernel uses/needs one)
}
With FreeBSD
Requires that FreeBSD is installed on a single partition with UFS. Assuming it is installed on sda4:
menuentry "FreeBSD" {
set root=(hd0,4)
chainloader +1
}
With Windows
This assumes that your Windows partition is sda3.
# (2) Windows XP
menuentry "Windows XP" {
set root=(hd0,3)
chainloader (hd0,3)+1
}
If the Windows Bootloader is on an entirely different harddrive than GRUB, it may be necessary to trick Windows into believing that it is in fact the first harddrive. This was possible in the old GRUB with map and is now done with drivemap. Assume GRUB is on hd0 and windows on hd2, you need to add the following after set root:
drivemap -s hd0 hd2
With Windows via EasyBCD and NeoGRUB
Since EasyBCD's NeoGRUB currently does not understand the GRUB2 menu format, chainload to it by replacing the contents of your C:\NST\menu.lst file with lines similar to the following:
default 0 timeout 1
title Chainload into GRUB v2 root (hd0,7) kernel /boot/grub/i386-pc/core.img
Visual Configuration
In 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 #Correct_GRUB2_No_Suitable_Mode_Found_Error. 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.
Setting the framebuffer resolution
GRUB2 can set the framebuffer for both GRUB2 itself and the kernel. The old vga= way is deprecated. The preferred method is editing /etc/default/grub as the following sample:
GRUB_GFXMODE=1024x768x32 GRUB_GFXPAYLOAD_LINUX=keep
To generate the changes, run:
grub-mkconfig -o /boot/grub/grub.cfg
The gfxpayload property will make sure the kernel keeps the resolution.
If this method does not work for you, the deprecated vga= method will still work. Just
add it next to the "GRUB_CMDLINE_LINUX_DEFAULT=" line in /etc/default/grub
for eg: "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=792" will give you a 1024x768 resolution.
You can choose one of these resolutions: 640×480, 800×600, 1024×768, 1280×1024, 1600×1200
915resolution hack
Some times for Intel graphic adapters neither # hwinfo --framebuffer nor vbeinfo will show you the desired resolution. In this case you can use 915resolution hack. This hack will temporarily modify video BIOS and add needed resolution. See 915resolution's home page
In 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 915resolution in GRUB2 command shell:
915resolution -l
The output will be something like:
Intel 800/900 Series VBIOS Hack : version 0.5.3 ... Mode 30 : 640x480, 8 bits/pixel ...
Next, our purpose is to overwrite mode 30. (You can choose what ever mode you want.) In the file /etc/grub.d/00_header just before the set gfxmode=${GRUB_GFXMODE} line insert:
915resolution 30 1440 900
Here we are overwriting the mode 30 with 1440x900 resolution. Lastly we need to set GRUB_GFXMODE as described earlier, regenerate GRUB2 configuration file and reboot to test changes:
# grub-mkconfig -o /boot/grub/grub.cfg # reboot
Background image and bitmap fonts
GRUB2 comes with support for background images and bitmap fonts in pf2 format. The unifont font is included in the grub2-common package under the filename unicode.pf2, or, as only ASCII characters under the name ascii.pf2.
Image formats supported include tga, png and jpeg, providing the correct modules are loaded. The maximum supported resolution depends on your hardware.
Make sure you have set up the proper framebuffer resolution.
Edit /etc/default/grub like this:
GRUB_BACKGROUND="/boot/grub/myimage" #GRUB_THEME="/path/to/gfxtheme"
To generate the changes and add the information into grub.cfg, run:
grub-mkconfig -o /boot/grub/grub.cfg
If adding the splash image was successful, the user will see "Found background image..." in the terminal as the command is executed.
If this phrase is not seen, the image information was probably not incorporated into the grub.cfg file.
If the image is not displayed, check:
- The path and the filename in
/etc/default/grubare correct. - The image is of the proper size and format (tga, png, 8-bit jpg).
- The image was saved in the RGB mode, and is not indexed.
- The console mode is not enabled in
/etc/default/grub. - The command
grub-mkconfigmust be executed to place the background image information into the/boot/grub/grub.cfgfile.
Theme
Here is an example for configuring Starfield theme which was included in GRUB2 package.
Edit /etc/default/grub
GRUB_THEME="/boot/grub/themes/starfield/theme.txt"
Generate the changes:
grub-mkconfig -o /boot/grub/grub.cfg
If configuring the theme was successful, you'll see Found theme: /boot/grub/themes/starfield/theme.txt in the terminal.
Your splash image will usually not displayed when using a theme.
Menu colors
As in GRUB Legacy (0.9x), you can change the menu colors in GRUB2. The available colors for GRUB2 are at http://www.gnu.org/software/grub/manual/html_node/Theme-file-format.html#Theme-file-format. Here is an example:
Edit /etc/default/grub:
GRUB_COLOR_NORMAL="light-blue/black" GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
Generate the changes:
grub-mkconfig -o /boot/grub/grub.cfg
One of the unique features of GRUB2 is hiding/skipping the menu and showing it by holding Shift when needed. You can also adjust whether you want to see the timeout counter.
Edit /etc/default/grub as you wish. Here is an example where the comments from the beginning of the two lines have been removed to enable the feature, the timeout has been set to five seconds and to be shown to the user:
GRUB_HIDDEN_TIMEOUT=5 GRUB_HIDDEN_TIMEOUT_QUIET=false
and run:
grub-mkconfig -o /boot/grub/grub.cfg
Other Options
LVM
If you use LVM for your /boot, add the following before menuentry lines:
insmod lvm
and specify your root in the menuentry as:
set root=(lvm_group_name-lvm_logical_boot_partition_name)
Example:
# (0) Arch Linux
menuentry "Arch Linux" {
insmod lvm
set root=(VolumeGroup-lv_boot)
# you can only set following two lines
linux /vmlinuz-linux root=/dev/mapper/VolumeGroup-root ro
initrd /initramfs-linux.img
}
Raid
GRUB2 provides convenient handling of raid-volumes. You need to add:
insmod raid
which allows you to address the volume natively. E.g. /dev/md0 becomes:
set root=(md0)
whereas a partitioned raid-volume (e.g. /dev/md0p1) becomes:
set root=(md0,1)
Persistent block device naming
You can use UUIDs to detect partitions instead of the "old" /dev/sd* and /dev/hd* scheming. It has the advantage of detecting partitions by their unique UUIDs, which is needed by some people booting with complicated partition setups.
UUIDs are used by default in the recent versions of GRUB2 - there is no downside in it anyway except that you need to re-generate the grub.cfg file every time you resize or reformat your partitions. Remember this when modifying partitions with Live-CD.
The recent versions of GRUB2 use UUIDs by default. You can re-enable the use of UUIDS by simply commenting the UUID line (this is also what it looks like by default):
#GRUB_DISABLE_LINUX_UUID=true
you can also just set the value as false as shown here:
GRUB_DISABLE_LINUX_UUID=false
Either way, do not forget to generate the changes:
grub-mkconfig -o /boot/grub/grub.cfg
Using Labels
It is possible to use labels, human-readable strings attached to filesystems, by using the --label option to search. First of all, label your existing partition:
# tune2fs -L a <LABEL> <PARTITION>
Then, add an entry using labels. An example of this:
menuentry "Arch Linux, session texte" {
search --label --no-floppy --set=root archroot
linux /boot/vmlinuz-linux root=/dev/disk/by-label/archroot ro
initrd /boot/initramfs-linux.img
}
Recall previous entry
GRUB2 can remember the last entry you booted from and use this as the default entry to boot from next time. This is useful if you have multiple kernels (i.e., the current Arch one and the LTS kernel as a fallback option) or operating systems. To do this, edit /etc/default/grub and change the setting of GRUB_DEFAULT:
GRUB_DEFAULT=saved
This ensures that GRUB will default to the saved entry. To enable saving the selected entry, add the following line to /etc/default/grub:
GRUB_SAVEDEFAULT=true
Security
If 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 grub-mkpasswd_pbkdf2. Enter a password and confirm it. The output will look like this:
Your PBKDF2 is grub.pbkdf2.sha512.10000.C8ABD3E93C4DFC83138B0C7A3D719BC650E6234310DA069E6FDB0DD4156313DA3D0D9BFFC2846C21D5A2DDA515114CF6378F8A064C94198D0618E70D23717E82.509BFA8A4217EAD0B33C87432524C0B6B64B34FBAD22D3E6E6874D9B101996C5F98AB1746FE7C7199147ECF4ABD8661C222EEEDB7D14A843261FFF2C07B1269AThen, add the following to
/etc/grub.d/00_header:
cat << EOF set superusers="username" password_pbkdf2 username <password> EOF
where <password> is the string generated by grub-mkpasswd_pbkdf2.
Regenerate your configuration file. Your GRUB2 command line and boot parameters are now protected.
Root Encryption
To let GRUB2 automatically add the kernel parameters for root encryption,
add cryptdevice=/dev/yourdevice:label to GRUB_CMDLINE_LINUX in /etc/defaults/grub.
Example with root mapped to /dev/mapper/root:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda2:root"
Also, disable the usage of UUIDs for the rootfs:
GRUB_DISABLE_LINUX_UUID=true
Regenerate the configuration.
Booting an ISO Directly From GRUB2
Edit /etc/grub.d/40_custom to add an entry for the target ISO. When finished, update the GRUB menu as with the usual grub-mkconfig -o /boot/grub/grub.cfg (as root).
Arch ISO
menuentry "Archlinux-2011.08.19-netinstall-x86_64.iso" {
set isofile="/archives/archlinux-2011.08.19-netinstall-x86_64.iso"
loopback loop (hd0,7)$isofile
linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=ARCH_201108 img_dev=/dev/sda7 img_loop=$isofile earlymodules=loop
initrd (loop)/arch/boot/x86_64/archiso.img
}
Ubuntu ISO
menuentry "ubuntu-11.04-desktop-amd64.iso" {
set isofile="/path/to/ubuntu-11.04-desktop-amd64.iso"
loopback loop (hdX,Y)$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile quiet noeject noprompt splash --
initrd (loop)/casper/initrd.lz
}
Using the command shell
Since 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 /boot/grub, 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.
GRUB2 offers multiple shells/prompts. If there is a problem reading the menu but the bootloader is able to find the disk, you will likely be dropped to the "normal" shell:
sh:grub>
If there is a more serious problem (e.g. GRUB cannot find required files), you may instead be dropped to the "rescue" shell:
grub rescue>
The rescue shell is a restricted subset of the normal shell, offering much less functionality. If dumped to the rescue shell, first try inserting the "normal" module, then starting the "normal" shell:
grub rescue> set prefix=(hdX,Y)/boot/grub grub rescue> insmod (hdX,Y)/boot/grub/i386-pc/normal.mod rescue:grub> normal
Pager support
GRUB2 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:
sh:grub> set pager=1
GUI configuration tools
Following package may be installed from AUR
- grub-customizer (requires gettext gksu gtkmm hicolor-icon-theme openssl)
- Customize the bootloader (GRUB2 or BURG)
- grub2-editor (requires kdelibs)
- A KDE4 control module for configuring the GRUB2 bootloader
- kcm-grub2 (requires kdelibs python2-qt kdebindings-python)
- This Kcm module manages the most common settings of Grub2.
- startupmanager (requires gnome-python imagemagick yelp python2 xorg-xrandr)
- GUI app for changing the settings of GRUB, GRUB2, Usplash and Splashy
parttool or legacy hide/unhide
If you have a win9x paradigm with hidden C disks GRUB Legacy had the hide/unhide feature. In GRUB2 this has been replaced by parttool. For example, to boot the third C disk of three win9x installations on the CLI enter the CLI and:
parttool hd0,1 hidden+ boot- parttool hd0,2 hidden+ boot- parttool hd0,3 hidden- boot+ set root=hd0,3 chainloader +1 boot
Using the rescue console
See #Using the command shell first. If unable to activate the standard shell, one possible solution is to boot using a live CD or some other rescue disk to correct configuration errors and reinstall GRUB. However, such a boot disk is not always available (nor necessary); the rescue console is surprisingly robust.
The available commands in GRUB rescue include insmod, ls, set, and unset. This example uses set and insmod. set modifies variables and insmod inserts new modules to add functionality.
Before starting, the user must know the location of their /boot partition (be it a separate partition, or a subdirectory under their root):
grub rescue> set prefix=(hdX,Y)/boot/grub
where X is the physical drive number and Y is the partition number.
To expand console capabilities, insert the linux module:
grub rescue> insmod (hdX,Y)/boot/grub/linux.mod
This introduces the linux and initrd commands, which should be familiar (see #Configuration).
An example, booting Arch Linux:
set root=(hd0,5) linux /boot/vmlinuz-linux root=/dev/sda5 initrd /boot/initramfs-linux.img boot
With a separate boot partition, again change the lines accordingly:
set root=(hd0,5) linux /vmlinuz-linux root=/dev/sda6 initrd /initramfs-linux.img boot
After successfully booting the Arch Linux installation, users can correct grub.cfg as needed and then reinstall GRUB2.
to reinstall GRUB2 and fix the problem completely, changing /dev/sda if needed. See #Bootloader installation for details.
Combining the use of UUID's and basic scripting
If you like the idea of using UUID's to avoid unreliable BIOS mappings or are struggling with GRUB's syntax, here is an example boot menu item that uses UUID's and a small script to direct GRUB to the proper disk partitions for your system. All you need to do is replace the UUID's in the sample with the correct UUID's for your system. The example applies to a system with a boot and root partition. You will obviously need to modify the GRUB configuration if you have additional partitions:
menuentry "Arch Linux 64" {
# Set the UUIDs for your boot and root partition respectively
set the_boot_uuid=ece0448f-bb08-486d-9864-ac3271bd8d07
set the_root_uuid=c55da16f-e2af-4603-9e0b-03f5f565ec4a
# (Note: This may be the same as your boot partition)
# Get the boot/root devices and set them in the root and grub_boot variables
search --fs-uuid --no-floppy --set=root $the_root_uuid
search --fs-uuid --no-floppy --set=grub_boot $the_boot_uuid
# Check to see if boot and root are equal.
# If they are, then append /boot to $grub_boot (Since $grub_boot is actually the root partition)
if [ $the_boot_uuid == $the_root_uuid] ; then
set grub_boot=$grub_boot/boot
fi
# $grub_boot now points to the correct location, so the following will properly find the kernel and initrd
linux ($grub_boot)/vmlinuz-linux root=/dev/disk/by-uuid/$uuid_os_root ro
initrd ($grub_boot)/initramfs-linux.img
}
Troubleshooting
Any troubleshooting should be added here.
Enable GRUB2 debug messages
Add:
set pager=1 set debug=all
to grub.cfg.
Correct GRUB2 No Suitable Mode Found Error
If you get this error when booting any menuentry:
error: no suitable mode found Booting however
Then you need to initialize GRUB2 graphical terminal (gfxterm) with proper video mode (gfxmode) 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).
Copy /usr/share/grub/unicode.pf2 to ${GRUB2_PREFIX_DIR} (/boot/grub/ in case of BIOS and UEFI systems). If GRUB2 UEFI was installed with --boot-directory=/boot/efi/EFI set, then the directory is /boot/efi/EFI/grub/:
# cp /usr/share/grub/unicode.pf2 ${GRUB2_PREFIX_DIR}
If /usr/share/grub/unicode.pf2 does not exist, install bdf-unifont, create the unifont.pf2 file and then copy it to ${GRUB2_PREFIX_DIR}:
# grub-mkfont -o unicode.pf2 /usr/share/fonts/misc/unifont.bdf
Then, in the grub.cfg file, add the following lines to enable 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.
BIOS systems:
insmod vbe
UEFI systems:
insmod efi_gop insmod efi_uga
After that add the following code (common to both BIOS and UEFI):
insmod font
if loadfont ${prefix}/fonts/unicode.pf2
then
insmod gfxterm
set gfxmode=auto
set gfxpayload=keep
terminal_output gfxterm
fi
As you can see for gfxterm (graphical terminal) to function properly, unicode.pf2 font file should exist in ${GRUB2_PREFIX_DIR}.
msdos-style error message
grub-setup: warn: This msdos-style partition label has no post-MBR gap; embedding won't be possible! grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged. grub-setup: error: If you really want blocklists, use --force.
This error may occur when you try installing GRUB2 in a VMware container. Read more about it here. It happens when the first partition starts just after the MBR (block 63), without the usual space of 1 MiB (2048 blocks) before the first partition. Read #MBR_aka_msdos_partitioning_specific_instructions
UEFI GRUB2 drops to shell
If grub loads but drop you into the rescue shell with no errors, it may be because of a missing or misplaced grub.cfg. This will happen if GRUB2 UEFI was installed with --boot-directory and grub.cfg is missing OR if the partition number of the boot partition changed (which is hard-coded into the grubx64.efi file).
UEFI GRUB2 not loaded
In some cases the EFI may fail to load GRUB correctly. Provided everything is set up correctly, the output of:
efibootmgr -v
might look something like this:
BootCurrent: 0000 Timeout: 3 seconds BootOrder: 0000,0001,0002 Boot0000* Grub HD(1,800,32000,23532fbb-1bfa-4e46-851a-b494bfe9478c)File(\efi\grub\grub.efi) Boot0001* Shell HD(1,800,32000,23532fbb-1bfa-4e46-851a-b494bfe9478c)File(\EfiShell.efi) Boot0002* Festplatte BIOS(2,0,00)P0: SAMSUNG HD204UI
If everything works correctly, the EFI would now automatically load grub.
If the screen only goes black for a second and the next boot option is tried afterwards, according to this post, moving grub to the partition root can help. The boot option has to be deleted and recreated afterwards. The entry for grub should look like this then:
Boot0000* Grub HD(1,800,32000,23532fbb-1bfa-4e46-851a-b494bfe9478c)File(\grub.efi)
Invalid signature
If 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:
# mv /boot/grub/device.map /boot/grub/device.map-old # grub-mkconfig -o /boot/grub/grub.cfg
grub-mkconfig should now mention all found boot options including windows. If it works, remove /boot/grub/device.map-old.
Eski GRUB' a dönüş yapmak
- Move GRUB2 files out of the way:
# mv /boot/grub /boot/grub.nonfunctional
- Copy GRUB Legacy back to
/boot:
# cp -af /boot/grub-legacy /boot/grub
- Replace MBR and next 62 sectors of sda with backed up copy (DANGEROUS AND NOT RECOMMENDED!):
# dd if=/path/to/backup/first-sectors of=/dev/sdX bs=512 count=63
A safer way is to restore only the MBR boot code use:
# dd if=/path/to/backup/mbr-boot-code of=/dev/sdX bs=446 count=1
References
- Official GRUB2 Manual - http://www.gnu.org/software/grub/manual/grub.html
- Ubuntu wiki page for Grub2 - https://help.ubuntu.com/community/Grub2
- GRUB2 wiki page describing steps to compile for UEFI systems - https://help.ubuntu.com/community/UEFIBooting
- Wikipedia's page on BIOS Boot Partition
