Shulou(Shulou.com)06/01 Report--

Editor to share with you Ubuntu reinstall failed to enter repair grub rescue mode how to do, I believe that most people do not know much, so share this article for your reference, I hope you will learn a lot after reading this article, let's go to know it!

Because there was a problem with the mouse after upgrading the Ubuntu from 13.04 to 13.10, it kept flashing as soon as it opened the web page, and a lot of things were different and difficult to use, so I chose to reinstall the system, but when I reinstalled it, I was divided into zones again, and then finished, a restart, a tragedy, and entered the repair grub rescue mode. I don't know what to do for a while, but fortunately, there is a tablet that can surf the Internet and search the Internet immediately. Soon found a lot, click on the first, "start with a flash drive to enter the Windows system to rewrite mbr"? Then my Ubuntu will be gone! Direct pass repair! "repair directly under grub rescue". Well, this is good. Try it according to the given method right away, I'll go, it's completely different! No change at all! Then search, um, this article seems to be much more reliable, and it also writes about the corresponding situation of this kind of problem. yes, it is caused by rezoning, and this seems to be it. Do it right away.

1. Enter set to view the current settings (it turns out that this is to check the current settings, and the previous search is not clear)

2. Enter set root= (hd0,msdos11). No wonder there is no change in mine just now. There is no set found before the choice, just root= (hd0,msdos11). (msdos11 is the location where my Ubuntu is installed. Everyone is different. You can use ls (hd0,x) / root/grub to check which partition is installed. After running the command, there are a lot of files.)

3. Enter insmod / grub/normal.mod, damn it, without this file, what's going on! Isn't mine Ubuntups! This is not scientific! Calm down, calm down! Check which disk Ubuntu is installed on which there are several folders, whether the path of the file is not the same, well, check an other file path to see, enter ls (hd0,msdos11) / root/grub/i386-pc, a return, come out a long list of file names, most of them are .mod and .img, this should be it, change the command to insmod (hd0,msdos11) / root/grub/i386-pc/normal.mod, success!

4. Enter normal, enter, familiar startup menu comes out. But it's not over.

5, Ubuntu, open the terminal, type sudo update-grub, and update the boot file.

6. Enter sudo grub-install / dev/sda, wait a few seconds, damn it, fail, there is no reason! Forget it. Try rebooting. Waiting. I'll go, it's grub rescueurs again! Start all over again, enter Ubuntu again, pull down the web page again, and there is a solution, but just now you don't care because you want to start with live cd, just try this method again! Generally speaking, the repair should have been completed here, but my situation is different. I redivided the zone during reinstallation, and I also respecified the location of the boot file. I need to use the following method again. )

7. Type sudo mount / dev/sda11 / mnt to mount the installed disk on / mnt

8, enter sudo grub-install-- boot-directory=/mnt/boot/dev/sda, damn it, what is this string of things? I didn't type it wrong, how come it didn't run successfully! Try again! It's still like this! After several repeated attempts, forget it, restart it, the miraculous startup menu is out! Has the execution been successful?!

The above is all the contents of the article "what to do if Ubuntu reinstall failed to start and enter repair grub rescue mode". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.