Professional Documents
Culture Documents
Grub 2 Basics - Ubuntu Forums
Grub 2 Basics - Ubuntu Forums
t=1195275
Search
Ubuntu Forums > The Ubuntu Forum Community > Other User Name User Name Remember Me?
Community Discussions > Tutorials & Tips
Grub 2 Basics Password Log in
Register Reset Password Forum Help Forum Council Today's Posts Search
Ubuntu Master
Roaster The Grub 2 Guide
(formerly Grub 2 Basics)
New for Natty - Grub 1.99 (RC) - Drag & Drop GRUB Background
Testing Ubuntu 11.04 Natty and Grub 1.99RC? Place a graphic in /boot/grub, run update-grub and you should have a Gru
Read more in this thread:
Grub Background - Simple Drag & Drop
For instance, in Grub 1.98 and earlier, the /etc/default/grub entry to hide "Recovery" menu entries was "GRUB_DISABLE_
In G2 1.99 it is currently "GRUB_DISABLE_RECOVERY=true".
Grub Submenu
1 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
Test versions of Ubuntu 11.04 (Natty Narwhale) are being released with Grub 1.99. One of the new features is the use of
is still being tweaked, but should hide older kernels in the main OS. Clicking on the Submenu entry will reveal the underl
Submenu kernel as the default initially was not possible, but a patch has been submitted by Colin Watson. The user will b
menuentry title or the "saved" function in /etc/default/grub's GRUB_DEFAULT= setting to set a submenu default.
GRUB_DEFAULT is currently not possible. More details as they become available.
1. Introduction
2. First Look Differences
3. Improvements
4. Booting Grub
5. Grub 2 Files & Options
6. Adding Entries to Grub 2
7. Removing Entries from Grub 2
8. Grub 2 Splash Images & Theming
9. Changing Menu Resolution
10. Password Protection
11. Booting to Recovery Mode w/o Menu Option
12. Uninstalling GRUB 2 > GRUB
13. Reinstalling GRUB 2 from the LiveCD
14. Booting to LiveCD ISO
15. Booting from the Rescue Mode
16. Restoring GRUB2 / XP / Vista / Win 7 Bootloaders
17. Grub Rescue Image
18. Grub 2 Fallback Option
19. Selected Problems & Bugs
20. Links
1. Introduction
I've written this guide to present some basic information about Grub 2. It is meant for users who may be familiar w
original Grub (Grub Legacy) menu.lst and wonder how it carries over to Grub 2. The current version of Grub 2 is 1.
Koala was the first Ubuntu release to use Grub 2 on new installations by default (1.97~beta4). In keeping with Ub
philosophy, 1.97~beta4 will probably remain the official version in 9.10/Karmic and will not be updated to 1.98. In
Grub 2 will refer to 1.98 unless otherwise noted. The user can check their current version with the "grub-install -v"
StartUp-Manager supports Grub 2, but not all options are available. The two most-used items, howeve
setting the menu timeout delay. There are plans for a StartUp-Manager 2 that works only for Grub 2 but it is still u
to its creator. To view a guide on installing and running StartUpManager, view the StartUpManager community do
it was based: http://ubuntuforums.org/showthread.php?t=818177
Official documentation at this point is still being created, which is partly the reason for this post. More comprehens
documentation will hopefully be forthcoming from the developers and volunteers. Of the existing documentation, I
links to the better sources at the end of this post.
For troubleshooting and modifying the Grub menu, it is important to know which version you are using (Grub legac
1.97~beta4; Grub 2 in Lucid 1.9 . To confirm the version of Grub used in your system, run this command:
Code:
grub-install -v
drs305@mycomputer:~$ grub-install -v
grub-install (GRUB) 1.98+20100804-5ubuntu3
2 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
A pre-made custom file, ''/etc/grub.d/40_custom'', is available in which users can place their own entries. Thi
by Grub updates.
The primary configuration file for changing menu display settings is ''/etc/default/grub''.
There are multiple files for configuring the the menu - ''/etc/default/grub'' mentioned above, and all the script
Other operating systems, such as Windows, should automatically be recognized and added to the menu.
No changes made in the configuration files will take effect until the `update-grub` command is also run.
* To update the GRUB 2 menu, the command sudo update-grub will be used throughout this guide.
"grub-mkconfig -o /boot/grub/grub.cfg" This runs several scripts and incorporates the results into /boot/grub/grub.c
seen on the screen during boot. Since the GRUB 2 developers do not intend to remove the update-grub
ease of use.
3. Improvements
GRUB 2's major improvements over the original GRUB include:
New configuration file structure
Scripting support including conditional statements and functions
Dynamic module loading
Rescue mode
Themes - under (very slow development). Users wishing to use theming should search the Internet for "burg
Graphical boot menu support and improved splash capability
Boot Ubuntu LiveCD and some other ISO images directly from hard drive
Non-X86 platform support (such as PowerPC)
Universal support for UUIDs (not just Ubuntu)
Improved internationalization, including support for non-ASCII characters
4. Booting Grub
Grub 2 loads before the operating system. It's modular components are loaded on an as-needed basis. Menu display
determined by settings in /etc/default/grub. Review the "Grub 2 Files & Options" section for specific entry and form
The Grub 2 user-configurable settings are contained mainly in /etc/default/grub and the files in /etc/grub.d. When
results are input into the /boot/grub/grub.cfg file.
/boot/grub/grub.cfg
This is the main Grub 2 file. It "replaces" Grub Legacy's /boot/grub/menu.lst This file contains the Gru
unlike Grub Legacy's menu.lst file, grub.cfg is not normally meant to be edited as it is the produc
scripts and is overwritten during certain updates. If a user edits grub.cfg, expect the changes to b
updates or disable the ability of the OS to run these updates.
grub.cfg is automatcially generated when "update-grub" is executed:
Each section (### BEGIN) is clearly delineated and references the file in the /etc/grub.d folder
was generated.
grub.cfg is updated by running the "update-grub" or "update-grub2" command as root.
By default, and whenever the "update-grub" command is executed, this file is made "read-only".
intent that the file should not be edited manually. If you must edit this file, instructions are pro
3 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfa
}
/etc/default/grub
This file contains information formerly contained in the upper section of Grub Legacy's menu.lst
the kernel line. The items in this file can be edited by a user with administrator (root) privileges.
Quote:
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
4 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
GRUB_DEFAULT - Sets the default menu entry. Entries may be numeric or "saved"
GRUB_DEFAULT=0 - Sets the default menu entry by menu position. As Grub Legacy, the first "menu
second is 1, etc.
GRUB_DEFAULT=saved - (Grub 1.98) Enables the "grub-reboot" and "grub-set-default" commands.
This setting allows the use of the following commands to set a default OS. The defau
interactive selection of an OS from the menu.
grub-set-default. Sets the default boot entry until changed.
The format is "sudo grub-set-default X, with X being the menuentry position (starting wit
exact menu string. Examples: sudo grub-set-default 3 or sudo grub-set-default "Ubuntu,
To obtain the existing menuentry choice number (starting from 0) or the menuentry "s
/boot/grub/grub.cfg"
grub-reboot. This command sets the default boot entry for the next boot only. The format of th
"grub-set-default" (see above).
For an example of how to enable the "saved" option with a custom menu, see the "
GRUB_DEFAULT="xxxx" - An exact menu entry, including the quotation symbols, may also be used.
menu will not matter. Example: GRUB_DEFAULT="Ubuntu, Linux 2.6.31-9-generic"
GRUB_SAVEDEFAULT=true * If set to true this setting will automatically set the last selected OS from th
the next boot. No commands need be run to set the default OS. For this entry to work, the GRUB_DEFAULT
GRUB_TIMEOUT=10 - No change from Grub Legacy. This is the number of seconds before the default entr
Setting this value to -1 will cause the menu to display until the user makes a selection.
To display the menu on each boot use a value of 1 or higher.
This command defers to the GRUB_HIDDEN_TIMEOUT command. If the GRUB_HIDDEN_TIMEOUT
pressing the SHIFT key, the GRUB_TIMEOUT counter begins its countdown.
Caution: Holding down the "SHIFT" key will not display the menu if "GRUB_TIMEOUT=" is set to
In addition to editing the file as root, you can also run the following commands the check and change
first checks the existing timeout, the second replaces the value. Replace T with the new value.
Code:
GRUB_HIDDEN_TIMEOUT=0
Wait X seconds for a key to be pressed before displaying the menu. If no key is pressed during that tim
GRUB_HIDDEN_TIMEOUT_QUIET=true
Used with the GRUB_HIDDEN_TIMEOUT setting.
true - No countdown is displayed. The screen will be blank.
false - A counter will display on a blank screen for the duration of the GRUB_HIDDEN_TIMEOUT value
This feature currently appears to be broken; the timeout counter isn't appearing when set to 'false' or n
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
Determines the descriptive name in the menu entry. (Ubuntu, Xubuntu, Debian, etc.)
GRUB_CMDLINE_LINUX
If it exists, this line imports any entries to the end of the 'linux' command line (Grub Legacy's "kernel" line) f
modes. This is similar to the "altoptions" line in menu.lst
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
This line imports any entries to the end of the 'linux' line (Grub Legacy's "kernel" line). The entries are appen
mode only. This is similar to the "defoptions" line in menu.lst. For a black screen with boot processes display
splash". To see the grub splash image plus a condensed text output, use "splash". This line is where other in
are placed.
5 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
Add or uncomment this line to prevent "Recovery" mode kernel options from appearing in the menu. If you w
only one kernel, make a special entry in /etc/grub/40_custom.
GRUB_DISABLE_OS_PROBER="true" * Enables/disables the os-prober check of other partitions for opera
Windows, Linux, OSX and Hurd.
GRUB_INIT_TUNE="480 440 1"
Introduced in Grub 1.98 (Lucid)
When uncommented, plays a single beep just prior to the Grub 2 menu display.
The format unless a file is named is: "tempo [pitch1 duration1] [pitch2 duration2] ..."
The duration is based on the tempo. A tempo of 60 gives the duration a value of 1 second, 120 is .5, 2
The length of the tone can be changed by modifying either the tempo (all tones) or duration (individua
Just a bit of fun:
Warning: The menu will not be displayed until the tone is finished
Close Encounters/5 Tone: GRUB_INIT_TUNE="480 900 2 1000 2 800 2 400 2 600 3"
Fur Elise (note long): GRUB_INIT_TUNE="480 420 1 400 1 420 1 400 1 420 1 315 1 370 1 335 1
213 1 262 1 315 1 335 3 213 1 420 1 400 1 420 1 400 1 420 1 315 1 370 1 335 1 282 3
282 3"
Online documentation is available by typing "info grub --index-search play" in a terminal.
* Entries which are not found in the default file and must be added by the user.
/etc/grub.d/
The files in this folder are read during execution of "update-grub" or "update-grub" commands. The co
/boot/grub/grub.cfg
The order of the entries in the grub menu is based on the order of the file names. File named with a st
those beginning with a letter. The order the files are run determines the menu order in grub.cfg.
Custom entries can be added to the "40_custom" file or in a newly created file.
Any file created must be executable in order to be included in the grub.cfg file during the "
00_header
05_debian_theme: Set background and text colors, themes
10_hurd Locates Hurd kernels
10_linux Locates Linux kernels based on results of the "lsb_release" command.
10_lupin Locates Linux kernels in Wubi installs within Windows, among other things.
20_memtest86+: If the file /boot/memtest86+.bin exists, it is included as a menu item.
30_os-prober: Searches for Linux and OS's on other partitions and includes them in the menu.
40_custom: A template for adding custom menu entries which will be inserted into
"update-grub" command. This and any other custom file must be made executable to allow impo
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
6 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
initrd /sysrcd/initram.igz
}
Note the new partition naming convention. Devices start counting from "0" as done previou
"hd0", sdb is "hd1", etc. However the first partition is now designated as sda1. Counting
sda5 is "5".
If the user wishes to get visual confirmation in the terminal that the 40_custom fil
"update-grub" is executed, the following line can be added to the /etc/grub.d/40_cus
Quote:
Place this line immediately after the first line - "#!/bin/bash" - and before the "e
Tip: If you want to have your custom entries at the top of the menu (say you want custom
"07_xxxx". Since the files in /etc/grub.d/ are read sequentially, those in "07_custom" will be placed bef
recommend not naming a custom menu file lower than 06 so that any theme run from 05_
any custom menu is created. After creating the file, run sudo update-grub and then check the value of
/grub. If it doesn't point to the correct menuentry, change the value of DEFAULT to the correct
Omitting memtest86+: To prevent "memtest86+" entries in your Grub 2 menu, remove the "executa
/20_memtest86+. You can do this via a file browser by selecting "Properties (right click), Permissions
Code:
Omitting Recovery Mode entries: The file /etc/grub.d/10_linux was recently updated to include
options. Edit /etc/default/grub and add or change this line:
Quote:
If you have an older version of /etc/grub.d/10_linux and the above does not work after updating grub, y
mode" entries in your Grub 2 menu, by editing /etc/grub.d/10_linux. If there are no conditional "if" sta
recovery mode, place a comment symbol (#) in front of the following lines (at approximately line 146)
Quote:
If you wish to retain one "Recovery mode" entry for insurance, you can add an entry to /etc/grub.d/40_c
the bottom of your grub menu.
Building a Totally Customized Menu: Ok, admit you are a control freak and you want to see only wh
customized titles, no "memtest86+" and no extra kernels. Here is how you do it:
Run sudo update-grub to get the current available kernels.
Copy the desired "menuentry" listings from /boot/grub/grub.cfg to /etc/grub.d/40_cus
starting with "menuentry" and ends with a line containing "}".
Add any other "menuentry" items you wish to see on the boot menu.
Edit the titles of the "menuentry" line if desired (between the quotation symbols).
"menuentry" line. Each entry should start with a "menuentry" line and end with a "}"
Remove the executable bit from /etc/grub.d/10_linux, /etc/grub.d/20_memtest86+
Removing the executable bit from any file in /etc/grub.d will exclude the file from
Code:
7 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
created by various Grub2 scripts, and it is usually preferable to edit the content of the scripts so the changes
The files that should be edited are contained in the /etc/grub.d folders and the /etc/default/grub
should recognize these changes may be overwritten or should disable the ability of the system to update the
In order to discourage its editing, grub.cfg is read-only. If you must edit this file:
Code:
Note: This file is returned to 'read-only' status anytime the update-grub command is run.
However, if encrypted disks are not an issue, here are the basics:
Manually copy grub splash images into the /usr/share/images/grub folder or install the default grub2 splash
Code:
8 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
The grub2's splash images are normally, but not always, controlled by /etc/grub.d/05_debian_theme. There a
1.99 & later, and 2 variants in Grub 1.98 (see below).
Grub 1.98 late + Grub 1.99 (Maverick / Natty )
Rather than edit the /etc/grub.d/05_header or /usr/share/desktop-base/grub_background.sh
background image designation directly into /etc/default/grub. The path assumes the folder is located i
partition.
Quote:
GRUB_BACKGROUND=/path/filename
Example: GRUB_BACKGROUND="/home/my_username/grub_images/my_grubimage.png"
Find the following line and edit the highlighted area, replacing it with the path and grub splash imag
Quote:
WALLPAPER="/<path-to-image>/<your-image-name-here-including-extension>"
Example: WALLPAPER="/home/my_username/grub_images/my_grubimage.png"
Grub 1.97~beta4
Find the following line and edit the highlighted area, replacing it with the grub splash image you wish
/usr/share/images/grub):
Quote:
.
for i in {/boot/grub,/usr/share/images/grub}/moreblue-orbit-grub {png,tga} ; do
sudo update-grub
9 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
Grub 2 currently supports unencrypted password protection. Encrypted password protection using PBKDF2, as we
currently under development.
Remove GRUB 2
Ensure you have an Internet connection and reliable power source. An interruption of either could leav
unbootable condition.
Code:
The user will be warned the system will be unbootable without installing another bootloader.
Once the packages are removed, many files will still remain in '/boot/grub'
Install GRUB 2
Code:
10 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
The user will be asked for any special commands to add to the default "linux" line.
TAB key to highlight "OK" and press ENTER.
Select the appropriate drive on which to install Grub2 (sda, sdb, etc) by highlighting the entry
Normally a partition (sda1, etc) should not be selected.
Code:
sudo update-grub
Reboot
If you aren't sure if you mounted the correct partition, once it's mounted run "nautilus /mnt" to inspec
correct partition, you should see the normal Ubuntu folders such as /bin, /boot, /etc, /home, etc
Example: sudo mount /dev/sda1 /mnt
Note: The partition to mount is normally the partition on which Ubuntu was installed: sda1, sdb5, etc
partition, use the device on which the /boot partition is located. Grub 2 works best when installed in t
BIOS boots. Also remember that you mount the partition (including the number) in this step, but you
number when you run the "sudo grub-install" command later.
Note: GRUB 2 counts the first drive (X) as "0", but the first partition (Y) as "1"
Only if you have a separate boot partition:
Code:
11 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
Reboot.
See the following thread in the Tutorials section for information and instructions on how to boot Ubuntu and other
ISO Booting with Grub 2
Additional information on the rescue mode is available in the "Command Line & Rescue Mode" section of the Ubun
Rather than duplicate his efforts in this post, here is the link to the original:
http://ubuntuforums.org/showthread.php?t=1014708
Boot the Ubuntu LiveCD, open a terminal (Applications, Accessories, Terminal) and enter the following commands
identify the Windows device (normally sda):
Code:
Bonus Section: BSD Menuentry - If you need to have an entry to boot into BSD/Windows from the Grub2 menu,
into a custom file:
Quote:
menuentry "FreeBSD" {
insmod ufs2
set root=(hd1,1)
chainloader +1
}
The ISO only boots to the grub prompt. It uses the Grub 2 files found on the ISO; if the problem is with the system
should boot. However, the ISO contains no kernels and must be told where to find the correct kernel and initrd files
must know the drive/partition on which the boot files are located and the non-Grub files must exist and be uncorrup
If the user hasn't made a rescue floppy/ISO, other alternatives include the Ubuntu Installation/LiveCD or SuperGru
grub-rescue-floppy.img - For floppy images.
To Install:
Insert a disk in the floppy drive.
Code:
fdformat /dev/fd0
mkfs -t msdos /dev/fd0
dd if=/usr/lib/grub-rescue/grub-rescue-floppy.img of=/dev/fd0
12 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
grub-rescue-cdrom.iso - When burning the image to a CD, select the option to copy an image and
Generate the image using the following command:
Code:
grub-mkrescue --output=<path/filename>
If an error message "/usr/bin/grub-mkrescue: 324: xorriso: not found", install the xorriso
Copy the ISO image to a CD using the CD burning app of your choice.
Once the grub rescue floppy/CD boots to the grub prompt, run the following commands.
The commands are slightly different than those used for booting by other means. The Grub 2 files on the floppy/CD
and initrd.img files need to be loaded.
If vmlinuz and initrd.img do not exist at (hdX,Y)/, you can simplify the typing using the TAB complete featur
On the linux line, type "vml" and then TAB to help complete the kernel number. Ensure the comple
fill the kernel number completely, and don't forget the "root=" and "ro" sections of the linux line.
On the initrd line, type "ini" and TAB to fill in a large part of the name. Continue typing/TABBI
used.
Sections in bold should be changed to match the user's system.
Code:
set root=(hd0,1)
linux (hdX,Y)/vmlinuz root=/dev/sdXY ro
# or if (hdX,Y)/vmlinuz does not exist:
linux (hdX,Y)/boot/vmlinuz-2.6.32.25-generic root=/dev/sdXY ro
# then
initrd (hdX,Y)/boot/initrd.img
# or if (hdX,Y)/initrd.img does not exist:
initrd (hdX,Y)/boot/initrd.img-2.6.33-25-generic
boot
To designate a fallback menuentry, add the following to /etc/grub.d/40_custom. X is the menuentry number (start c
menuentries at 0):
Quote:
set fallback=X
"out of disk" ,"device not found", "no such device" , "root device" Errors
Causes are many, but can be caused by Grub2 not finding partitions/files it is looking for. Some possible areas to ex
Does your BIOS see the files? Older BIOS may not see past 8GB or 137GB of the partition. You may need to c
partition or adjust the BIOS to use the 'large disk' mode or update the BIOS to allow it to use today's larger d
Some users may need to add "rootdelay=90" to the end of the "linux" line in /etc/default/grub. The might be
13 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
http://www.gnu.org/software/grub/manual/
Whether the failure is due to improper user selections or Grub 2's failure to recognize a Wubi install, it has been rep
and users can review it for status updates and recovery options when they become available:
https://bugs.launchpad.net/wubi/+bug/610898
Note: Most of this information has been incorporated, with a few graphics, into a page in the Ubuntu Help site. I w
up-to-date and users are free to continue to post comments here. The help page is located here: https://help.ubuntu
meierfra has been busily building pages which detail how to solve many of the common problems users are experie
SourceForge web page should be one of the first stops for those seeking answers to Grub 2 issues.
Disable the "GRUB_HIDDEN_TIMEOUT=" line by placing a # symbol at the beginning of the line.
14 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
Set "GRUB_TIMEOUT=" to a positive integer (number of seconds to display the menu before automatic sele
press ENTER (no timeout). The entry will look like this:
Quote:
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT="10"
Workaround: During the final stages of the install there is an "Advanced" button which allows the user to select the
Workaround: HP protection tools are rewriting to the MBR when Windows is run. The protecttools app must be rem
#10 in the Bug Report.
"Grub loading. The symbol ' ' not found. Aborted." on Dell machines..
On Dell computers with Dell DataSafe Local Backup (DDSLB) installed, the above message is displayed with a serie
section. This is a reported bug,
bug #482757. Thanks to merry_meercat's post which details how to fix the problem.
"Grub loading. The symbol ' ' not found. Aborted." on Dell machines..
On Dell computers with Dell DataSafe Local Backup (DDSLB) installed, the above message is displayed with a serie
section. This is a reported bug,
bug #482757. Thanks to merry_meercat's post which details how to fix the problem.
20. Links
Grub 2 (help.ubuntu.com)
Grub 2: Title Tweaks
Grub 2: 5 Common Tasks
Grub 2: Introduction
Grub 2: Purge & Reinstall
Grub 2: ISO Booting with Grub 2
Grub 2: Password Protection
15 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
__________________
GRUB2 : Tweaks : Basics : Tasks : ISO : Remove Kernels : PW : Chroot : ISO-Install : Customizer
Last edited by drs305; 2 Weeks Ago at 01:51 PM.. Reason: Editing grub.cfg
sudo update-grub
~$ sudo update-grub
Updating /boot/grub/grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.28-14-generic
Found initrd image: /boot/initrd.img-2.6.28-14-generic
Found linux image: /boot/vmlinuz-2.6.28-13-generic
Found initrd image: /boot/initrd.img-2.6.28-13-generic
Found linux image: /boot/vmlinuz-2.6.28-12-generic
Found initrd image: /boot/initrd.img-2.6.28-12-generic
Found linux image: /boot/vmlinuz-2.6.28-11-generic
Found initrd image: /boot/initrd.img-2.6.28-11-generic
Found memtest86+ image: /memtest86+.bin
Found Ubuntu karmic (development branch) (9.10) on /dev/sda6
done
But it does not add the last Karmic entry in the menu:
Code:
16 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/update-grub using templates
# from /etc/grub.d and settings from /etc/default/grub
#
__________________
HP DV6-2113sa Laptop, AMD Turion™ II Ultra Dual-Core Processor M620, 4Gb memory, ATI Radeon™ HD 4530
Graphics, Ubuntu 10.10 64-bit
Ubuntu Master Roaster I don't know why grub2 isn't picking it up. I have had a few instances of grub2 not
picking up all the kernels scattered over my drives but I don't remember grub2 actually
ignoring ones that it located.
a. Change one of the titles so I know the grub.cfg I see when it boots is the one I am
looking at in the editor (i.e. if there are multiple grub.cfg files on your system). You will
have to chmod +w to actually edit grub.cfg
Join Date: Jan 2007 b. Search your system for multiple instances of the file.
My beans are hidden!
Ubuntu Development c. Place the kernel you want to show up in /etc/grub.d/40_custom so at least it shows up
Release when you update grub. At best you will have two instances - the detected and the
custom entries; at worst you will have at least the one from the 40_custom file. Don't
forget to make the file executable.
Last edited by drs305; July 18th, 2009 at 07:38 AM.. Reason: 40_custom file problem
17 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
set root=(hd0,8)
search --fs-uuid --set c3eb67b1-7f8f-419b-a462-c79a6c76e5de
menuentry "Ubuntu, linux 2.6.28-14-generic" {
linux /vmlinuz-2.6.28-14-generic root=UUID=9018bfe2-9de3-4692-9883-fc2f875e6455 ro quiet splash
initrd /initrd.img-2.6.28-14-generic
The first entry is for Jaunty, which is my primary OS, the second is for Karmic.
This is my fstab:
Code:
18 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
This is my fstab:
Code:
Edit: foxy123 has a separate boot partition for his Karmic install as well, so his sda7 entry was correct. The following was
written before I found out the separate test-boot partition was linked to the Karmic installation.
I believe the problem is with your partition numbers. First, a disclaimer. I'm relying on the comments in fstab being
accurate. Since they aren't updated, they really can't be relied upon unless confirmed via "mount", "sudo blkid", or some
other command. So I'm relying on sda6 being the correct partition number. I'm also making the assumption that the
Karmic install is on sda6 and not sda7, since it is the sda6 UUID in the boot menu.
Grub 2 counts partitions a bit differently. sdXY, with X being the device (a,b,c) and Y being the partition number (1,2,3).
The device starts counting at 0 - sda is device 0. The partitions (and this is a change) start counting at 1, so partitio
is counted as 1. So sdb3 is device 1, partition 3.
In your setup, sda6 should be listed as (0,6). Try this as your Karmic entry and see if it works correctly. If it doesn't,
confirm the device and UUID designations by running "sudo blkid -c /dev/null".
Quote:
__________________
GRUB2 : Tweaks : Basics : Tasks : ISO : Remove Kernels : PW : Chroot : ISO-Install : Customizer
You may have heard about another Linux bootloader called LILO (stands for LInux
LOader). While a sensible option for many Linux users, I believe that GRUB is a better
choice, for several reasons:
19 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
Join Date: Jul 2009 LILO supports only up to 16 different boot selections; GRUB supports an
Beans: 2 unlimited number of boot entries.
LILO cannot boot from network; GRUB can.
LILO must be written again every time you change the configuration file; GRUB
does not.
LILO does not have an interactive command interface.
All in all, it seems that GRUB is the winner. So let's see what this baby can do.
Code:
Join Date: Apr
/dev/sda2: UUID="4d5250be-75cf-4ce4-9295-ae5e2cabd441" TYPE="swap"
2005
/dev/sda5: UUID="4802e809-ecaa-4932-bd01-4a816c0bbd4f" TYPE="ext3" - my /home partition
Beans: 1,189
/dev/sda6: UUID="6ad1f928-50b9-4aea-9495-95df46d08d58" TYPE="ext3" - Karmic / partition
/dev/sda7: UUID="0c98fbe4-ed7c-4134-994a-07d49074e137" TYPE="ext2" - Karmic /boot partition
/dev/sda8: UUID="c3eb67b1-7f8f-419b-a462-c79a6c76e5de" TYPE="ext2" - Jaunty /boot partition
/dev/sda9: UUID="9018bfe2-9de3-4692-9883-fc2f875e6455" TYPE="ext3" - Jaunty / partition
In the Jaunty setup the menu points out to a /boot partition (sda8 c3eb67b1-7f8f-419b-a462-c79a6c76e5de). So
I have to use something like:
Code:
I am having a small issue I cannot figure out. It is not world stopping but annoying.
Join Date: Oct 2004 I have also posted this on the kubuntu forum as I am running Kubuntu but since we are
Location: Switzerland all a family :
Beans: 51 http://kubuntuforums.net/forums/inde...opic=3105336.0
20 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
As some of mentioned that they cannot see the atch. on the kubuntu site I will add them
here as well. sorry.
Attached Files
grubcfg.txt (2.5 KB, 69 views)
30_os-prober.txt (4.4 KB, 44 views)
Here is my fdisk
Code:
21 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
Code:
Glide,
I don't have a lot of expertise with setting up dual boots with Windows - if it was
something obvious and I had a solution I'd post it here.
Join Date: Jan 2007
My beans are hidden!
It appears yours is a Grub legacy question. Since this thread was written about Grub 2, I
Ubuntu Development
suggest you create a new thread for your issue. It will get a bit confusing if we mix the
Release
two on this thread.
Thanks.
__________________
GRUB2 : Tweaks : Basics : Tasks : ISO : Remove Kernels : PW : Chroot : ISO-Install :
Customizer
Bookmarks
Tags
Posting Rules
22 of 23 17/04/11 16:28
Grub 2 Basics - Ubuntu Forums http://ubuntuforums.org/showthread.php?t=1195275
Posting Rules
Smilies are On
[IMG] code is On
HTML code is Off
Forum Rules
vBulletin ©2000 - 2011, Jelsoft Enterprises Ltd. Ubuntu Logo, Ubuntu and Canonical © Canonical Ltd. Tango Icons © Tango
Desktop Project. bilberry
23 of 23 17/04/11 16:28