If you’re using Linux for quite a while and it is your daily task to install and test new Linux distributions, then you might have seen at times all the installed operating systems are not listed in the GRUB menu. It may be due to GRUB not being installed correctly, or GRUB not able scan the hard drives correctly.

If it ever happened to you, do not freak out! It is really very easy to solve. The GRUB 2 bootloader has special tools for scanning the hard drives installed on your computer for bootable operating systems installed on your hard drives.

In this article, I will show you how to solve the problems stated above and use grub2-mkconfig tool to solve it.  I will be using Debian 9 Stretch for the demonstration, but it should work on any modern Linux distribution with GRUB 2 installed. Let’s get started.

What grub2-mkconfig Does:

grub2-mkconfig is a really simple tool. All it does is scan the hard drives of your computer for installed bootable operating systems (including Window, Mac OS and any Linux distributions) and generates a GRUB 2 configuration file. That’s it.

Difference Between grub2-mkconfig and grub-mkconfig:

Even though GRUB 2 is installed on your computer, the grub2-mkconfig command may not be available in your favorite Linux distribution. But the grub-mkconfig command may be available in your Linux distribution. There is no difference between grub-mkconfig and grub2-mkconfig if GRUB 2 is installed.

Note that, if you have GRUB legacy installed, then grub-mkconfig and grub2-mkconfig commands will not be the same.

You can check which version of GRUB is installed on your Linux machine with the following command:

As you can see, on my Debian 9 Stretch machine, GRUB 2.02 is installed. I also don’t have grub2-mkconfig command available on Debian 9 Stretch. It is renamed to grub-mkconfig. So grub-mkconfig and grub2-mkconfig is the same in my case.

Using grub2-mkconfig:

The grub2-mkconfig or the grub-mkconfig command only has one important option. The -o or long format the –output option. It is used to tell GRUB 2 where the generated GRUB configuration file should be saved.

By default, grub2-mkconfig or the grub-mkconfig command prints the generated configuration file to STDOUT, which is the terminal of your Linux operating system.

If this is what you want, then run grub2-mkconfig or the grub-mkconfig command as follows:

As you can see, the generated GRUB 2 configuration is printed on the terminal screen. This may not be very helpful.

If you want, you can export the generated GRUB 2 configuration to a file. The format of the command is given below:

If you prefer the long format, then

NOTE: Here, FILE_PATH is the path to the file where you want the generated GRUB 2 configuration to be saved.

Let’s say, you want to save the generated GRUB 2 configuration to a file grub.cfg in your user’s HOME directory.

To do that, run the following command:

As you can see, a new GRUB 2 configuration file is generated.

As you can see, grub.cfg file is generated on my user’s HOME directory.

As you can see, the contents of the generated grub.cfg file is the same as earlier when I printed the output in the terminal.

Updating GRUB 2 Configuration File (BIOS):

If you’re using old BIOS based motherboards, then the GRUB 2 bootloader configuration file should be in the /boot/grub/grub.cfg file as you can see in the screenshot below.

NOTE: On some Linux distributions such as CentOS 7 or RHEL 7, the GRUB 2 configuration file can be found at /boot/grub2/grub.cfg. If it is the case for you, then make sure you adjust the path before you run the grub2-mkconfig or grub-mkconfig command in the article below.

To update the GRUB 2 configuration file on BIOS based Linux installation, run the following command:

The GRUB 2 configuration file should be updated.

If you’re expecting any changes, restart your computer with the following command:

You should see what you’re expecting in the GRUB menu just after you press the power button.

Updating GRUB 2 Configuration File (UEFI):

On UEFI based motherboards, updating the GRUB 2 configuration is a little bit trickier.

On EFI based Linux installs, the GRUB 2 configuration file is in the /boot/efi/EFI/<YOUR_OS>/grub.cfg

Here, <YOUR_OS> is the name of the directory where the grub.cfg is located. The directory name will be different for each Linux distribution. The trick is to determine the name of the directory that is being used at boot time. If you haven’t been playing around with different Linux distribution, chances are higher that there will be only one directory. Otherwise, there will be many directories from which you will have to determine the active one.

Run the following command to list all the available directories in the /boot/efi/EFI directory:

As you can see, on my CentOS 7 machine, I have only one directory centos/

Now to update the GRUB 2 configuration file, run the following command:

The GRUB 2 configuration file should be updated.

Now reboot your computer and you should see your expected entries in the GRUB menu.

Other Usage of grub2-mkconfig and grub-mkconfig:

Suppose you updated the kernel of your favorite Linux distribution. After the installation, you checked the version of your kernel and you’re surprised that it was not updated! Oh no!

Well, don’t get upset. The grub2-mkconfig or the grub-mkconfig command can also scan the /boot directory to check for installed Linux kernels and generate a GRUB 2 boot entry for each of them.

The commands and the processes are the same as given in the Updating GRUB 2 Configuration File (BIOS) and Updating GRUB 2 Configuration File (UEFI) sections of this article above.

So that’s how you use grub2-mkconfig or grub-mkconfig command to solve many boot problems on Linux. Thanks for reading this article.