Why grub console

Hurrah, we have found the root filesystem. You can omit the msdos and gpt labels. If you leave off the slash it will print information about the partition. You can read any file on the system with the cat command:. Then run these commands, using your own root partition, kernel, and initrd image:. The first line sets the partition that the root filesystem is on.

The second line tells GRUB the location of the kernel you want to use. How do you know the correct partition? I think you can extrapolate the rest. The third line sets the initrd file, which must be the same version number as the kernel. If his solution doesn't help you can actually reinstall the grub. To do that:. Ubuntu partition is the one with the name "Linux" not necessarily the one with the star, although could be. B If the previous repair doesn't solve your problem, you can try to use 'BootRepair'.

One potential fix I can't promise this will work would be to boot the system using an Ubuntu or other Linux Distro LiveCD and running the command sudo update-grub. This will cause grub to look for any OS kernels and add them correctly to the boot menu.

Again, this is not a guaranteed fix, but it can at times work. Maybe you removed the kernel file or your grub configuration file have some mistakes. It can manually specify a kernel to boot like below,. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Melebius SanHolo SanHolo 10 10 bronze badges.

In my case this brings me back to the terminal, and the 2nd exit boots to the primary OS. ThunderBird 1, 11 11 gold badges 17 17 silver badges 30 30 bronze badges. For Ubuntu Athul Athul 1. In case the questioner is not as familiar with command line operations as you are, perhaps you could add a few words of explanation as to what these commands do and why you suggest doing them. The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end.

Does ES6 make JavaScript frameworks obsolete? Featured on Meta. Now live: A fully responsive profile. Linked 0. See more linked questions. Related 2. Installation of GRUB is a two-step process. The second step is to install and configure GRUB as the boot loader for your system. The first step is the usual: download the source archive, untar it, configure and make install. Assuming you have found a source mirror see www.

For the second step of installation, we will first build and work with a GRUB boot floppy. This way we can use GRUB to learn about its features while testing various configurations for our particular system. Even if you decide not to install GRUB on your hard disk right away, no harm done: you will now have your own GRUB boot floppy available to rescue systems with trashed boot loaders.

That way, we will always be able to get to its menu configuration file if we need to. Scrounge around in your junk drawer for some unused floppy a new one would be even better , and give it a fresh format and FAT filesystem:. We will discuss the features of this shell in more detail a little further on.

For now, enter the following series of commands at the grub prompt:. Figure 1. GRUB in command-line mode. And that's it! This sequence of commands completes the installation of GRUB on the floppy disk.

It is now bootable and will allow us to boot any other OS on our system. To see how GRUB may be used to boot a multitude of different operating systems, consider this example setup:. Note that although GRUB and Linux are capable of dealing with installations in extended partitions, here we show a preference for using primary partitions whenever possible. Filesystems in primary partitions are often mountable by other operating systems, whereas cross-OS mounting filesystems in extended partitions is often not supported.

This system has two hard disks with six different operating systems using seven partitions. As you probably know, each OS has its own nomenclature for naming devices and partitions. You get large helpings of this alphabet soup whenever maintaining any multiboot setup. Since GRUB also needs to be capable of loading any of these systems, it has its own OS-neutral naming conventions for referring to devices.

Hard disks are all hd, floppy disks are fd, device numbering starts from zero, partition numbering starts from zero and complete device names are enclosed in parentheses. With these naming rules, the floppy disk is fd0 , the Win98 partition is hd0,0 , and GRUB recognizes the Slackware and Debian partitions respectively as hd0,1 for slackware and hd0,2 for debian.

Okay, ready to give GRUB a taste? Badda-bing, badda-boom, that postage-stamp-sized Tux appears in the upper-left corner of your screen yes, Slackware is configured to use the framebuffer device , and Linux bootstraps its jolly way into glorious being. Another example. Reboot the system again with the GRUB floppy, and enter the following commands at the grub prompt:.

Now your screen turns into a vague blue cloud, and you think you have made some horrible mistake. Then you realize it's only Windows and you remind yourself to expunge this partition one day soon. Let's take a closer look at these examples. If the device has a filesystem recognized by GRUB that is, one of ext2fs, reiser, ffs, etc. The argument to the kernel command is the filename of the boot image relative to the device specified by the root command above.

The kernel image specified is now loaded and sent rolling down the royal road to bootdom.