/usr/lib/grub/
are updated, and grub-legacy files installed to /boot/grub
and the MBR
are not removed. You can boot back into grub-legacy by simply renaming /boot/grub/menu.lst.pacsave
to /boot/grub/menu.lst
. /dev/sda1
would be referred to as (hd0,msdos1)
(for MBR) or (hd0,gpt1)
(for GPT)./boot
). If you are booting from a separate /boot
partition, and this partition is smaller than 32 MB, you will run into disk space issues, and pacman will refuse to install new kernels./dev/sdX
with your actual disk path):grub-mkconfig
fails, convert your /boot/grub/menu.lst
file to /boot/grub/grub.cfg
using:/boot/grub/grub.cfg
config file and simply rebooted into GRUB Command Shell, type:/boot/grub/grub.cfg
config file./boot
:/boot/grub/menu.lst
. Edit this file to suit your needs.timeout #
-- time to wait (in seconds) before the default
operating system is automatically loaded.default #
-- the default boot entry that is chosen when the timeout
has expired./boot
is on a separate partition):/boot
, which may be on a dedicated partition./boot
, use the GRUB shell find
command to locate the GRUB files. Enter the GRUB shell as root by:/boot
partition, wherein /boot
is merely a directory under /
:/boot
partition:stage1
file. For example:root
line in your configuration file. Type quit
to exit the shell./boot/grub/menu.lst
(assuming that your Windows partition is on the first partition of the first drive):makeactive
.boot.ini
file to reflect the change (see this article for details on how to do that).map
command must be used. This will make your Windows install think it is actually on the first drive. Assuming that your Windows partition is on the first partition of the second drive:makeactive
./boot/grub/menu.lst
to match boot options, or see chainloader and configfile (recommended).chainloader
or configfile
command should be used to boot another Linux distribution that provides an 'automagic' GRUB configuration mechanism (e.g. Debian, Ubuntu, openSUSE). This allows the distribution to manage its own menu.lst
and boot options.chainloader
command will load another bootloader (rather than a kernel image); useful if another bootloader is installed in a partition's boot sector (GRUB, for example). This allows one to install a 'main' instance of GRUB to the MBR and distribution-specific instances of GRUB to each partition boot record (PBR).configfile
command will instruct the currently running GRUB instance to load the specified configuration file. This can be used to load another distribution's menu.lst
without a separate GRUB installation. The caveat of this approach is that other menu.lst
may not be compatible with the installed version of GRUB; some distributions heavily patch their versions of GRUB.(hd0,2)
.menu.lst
:(hd0,2)
is GRUB:chainloader
command can also be used to load the MBR of a second drive:/boot/grub/menu.lst
:/dev/sda3
.*stage*
files are expected to be in /boot/grub
, which may not be the case if the bootloader was not installed during system installation or if the partition/filesystem was damaged, accidentally deleted, etc. /boot/grub/menu.lst
) before proceeding. Refer to Finding GRUB's root to ensure your devices are defined correctly.chroot
ed environment (i.e. from installed environment via a separate medium) for cases like RAID configurations or if you forgot/broke your GRUB installation. You will need to Change root from a LiveCD or another Linux installation to do so.root
command with the output from the find
command (see Finding GRUB's root) to instruct GRUB which partition contains stage1 (and therefore, /boot
):Tab
twice you will see the available storage devices, this can also be done for partitions. Tab-completion also works from the GRUB boot menu. If there is an error in your configuration file you can edit in the boot menu and use tab-completion to help find devices and partitions. See #Edit GRUB entries in the boot menu.setup
, enter quit
to exit the shell. If you chrooted, exit your chroot and unmount partitions. Now reboot to test.grub-install
command followed by the location to install the bootloader. For example to install the GRUB bootloader to the MBR of the first drive:menu.lst
, but you might want to use your LCD wide-screen at its full native resolution. Here is what you can do to achieve this:vga=867
) does not work. This is because the graphic card manufacturers are free to choose any number they wish, as this is not part of the VBE 3 standard. This is why these codes change from one card to the other (possibly even for the same manufacturer).ask
in the kernel line with the correct one you have picked.[369] 1680x1050x32
would be:hwinfo --framebuffer
as root.vga=
kernel option in menu.lst
. Or convert it to decimal to avoid the use of 0x prefix.menu.lst
:blkid
or ls -l /dev/disk/by-uuid
. It is defined in menu.lst
with either:e
key). Append the following parameters to the kernel options:/boot/grub/menu.lst
(the password must be at the beginning of the configuration file for GRUB to be able to recognize it):lock
command:menu.lst
setup like this:default 0
to default saved
-- this will record the current default in a default
file in the GRUB directory whenever the savedefault command is used. Now add the line savedefault 0
to the bottom of the Windows entry. Whenever Windows is booted, it will reset the default to Arch, thus making changing the default to Windows temporary. grub-set-default
. So, to reboot into Windows, enter the following commands:/sbin/grub-set-default
amongst the commands the user is allowed to issue without supplying a password).make all
) will make a LILO call, and LILO will then be installed over GRUB. LILO may have been included in your base system, depending on your installer media version and whether you selected/deselected it during the package selection stage.menu.lst
file to the disk:hiddenmenu
option can be used in order to hide the menu by default. That way no menu is displayed and the default option is going to be automatically selected after the timeout passes.Still, you are able to press Esc
and the menu shows up. To use it, just add to your /boot/grub/menu.lst
:/dev/sda6
and resize /dev/sda7
, then finally re-create what used to be /dev/sda6
only now it appears at the bottom of the list, /dev/sda9
for example. Although the physical order of the partitions/logical drives has not changed, the order in which they are recognized has changed.fdisk -l
. Now you just need to fix GRUB. See the Bootloader installation section./boot
then re-write GRUB to the MBR on the disk./dev/sda
. So check here, whether the 'Id' values of your partitions are correct. The 'System' column will show you the description of the 'Id' values.t
, select you partition number and type in the new system id (Linux = 83). You can also list all available system ids by typing L
instead of a system id.fixboot
to repair the partition boot sector. After this, you will have to install GRUB again---this time, to the MBR, not to the Windows partition---to boot Linux.e
. Use tab-completion if you need to to discover devices then Esc
to exit. Then you can try to boot by pressing b
. /boot/grub/device.map
during installation or boot, run:/boot/grub/menu.lst
.Ctrl+Alt+F2
or any other F-key for a free virtual console.This assumes that your root file system is mounted in the folder /mnt
and the boot file system is either mounted or stored in the folder /mnt/boot
./mnt/boot
folder), by issuing the command:/mnt/boot/grub
folder already contains all the needed files, jump to step 3. Otherwise, do the following commands (replacing /mnt
, your_kernel
and your_initrd
with the real paths and file names). You should also have the menu.lst
file written to this folder:/dev/vda
, and (hd0,0)
with the correct device and partition corresponding to your setup.