Here is how I created a Grub2 boot-cd with a (grub.cfg) menu:
mkdir /tmp/cdroot
mkdir /tmp/cdroot/boot
mkdir /tmp/cdroot/boot/grub
cp /boot/grub/grub.cfg /tmp/cdroot/boot/grub
cd /tmp
[code]....
NOTE: The above proceedure assumes you already have a grub.cfg file. If you don't, create one in the /tmp/cdroot/boot/grub directory
I've been following this guide [URL].... on creating a custom boot menu for Grub2 and I've run up against a wall. I made it all the way to the section on testing the custom menu but when I do, the new menu refuses to load. When I get to the boot screen I see the standard menu plus an extra entry at the bottom that will show what my custom menu will look like. When I select it though, it won't load. The screen blinks and remains on the main menu. I don't have the correct 'set' and 'search' lines in the 40_custom entry and I don't know how to correct them.
View 6 Replies View RelatedI have a "master" IDE HD upon which reside several Linux OSs and a couple of Windoze OSs. The boot system is Mandriva using Grub Legacy and the latter's menu.lst file is where I select which OS I wish to use. I use HD physical carriers for my HDs. I used GPartEd to copy over newly installed OSs on another drive to the "master" HD. The commands in the menu.lst file for Linux OSs are representative as follows:
Name of OS
root (hdx,x)
configfile /boot/grub/menu.lst
Task: Enter Grub2 which, I seem to understand, is a work in progress. I presume that some commands in Grub2 are not recognizable by Grub Legacy. I installed Debian 6 on another drive and I wish to incorporate an entry in the menu.lst file described above using the technique described above. Is it possible to use the menu.lst file in Grub Legacy (0.97) in order to boot the Grub2 Debian OS? Or am I chasing windmills?
I tend to update stuff slower than most - I'm still using Hardy and I probably won't upgrade to Lucid until June-ish. I wanted to test drive GRUB2 so I upgraded following instructions here:When I chainloaded GRUB2, I got a menu that only contained Ubuntu; my Windows Vista bootloader entry had disappeared. I couldn't find a sample "40_custom" entry to modify when I tried to create an entry for Vista myself. Had no problem booting into Ubuntu and I could still boot Vista from the old menu. Spent about 20 minutes on it, then I gave up and reinstalled legacy GRUB.
View 9 Replies View RelatedI'm having an odd dual-boot problem. Briefly, I can't boot Windows XP from its entry on the GRUB2 menu. If I set the disk order in BIOS so that the machine boots off the drive with Windows XP, XP starts normally. However, if I boot off the Ubuntu drive, which brings up the GRUB2 menu, choosing the "Windows 7 loader" option (why it says Windows 7 when there's only Windows XP is another question!) just makes my system reboot.
It appears there's some problem with the way GRUB2 attempts to start Windows XP. I'm also wondering why GRUB2 thinks it sees the Windows 7 loader. There shouldn't be any Windows 7 anything anywhere. I once had a Windows 7 RC install on the same disk as Windows XP, but I wiped the Windows 7 system partition and reallocated its space as just another NTFS partition. FWIW, GRUB2 is installed on the MBR of the disk containing my Ubuntu install. Windows XP has a different drive all to itself.
change the boot menu - GRUB
I regularly update my ubuntu (10.04), and new minor versions keep accumulating on the GRUB screen. Right now I have 5 different versions listed on the GRUB, even though I always select the latest version to work with.
Am I supposed to do anything to get rid of the old version references? Do these old versions affect disk space/performance?
I had debian squeeze already installed, then installed win 7. Windows overwrote by MBR, as I expected it to, so I used an ubuntu live cd to reinstall grub2 to debian root.
I rebooted, and sure enough I had grub back. The boot menu has debian on it. Just debian (crunchbang actually, but its the same thing).
So I added a script in /etc/grub.d (called Windows_11) to create a windows chainloader entry in grub.cfg, and ran update-grub.
Update-grub picks up my /etc/grub.d/Windows_11 script, and adds an appropriate chainloader entry to /boot/grub/grub.cfg.
So I would expect this new chainloader entry to show up in my boot menu when I boot up. But it doesn't; on booting I only have the option to select debian.
Here is my /boot/grub/grub.cfg -
Code:
### BEGIN /etc/grub.d/10_linux ###
menuentry 'CrunchBang Linux, with Linux 2.6.32-5-686' --class crunchbang --class gnu-linux --class gnu --class os {
insmod part_msdos
[Code].....
i am trying to change the boot order on the GRUB menu so that the countdown automatically starts on an older kernel. From what i can see all the solutions on the web want me to edit the /boot/grub/menu.lst file. The problem is that i don't have one. Someone also mentioned that if i don't have a menu.lst file then i should look for the grub.conf file. I don't have on of those either. The closest thing in /boot/grub is grub.cfg but that looks nothing like the descriptions i have heard of /boot/grub/menu.lst file
View 5 Replies View RelatedAs a long time Red Hat/Fedora user, I'm quite new to the Ubuntu/Debian culture, and/or, to the Grub2 specific behavior.I'd like to see Grub2 system selection menu at every boot time even if I only have a single operating system, Ubuntu 9.10, on my hard drive. What should I do fot this purpose?
View 1 Replies View RelatedAfter upgrading to 10.10 the grub boot menu stopped showing up. I made a custom menu in grub.d and update grub finds everything, but when I restart my system the boot menu never shows. I should have two kernels. How do I get the boot menu to show every time I restart my system?
View 9 Replies View RelatedI just installed Debian squeeze. I installed grub to the MBR. It uses Grub 2. Apparently I'm not supposed to edit /boot/grub/grub.cnf, but /etc/default/grub and /etc/grub.d. I looked at these and read The Readme as well as a tutorial at [URL]. I'm still not sure of what to do. When I boot up I get 4 choices: 2 for Squeeze and two for another linux distro. I would like to edit the print out I get when I boot up, as well as add the partition for XP which wasn't included.
This is /etc/default/grub:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
GRUB_DEFAULT=2
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="" .....
In my Red Hat 7.2 , the /boot/grub/grub.conf has the following data :
But when I reboot my Red Hat server , I don't see the Grub menu to say edit the boot kernel .
I hav two 40 GB hard disks.RHEL5 is installed on 1st and Windows on 2nd. In order to use each OS I manually hav to go and change the "first boot device" option in BIOS setting and boot into required OS. GRUB doesn't show Windows in its boot menu.How can I make GRUB recognize Windows and boot into both OS using GRUB boot menu?
View 1 Replies View RelatedIn order for me to get started with Linux, I downloaded & installed Virtualbox (V3.2.10) on my WinXP machine, and downloaded the Puppy Linux image from as per[URL].. When I start up the VM, I get a GRUB menu allowing me to boot
Quote:
Linux (on /dev/hda1)
Install GRUB to floppy disk (on /dev/fd0)
Install GRUB to Linux partition (on /dev/hda1)
I tried the first option, which results in Quote:
Booting 'Linux (on /dev/hda1)'
root (hd0, 0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz root=/dev/hda1 ro vga=normal
[Code]...
I have a problem with my GRUB bootloader. I have Ubuntu 9.10 and Win XP installed on my laptop. But only the list of Ubuntu appears in the menu and NOT win XP.
Some instructions say try to edit the "menu.lst" file in "/boot/grub/" menu.
But there is no such a file in my /boot/grub/" folder.
I'm running a dual-boot with linux mint and Windows. I have an E-machines desktop with : 760 GB Hard Drive 6GB RAM NVidia GeForce Graphics card 6150se Integrated AMD Athalon II X2 235e dual-core processor My problem is getting my grub to boot into Linux Mint, and the problem may lie with my graphics card. Whenever I install the linux mint for the first time, I am prompted to activate my proprietary NVidia graphics driver, which I do. Then I am asked to reboot.
Upon reboot, the system gets to the grub menu, accepts my selection to boot linux mint, then the "progress dots" appear on the screen. After about 8 seconds, the screen switches into command prompt mode. I never get to the graphical sign-on screen. All I get is the console sign-on prompts. From there my only option seems to be to reboot. (sudu reboot). After which, of course, I am forced to go into Windows vs. Linux to avoid the problem. Once Windows has loaded up, I do a restart and go back into Linux Mint . Finally, I get to the Linux sign-on graphical screen.
To summarize, i cannot restart linux mint without getting stuck staring at a console screen. I can get back into linux mint if i use the command 'sudo reboot', and, from the grub menu, choosing to go into Windows. From Windows, I then do a restart and end up back at the grub screen again, but this time when I select linux mint, things work and I am given the sign-on gui.
If I choose to not install the graphics driver (and put up with the annoying reminder to activate one), the system dual boots without a problem.
I tried making some changes to /boot/grub/menu.lst file by logging in thru su but it throws following error:
[root@localhost avi]# /boot/grub/menu/lst | gedit
(gedit:4874): GnomeUI-WARNING **:
While connecting to session manager:
Authentication Rejected, reason : None of the
authentication protocols specified are supported and host-based authentication failed.
bash: /boot/grub/menu/lst: No such file or directory
The XP partition ceased to boot (in fact when it seems to start Windows, it re-boots once and again). I can access the XP partition from Ubuntu 9.10
If I boot with the WXP CD and reinstall it in the original NTFS partition, will it wipe the boot menu out, loosing any chance to boot in Linux?
I upgraded my main box to Ubuntu 10.04 and everything runs fine, except for a problem with grub: I can't modify the boot menu in any way, I'm stuck with what grub2 thought was the optimal setup at installation time (and it got it wrong, btw). The current boot menu lists:
- my older 9.10 install in sdb2 (one kernel)
- legacy windows XP install on sda1
- my even older 9.04 install in sdb1 (two kernel versions)
- my new install in sdb3, with only one kernel (the one coming with the distro CD)
I tried anything I could think of to modify this menu:
- modify the /etc grub config file then running sudo update-grub
- using a specific app (system manager? don't remember its name)
- upgrading to the latest kernel
- removing and reinstalling grub
to no avail: the menu is still there in the above form, and I have to manually select the 10.04 (old) kernel by hand every time I reboot.
Have recently installed 10.10 and have several other OS' installed, as well as other NTFS (non-OS) partitions. After a couple of updates, my boot menu shows about 8 entries, whereas I should only have about 4... How is this fixed in Grub2?
Have installed Startup Manager, and there seems to be no option here...
I'd like have some text written on my grub2 boot menu.
In legacy grub you could just add: title Foobar and you'd get "Foobar" displayed.
I tried: menuitem "Foobar" {} grub2, but it doesn't work. Any ideas how do you do something like that?
(Yes, I know writing grub.cfg by hand is not very smart. But I have a special situation: I wrote my own grub.cfg on a dedicated boot partition from where I chainload to other grub on other partitions. Those secondary grubs generate their grub.cfgs on the fly, so everything is OK )
I've already read and tested the various guides for pasword portecting the menu items. What I need is a little bit different. I need to protect the whole boot menu so normal users cannot select any entry at all and only let the default entry boot.
View 4 Replies View RelatedI have a dual boot system with Windows XP and Fedora12. Following is the partition structure of my harddisk.
Disk /dev/sda: 80.1 GB, 80060424192 bytes
255 heads, 63 sectors/track, 9733 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x5e5e5e5e
Device Boot Start End Blocks Id System
/dev/sda1 1 1912 15358108+ 7 HPFS/NTFS
[Code]...
I deleted the "/dev/sda8" through Windows Disk Management, and when i restarted the system. GRUB boot menu vanished and a GRUB console appeared. Then I booted my system using Fedora12 live USB and created a new partition at same place from where i deleted it, and then after restart my started working normally as it was before partition deletion.
But, I don't understand what actually happened. Can anyone tell me in detail what happened and why and what to do to avoid such things in future?
I have just updated my Ubuntu linux to Ubuntu 10.4, not my grub menu isnt letting me boot to Windows Partition.The problem seems to be with grubs new update from using an editable menu.lst file to using a non editable grub.cfg file. Everywhere I look it states "DO NOT EDIT THE GRUB.CGF FILE". I am at a loss as what to do. I figured that the new configuration has screwed up the Windows Boot File. Anyone have any suggestions on how to fix this. I am not sure if it is a windows issue or an issue with the Grub boot menu.
View 2 Replies View RelatedI have Ubuntu 9.10, PuppyLinux431 and Windows XP on a Toshiba laptop. I like Ubuntu, but the speed of PuppyLinux is addictive, so that was my default boot until I upgraded Ubuntu which included an upgrade to Grub2.
My problem: Grub2 doesn't recognise PuppyLinux. Using information from [url] I have made an executable file named 07_Puppy in /etc/grub.d and did update-grub from root. Still no luck. I can boot PuppyLinux from the grub command line using the following commands:
Just before grub displays the boot menu, I think I see a very brief message about a syntax error, but it's gone before I can read it.
Here is the contents of my grub.cfg:
Quote:
Why Grub2 doesn't see Puppy and let me boot it from the menu?
My Grub2 boot menu includes:
Ubuntu, Linux 2.6.31-19-generic
Ubuntu, Linux 2.6.31-19-generic (recovery mode)
Ubuntu, Linux 2.6.31-14-generic
Ubuntu, Linux 2.6.31-14-generic (recovery mode)
Q1) I only really need the latest kernel, 2.6.31-19, don't I?
Q2) So how can I get rid of the two 2.6.31-14 entries?
I have two hard drives - (1) 80GB (2) 500GB: the 1st HD has 3 partitions (in that order) - Windows 7, Ubuntu 10.10 & Swap. the 2nd HD is for storage only, and has 2 partitions.
I did the following - I installed Windows 7 on the first partition of the 1st HD, it booted just fine. Then I installed Ubuntu 10.10 on the second partition of the 1st HD.
Windows 7 shows in the GRUB menu alongside with Ubuntu. Ubuntu boots just fine, but when I select Windows it simply restarts the computer and the GRUB menu shows again.
RESULTS.txt of Boot Info Script:
Code:
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #3 for (,msdos3)/boot/grub.
[Code]....
machine boots straight to Windows, Grub2 does not display the normal boot menu choices. Therefore, not able to boot into Ubuntu 9.10.Perhaps someone could look at this Results.txt file and shed some light on what went wrong.This machine was working fine for a long time, then all of a sudden, it starting booting straight to Windows.
View 9 Replies View RelatedI've got myself the curious situation where, when I boot the system, I can get grub to start, but it always drops to the prompt.
I can run:configfile /grub/menu.lst
and this brings up the menu with no problems, and from there I can boot the system to either linux or windows. What I don't understand is why it wont go to the menu in the first place?As far as I can tell, grub/Kubuntu got confused when installing, as each of the hd#,# settings in the menu.lst have needed tweaking to let the system boot. (e.g. windows is actually hd0, but the original install had it at hd2. Likewise linux is on hd1, but the menu.lst had it at hd0). I've happily tweaked these to make the system boot, but would appreciate any help in convincing grub to actually load the menu without me having to use the prompt.
I got ubuntu 10.04 lucid lynx along with windows (dual boot) and using Grub. On my computer, I have my C:/ (programs) and D:/ (data). I've never used my D:/ before that day that I've lost my windows partition on my grub menu. I usually use my D:/ with windows. The first time I used my D:/ to store data with linux, I lost my windows option in my grub menu. I'm not sure what I did wrong but I do want to restore my windows option in my grub menu.
After "fdisk -l",
I checked in /boot/grub and there is no menu.lst to modify. how I can get back my windows option in my grub menu ?