Grub Boot Error 2
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business
Grub Rescue Commands
Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users grub rescue boot windows Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes grub rescue commands list a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top GRUB error (2) while booting Ubuntu 12.04 up vote 2 down vote
Grub Rescue Unknown Filesystem
favorite I have installed Ubuntu 12.04 on my computer. The install went fine but now I have the next error while booting: grub stage 1.5 - error 2 I'm posting from the live CD and I didn't find an useful answer in Google. 12.04 grub2 boot-failure share|improve this question edited Dec 1 '12 at 18:58 Lucio 8,3921761114 asked Dec 1 '12 at 18:31 Gabriel 113 1 Adding the output of the boot info script to your
Ubuntu Grub Repair
question would help, but stage1.5 is part of grub-legacy and 12.04 uses grub2, so you must have some other disk that has an old broken grub install on it that you are booting rather than the one you installed 12.04 on. –psusi Dec 1 '12 at 20:50 Thanks for your help ! I understand what you wrote, but I'm a newbie with Ubuntu. Where is this boot info script ? I didn't find it. Before installing Ubuntu I was running Kubuntu (don't remember the version). Maybe am I still lauching the old grub... But how to check it ? I tried "sudo grub" on my Live cd, but i get a "command not found"... –Gabriel Dec 1 '12 at 23:49 Google for boot info script and it should be the first thing that comes up. Do you have more than one hard drive? –psusi Dec 2 '12 at 1:24 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote Boot from LiveCD and from a terminal run 'grub-install /dev/hda' command and then boot from the hard disk. The command will do a fresh install of grub on your hard disk and overwrite any previous versions of grub. Hopefully this will fix it. share|improve this answer answered Dec 4 '12 at 22:32 gdesilva 211 add a comment| Your Answer draft sav
error string and then halt. Pressing Ctrl-Alt-Del will reboot. The following is a comprehensive list of error messages for the Stage 1: "Hard Disk Error" This error message will occur if the Stage 2 or grub rescue no such partition Stage 1.5 is being read from a hard disk, and the attempt to determine the
Grub Command Line Boot
size and geometry of the hard disk fails. "Floppy Error" This error message will occur if the Stage 2 or Stage 1.5 is being grub commands read from a floppy disk, and the attempt to determine the size and geometry of the floppy disk fails. It's listed as a different error since the probe sequence is different than for hard disks. "Read Error" This http://askubuntu.com/questions/224336/grub-error-2-while-booting-ubuntu-12-04 error message will occur if a disk read error happens while trying to read the Stage 2 or Stage 1.5. "Geom Error" This error message will occur if the location of the Stage 2 or Stage 1.5 is not in the area supported by reading the disk with the BIOS directly. This could occur because the BIOS translated geometry has been changed by the user or the disk is moved to another machine or controller after installation, or http://www.uruk.org/orig-grub/errors.html GRUB was not installed using itself (if it was, the Stage 2 version of this error would have been seen during that process and it would not have completed the install). Errors Reported by the Stage 1.5 The general way that the Stage 1.5 handles errors is to print an error number in the form "Error: " and then halt. Pressing Ctrl-Alt-Del will reboot. The error numbers correspond to the Errors Reported by the Stage 2 in the listed sequence. Errors Reported by the Stage 2 The general way that the Stage 2 handles errors is to abort the operation in question, print an error string, then (if possible) either continue based on the fact that an error occurred or wait for the user to deal with the error. The following is a comprehensive list of error messages for the Stage 2 (error numbers for the Stage 1.5 are listed before the colon in each description): 1 : "Selected item won't fit into memory" This error is returned if a kernel, module, or raw file load command is either trying to load it's data such that it won't fit into memory or it is simply too big. 2 : "Selected disk doesn't exist" This error is returned if the device part of a device- or full filename refers to a disk or BIOS device that is not present or not recognize
Computing Tutorials Open Source Pro LearnWhat is Linux? Training Certification Events Webinars CommunityParticipate Q&A Forums Blogs ResourcesNewsletter Distributions Publications Infographics Photos Videos Jobs Carla Schroder June 12, 2014 How to Rescue a Non-booting GRUB 2 https://www.linux.com/learn/how-rescue-non-booting-grub-2-linux on Linux Once upon a time we had legacy GRUB, the Grand Unified Linux http://www.plunk.org/~grantham/cgi-bin/blog.cgi?id=00018 Bootloader version 0.97. Legacy GRUB had many virtues, but it became old and its developers did yearn for more functionality, and thus did GRUB 2 come into the world. GRUB 2 is a major rewrite with several significant differences. It boots removable media, and can be configured with an option to enter your system BIOS. It's grub rescue more complicated to configure with all kinds of scripts to wade through, and instead of having a nice fairly simple /boot/grub/menu.lst file with all configurations in one place, the default is /boot/grub/grub.cfg. Which you don't edit directly, oh no, for this is not for mere humans to touch, but only other scripts. We lowly humans may edit /etc/default/grub, which controls mainly the appearance of the GRUB menu. We may also edit the scripts in /etc/grub.d/. grub rescue commands These are the scripts that boot your operating systems, control external applications such as memtest and os_prober, and theming./boot/grub/grub.cfg is built from /etc/default/grub and /etc/grub.d/* when you run the update-grub command, which you must run every time you make changes. The good news is that the update-grub script is reliable for finding kernels, boot files, and adding all operating systems to your GRUB boot menu, so you don't have to do it manually. We're going to learn how to fix two of the more common failures. When you boot up your system and it stops at the grub> prompt, that is the full GRUB 2 command shell. That means GRUB 2 started normally and loaded the normal.mod module (and other modules which are located in /boot/grub/[arch]/), but it didn't find your grub.cfg file. If you see grub rescue> that means it couldn't find normal.mod, so it probably couldn't find any of your boot files. How does this happen? The kernel might have changed drive assignments or you moved your hard drives, you changed some partitions, or installed a new operating system and moved things around. In these scenarios your boot files are still there, but GRUB can't find them. So you can look for your boot files at the GRUB prompt, set their locations, and then boot your system and fix your GRUB configuration. GRUB 2 Command Shell The
how I solved it, in case someone else has the same problem and starts googling around. Don't bother reading this unless you are a Linux nut. I wanted to transition my GRUB partition (typically /boot, but /boot/grub for me) from my second hard disk (don't ask) to my first hard disk. I: booted the Ubuntu 8.10 32-bit CD (actually a USB flash drive) into a live session, ran the partition editor from the "System menu", created a new partition, /dev/sda2, for the GRUB partition and initialized it (mkfs.ext2) for through the partition editor, copied every file from the old GRUB partition, /dev/sdb3, to the new one, unmounted, ran grub and root (hd0) then setup --prefix= (hd0,1) and the result was "Done." (successful) rebooted I received an "Error 2" from GRUB. What this means is that GRUB could not open the partition I initialized it with, which is odd, since I had just used GRUB to set itself up, so I knew that GRUB saw hd0,1 from the Ubuntu live session. I rebooted into the liveCD image. Ran GRUB. I ran find menu.lst and the output was (hd0,1) and (hd1,2) , so GRUB could definitely see both partitions from inside the live session. I ran setup --prefix= (hd2,1) in order to restore the old GRUB partition, and rebooted. Then I was able to enter GRUB's command line using "c". Inside GRUB booted from the BIOS, though, find menu.lst only output (hd1,2) . The implication is that GRUB inside the live session can see both partitions, but somehow the GRUB installed into the MBR could see only the original partition but not the one I just created. GRUB from the BIOS could see my other hd0 partitions, as find vmlinuz returned (hd0,2) , where one of my Linux installations lives, so it's not like the BIOS couldn't see that first drive. So my hunch is that a newer ext2 filesystem has some incompatibility with the old stage1.5 that w