Error No Such Device Grub Rescue Ubuntu 10.04
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 Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes 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 Boot error > no such device: grub rescue [duplicate] up vote 17 down vote favorite 5 This question already has an answer here: How can I repair grub? (How to get Ubuntu back after installing Windows?) 9 answers After an installation of Ubuntu 12.04, erasing an old partition with Ubuntu 10.10, I can't get grub to load. I can't access my Windows 7 partition either I get the message: > error: no such device: 58ABF29C... grub rescue> I suppose my master boot record got erased/corrupted. How can I check and fix this? installation grub2 share|improve this question asked May 29 '12 at 12:43 andandandand 5444716 marked as duplicate by Eliah Kagan, con-f-use, RolandiXor♦ Mar 19 '13 at 17:50 This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question. If your MBR were erased, GRUB would not run at all. What is happening here is that the MBR code is running, and has been told to look on the partition with the UUID of 58abf29c... for the configuration menu. Most likely, this was the partition you erased, so it doesn't exist anymore. The easiest way to fix it would be to download the grub boot repair CD, which will probably fix it automatically. –Marty Fried May 29 '12 at 16:22 A complete answer is here askubuntu.com/questions/125428/… –Bryce Nov 11 '13 at 17:58 add a comment| 3 Answers 3 act
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 Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best http://askubuntu.com/questions/143667/boot-error-no-such-device-grub-rescue answers are voted up and rise to the top working 14.04 ubuntu to error: no such device: grub rescue> up vote 0 down vote favorite I'm a father and I was trying to get one more entry on gnucash after my youngest woke up. I had gnucash, keypass, chrome and LibreOffice calc up when my son found the power button.... Nooooooo! :D When I restarted Ubuntu http://askubuntu.com/questions/777005/working-14-04-ubuntu-to-error-no-such-device-grub-rescue I was met with the following: Error: no such device... grub rescue> I don't think the system was updating and only other software that could be running was CrashPlan. Below is my initial attempt grub rescue> ls (hd0) There is no partition recognized… I tried to change the directory to hd0, but couldn’t (no something something) Then I started Ubuntu up in Live CD mode by “trying Ubuntu” from my original installation CD. I ran Boot Info Script by downloading it from bootinfoscript.sourceforge.net Extracting using the default extractor (not the terminal) Then in the terminal I wrote: Sudo ~/Downloads/bootinfoscript The result is posted below. Boot Info Script 0.61 [1 April 2012] ============================= Boot Info Summary: =============================== => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of the same hard drive for core.img. core.img is at this location and looks in partition 112 for . sda1: __________________________________________________________________________ File system: Extended Partition Boot sector type: - Boot sector info: sda5: __________________________________________________________________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Boot files: ============================ Drive/Partition Info: ============================= Drive: sda _____________________________________________________________________ Disk /dev/sda: 1000.2 GB, 1000203804160 bytes 255 heads, 63 sectors/track, 121601 cyl
Preparation Boot-Repair Search & Set How & Where to Search Specific Troubleshooting grub> grub rescue> GRUB Editing the GRUB 2 Menu During Boot Key Points About Terminal Menu Editing: Menu Editing Examples Post Boot Follow Up https://help.ubuntu.com/community/Grub2/Troubleshooting Fallback mode GRUB 2 Errors Selected Problems and Bugs External Drive Installs and ''grub-pc'' Updates External Drive Installs and MBR Selection Boot Partition is in Logical Volume whose Volume Group contains http://karuppuswamy.com/wordpress/2011/09/09/how-to-fix-grub-rescue-prompt-without-live-cd-for-grub2/ a snapshot insmod fails with "error: no such disk" Links This page provides the user with information on options available for repairing GRUB 2 boot issues and specific instructions on how to error no use the GRUB 2 terminal. The instructions are written for GRUB 1.99, which is the version of GRUB 2 which is included on Ubuntu 11.04, Natty Narwhal, and later. Differences for version 1.98 (Ubuntu 10.4, Lucid Lynx) are noted when the procedures differ. GRUB 2's ability to fix boot problems is greatly improved over the original GRUB bootloader. In addition to an automatic fallback error no such mode if booting from a menuentry in a submenu, GRUB 2 allows the user to edit its menu before the operating system is loaded. The rescue mode GRUB 2 terminal can help boot an operating system so that permanent repairs to system files can be made. The instructions on this page are written for a fully-installed Ubuntu operating system. WUBI boot problems are not covered in detail although they are addressed in several sections. Overview GRUB 2 boot problems can leave the system in several states. The user may see one of the following displays on the monitor when a boot fails. The display provides the first indication of what might be causing the failure to boot. Here are the failure prompts and displays, and the possible cause of each: grub> prompt: GRUB 2 loaded modules but was unable to find the grub.cfg file. grub rescue> prompt: GRUB 2 failed to find its grub folder, or failed to load the normal module. grub>: - The grub prompt on a blank screen. GRUB 2 has found the boot information but has been either unable to locate or unable to us
TS-110 NAS Applications Windows Android Chrome OS Storage HOWTOs Projects Software Hardware Photography How to fix GRUB rescue prompt without Live CD? (For GRUB2) Posted on September 9, 2011 by Black God Recently most of the leading Linux distributions have moved to GRUB2 Boot loader. It has a long list of features. Given that it has some learning curve also. Since it is a boot loader, not an user space application, we don't care about it till it puts us in rescue prompt :-). As usual today I was playing with my laptop and resulted in GRUB rescue prompt. I mean when I boot my laptop, I was not welcomed with GRUB menu, instead with a rescue prompt. I tried grub1 commands in this shell, but unfortunately it did not respond to any command positively. Then I learned about GRUB2 commands and able to get into my Linux installation (Debian wheezy) without any Live CD or other OS installation. So I thought of sharing the commands I used at rescue prompt to boot successfully into the existing Linux installation. Here is the snapshot of my grub rescue prompt session. I believe this will be sweet and short. Enter the following command in sequence. I have given (hdx,y) as generic syntax, where x is your hard disk number and y is the partition number. For example, if your grub is in /dev/sda1 then it is (hd0,1). In linux command line, pass your appropriate root device. I have mentioned it as /dev/sdXX. set prefix=(hdx,y)/boot/grub insmod (hdx,y)/boot/grub/linux.mod The above two command will put grub in regular command mode. This is the extra step you need in case of GRUB2. The below three steps are options, it may be needed - I am not sure. insmod part_msdos insmod ext2 insmod gzio Now continue with GRUB2 commands. set root=(hdx,y) linux /boot/vmlinuz-3.0.0-1-686-pae root=/dev/sdXX ro initrd /boot/initrd.img-3.0.0-1-686-pae boot Guys, now you should see kernel and initial ram disk loading message. You are done! Once booted you c