Grub loading error 22 windows

What Is GRUB

GRUB or GNU GRUB is short for GRand Unified Bootloader. It is a boot loader used on multi-OS computers that provides users the choice to choose which operating system to boot from on the computer. Different operating systems may need varying boot loaders. For example, NTLDR is the boot loader for Windows NT operating systems, and LILO is the boot loader for Linux. As for GRUB, it is the boot loader for Windows and Linux and is generally used on computers that are with both Windows and Linux installations.

Here’s a quick view of common GRUB loading errors and corresponding solutions. Jump to the part you’re most interested:

Workable Solutions Step-by-step Troubleshooting
Fix 1. GRUB Loading Error 15 boot from the Live CD, and mount/boot depending on your partition…Full steps
Fix 2. GRUB Loading Error 17 use a distribution CD or Live CD to set up Grub as sudo grub > root (hd0,0) > setup (hd0) exit…Full steps
Fix 3. GRUB Loading Error 21 Boot the computer from the Ubuntu installation disc > Run Command Prompt as an administrator…Full steps
Fix 4. GRUB Loading Error 22 Restart the computer and press «F8» until you see the options, go back to the menu…Full steps

Common GRUB Loading Errors

However, it’s not without a problem while using GRUB. Many users have the experience of encountering the GRUB loading error during the computer startup. There are two versions of GRUB, and if you’re using Stage 1.5 or Stage 2.0, you’ll probably encounter grub loading error 15, 17, 21, or 22.

GRUB loading error 15

File not found. This error is displayed when the specified file name cannot be found.

GRUB loading error 17

Cannot mount selected partition. This error is displayed when the partition requested exists, but the file system type is not be recognized by GRUB.

GRUB loading error 21

The selected disk does not exist. This error is displayed if the disk is not recognized by the BIOS in the system.

GRUB loading error 22

No such partition. This error is displayed if a requested partition isn’t on the selected disk.

What Causes GRUB Loading Error 15, 17, 21, 22

When you install Windows and Linux on a computer, you need to configure GRUB correctly to boot from one of the operating systems successfully. Or you may encounter GRUB loading errors, like error 15, 17, 21, and 22. The common GRUB loading errors might be caused by:

  • Improper configuration of GRUB
  • The wrong installation location of GRUB
  • Accidental deletion of GRUB
  • The corruption of MBR

How to Fix GRUB Loading Error 15, 17, 21, 22

The solutions differ based on the error you are faced with. Specify the error message you encounter and carry out the corresponding solution.

Fix GRUB Loading Error 15

Make sure the kernel exists. To find out what the exact kernel name is, boot from the Live CD, and mount /boot depending on your partition and then do the following: cd /boot | ls

Fix GRUB Loading Error 17

Make sure your root(x,y) settings are right in your Grub.conf. You could use a distribution CD or Live CD to set up Grub as shown below. (h0,0) means the first hard drive and the first partition on that drive.

sudo grub

root (hd0,0)

setup (hd0) exit

Fix GRUB Loading Error 21

Step 1. Boot the computer from the Ubuntu installation disc.

Step 2. Run Command Prompt as an administrator.

Step 3. Enter the following command:

$sudo -s
#grub
grub> find /boot/grub/stage1 (then cmd will return something like «hd0,0»)
grub> root (hd0,0)
grub> setup (hd0)
grub> quit

Fix GRUB Loading Error 22

Step 1. Restart the computer and press «F8» until you see the options.

Step 2. Go back to the menu where you can choose the operating system.

Step 3. Choose «Microsoft Windows Recovery Console». (You may need your Windows installation disc to access the recovery console.)

Step 4. If you are asked to choose the system drive, enter the number in front of the system drive listed.

Step 5. Enter the account password as required. Run the command fixmbr and enter «y» to confirm the operation.

Step 6. Enter «exit» and restart the computer.

How to Recover Data Lost After Fixing GRUB Loading Error

Applies to: Restore all lost files and data after fixing GRUB loading error in Windows 10/8/7.

Applying the fix for a specific grub loading error in Windows may cause data loss. For example, some operations would format the disk partition or delete hard drive contents. So it’s necessary to learn how to recover data after getting rid of the grub loading error on your computer.

Reliable EaseUS Data Recovery Wizard — EaseUS Data Recovery Wizard specializes in file recovery on all Windows operating systems. It allows you to recover data lost due to the GRUB loading error effectively in only a few simple clicks.

See how to recover the accidentally deleted or formatted hard disk data while fixing GRUB loading error on your computer with ease:

Step 1. Run EaseUS Data Recovery Wizard. Choose the drive where you lost files and start scanning by clicking «Search for Lost Data». This software allows you to recover lost data from all devices, including HDD, SSD, USB drive, SD card, pen drive, camera, etc.

select a location to scan

Step 2. Browse the full scan results. You can choose the file type you need by clicking on the file type filter. EaseUS data recovery software supports 1000+ file types like photos, videos, documents, emails, audio files, and many more. 

Choose files to recover

Step 3. Select the files you want to preview. Click «Recover» and set a storage location or Cloud drive to save the recovered data. 

Recover lost data

Besides, you can also apply this data recovery software to recover files and data lost on the desktop, laptop, internal hard drive, external hard drive, removable USB flash disk, pen drive, memory card, and many more storage devices.

The Bottom Line

GRUB loading errors always occur on computers with dual OS, and each error code is informative since it indicates what the possible cause is. Apply the solutions provided to cope with the issue and use EaseUS Data Recovery Wizard to retrieve the data when data loss happens.

When you boot your computer, you might find that your computer is stuck in Grub Loading Error 15, 17, 21, or 22. Do you know what they are, the causes of these GRUB Load Errors, and how to fix them to make your computer go back to normal? This MiniTool article shows you the answers.

What Is GRUB Loading Error?

GRUB, which is also known as GNU GRUB, stands for GNU GRand Unified Bootloader. It is a boot loader package from the GNU Project. It provides you a choice to boot one of multiple operating systems installed on a computer or choose a specific kernel configuration available on a particular operating system’s partitions.

It is similar to NTLDR or BOOTMGR on Windows. But, it supports both Windows and Linux kernels and has more features. You need to configure GRUB properly when using your computer. If not, you might encounter different kinds of GRUB errors like Grub Loading Error 15, 17, 21, 22….

Tip: If you encounter the BOOTMGR is missing issue, you can refer to this article to solve it: 11 Solutions to “BOOTMGR Is Missing” Error in Windows 10/8/7; If you are facing NTLDR is missing issue, you can read this post to get the solutions: 10 Solutions to Fix NTLDR Is Missing in Windows 10/8/7.

Now, we will introduce these common GRUB Loading Errors in the following content.

Common Grub Loading Errors

Usually, there are no error codes in Grub Stage 1. You might just receive the error message saying Hard Disk Error, Floppy Error, Read Error, or Geom Error. The GRUB loading error code always appears in Grub Stage 1.5 or Stage 2.0.

There are 4 common GRUB Loading Errors:

  1. Grub Loading Error 15: File not found. This GRUB Loading Error always appears when a specified file name cannot be found by the system.
  2. Grub Loading Error 17: Cannot mount selected partition. This GRUB Loading Error always appears when the required partition exists, but the type of file system is not recognized by GRUB.
  3. Grub Loading Error 21: Selected disk does not exist. This GRUB Loading Error always appears when the disk is not recognized by the BIOS in the system.
  4. Grub Loading Error 22: No such partition. This GRUB Loading Error always appears when a required partition is not on the selected disk.

Top Reasons for GRUB Loading Errors

Why do the GRUB Loading Errors occur when you boot your computer? Here, we collect some reasons and show them as follows:

  • The configuration of GRUB is improper.
  • GRUB is installed in a wrong location.
  • GRUB is deleted by mistake.
  • MBR is corrupted.

Now, you know what GRUB is, the common GRUB Loading Error codes, and the top main causes of these errors. Then, if you are bothered by the GRUB Loading Error, you must want to get rid of it immediately because you still need to use your computer to deal with your work. Keep reading to get the solutions.

How to Fix GRUB Loading Errors?

Focusing on these 4 GRUB Loading Errors, we will introduce 4 different solutions. You just need to select a suitable solution according to the error code you receive.

How to Fix GRUB Loading Errors?

  1. How to fix GRUB Loading Error 15?
  2. How to fix GRUB Loading Error 17?
  3. How to fix GRUB Loading Error 21/22?

How to Fix GRUB Loading Error 15?

If you are bothered by Grub Loading Error 15, you need to make sure that the kernel file exists on your computer. Here, you need to shut down your PC and then boot it from the live CD. Then, you can mount /boot on your partition and then do the following: cd /boot | ls to check the exact name of the kernel file.

It is quite possible that the kernel file is missing from your computer. If so, you can still use the live CD to perform a system reinstallation to get rid of the issue.

How to Fix GRUB Loading Error 17?

If you are facing Grub Loading Error 17, you need to make sure that your root(x,y) settings are right in your Grub.conf. You still need to use a live CD to set up Grub as follows:

1. Boot your computer from a live CD.

2. Execute this command: sudo fdisk –l.

3. You are likely to get the following results:

Disk /dev/sdb: 500.1 GB, 500107862016 bytes

255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x62ff371f

Device Boot Start End Blocks Id System

/dev/sdb1 2048 206847 102400 7 HPFS/NTFS/exFAT

/dev/sdb2 206848 174082047 86937600 7 HPFS/NTFS/exFAT

/dev/sdb3 174082110 976771071 401344481 f W95 Ext’d (LBA)

Partition table entries are not in disk order.

The cause of the problem appears on the last line: Partition table entries are not in disk order.

4. You can fix the problem by executing the following command: sudo fdisk /dev/hda. hda means the whole hard disk.

5. If you are an expert, you can select x and press Enter. If you are not an expert, just skip to the next step.

6. Select f and press Enter to fix the partition order.

7. Select w and press Enter to write table to disk.

8. Then, you need to finalize these command one by one in GRUB:

sudo grub

root (hd0,1)

setup (hd0)

quit

Here, (h0, 1) stands for the first hard drive and the second partition on that drive.

Of course, the above hd0,1 and hd0 are just examples. You need to know which hard disk houses your OS and then replace the numbers according to your actual situations.

When all these steps are done, you can restart your computer to check whether it can work as normal.

How to Fix GRUB Loading Error 21/22?

If you are bothered by GRUB Loading Error 21/22, you can follow these steps to fix the problem.

  1. Boot your computer from the live CD.
  2. Open a terminal and then run sudo grub. This can lead you to a GRUB command line.
  3. Run find /boot/grub/stage1.
  4. Then, run root (hd0, 1). Here, (h0, 1) stands for the first hard drive and the second partition on that drive. You can replace these two numbers according to your own situation.
  5. Next, run setup (hd0).
  6. At last, run quit to complete the operation.

After these 6 steps, you still need to reboot your computer to see whether the GRUB Loading Error 21 or GRUB Loading Error 22 is disappeared.

Click to tweet

If You Lose Your Data Due to GRUB Loading Errors

After the GRUB Loading Errors are solved, you can use your computer as usual. However, you may find that some important files are missing from your device by accident due to the error. In a situation like this, you can use a professional data recovery software to get back your data. Here, we suggest using MiniTool Power Data Recovery.

This free file recovery tool is specially designed to rescue your lost and deleted files from your computer hard drives, SD cards, memory cards, pen drives, CDs, DVDs, and more. It has 4 recovery modules that are designed for different situations.

For example, if you want to recover data from a partition on the hard drive, you can use the This PC module. But, if you have repartitioned the hard drive after missing files, you’d better use the Hard Disk Drive module because it enables you to scan the entire drive at once.

This software is designed for Windows computers. However, if your computer is dual-boot (Windows and Linux), you can choose to recover your Linux data under Windows.

MiniTool Power Data Recovery has a trial edition and you can use it to scan the drive that has saved your lost files and then check whether it can find the files you want to restore. If you are interested in it, you can press the following button to download and then install it on your computer to have a try.

MiniTool Power Data Recovery TrialClick to Download100%Clean & Safe

After installing MiniTool Power Data Recovery on your device, you can use these steps to retrieve your data.

1. Open this software and you will enter the This PC interface directly.

2. Suppose that you want to recover data from a partition, you can just stay at this recovery module. Then, you need to select the target partition and press Scan to start the scanning process.

select the target partition to scan

3. The whole scanning process will last for a while. To make sure that you can get the best data recovery effect, you need to wait until the whole process ends. Then, this software will show you the scan results by path.

Here, you can click each path and unfold the folders in it to find your needed files. However, you may find that it is not easy and fast to find the target items using this method. If so, you can use other features of this software to perform a quick search.

For example:

  • Type: The Type feature can enable the software to show the scan results by type. You must know which type of data you want to recover. So, you can select that type to find your needed files quickly.
  • Show Lost Files: After scanning, this software will show you all the data on the drive including existing and deleted files. If you only need to restore the deleted files, you can use this feature to make the software only show you the lost files. This can narrow down the search range.
  • Find: If you still remember the name of the file you want to recover, you can use this feature to directly locate that file. However, if the name of the file is damaged, you will be unable to use this method to find your data.
  • Preview: This feature enables you to preview different types of files. So, if you are not sure whether it is the file you want to restore, you can just preview it to make a confirmation.

Type, Show Lost Files, Find, and Preview

4. You are not allowed to use this trial edition to recover the scanned files. However, you can update this software to a full edition and then recover your needed files without limits. If you are a personal user, the Personal Ultimate edition can fully meet your need and you can even enjoy a lifetime free update.

Here, you need to know that you should not select the files’ original path to save these data. Otherwise, the deleted files will be overwritten and become unrecoverable.

Click to tweet

Bottom Line

Now, you should know what GRUB is, the GRUB Loading Errors you may encounter when booting your PC, and how to get rid of these errors. At the same time, we also recommend a data recovery software for recovering your lost and deleted files that are caused by these GRUB Loading Errors. We hope this article is helpful to you.

Should you have any related issues, you can contact us via [email protected] or let us know in the comment.

GRUB Loading Error FAQ

What is a GRUB Loading Error?

A GRUB Loading Error always happens when you boot the computer. It can be caused by improper GRUB configuration, a wrong location of GRUS, missing GRUB, corrupted MBR, etc.

How do I fix grub loading errors?

There are different kinds of GRUB Loading Errors like GRUB Loading Error 15, 17, 21, and 22. This current article shows you the corresponding solutions. You can scroll up to find them.

How to fix Error No Such Partition Grub Rescue?

Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00087a69

Device    Boot     Start       End    Blocks  Id System
/dev/sda1 *      4208640 171976703  83884032  83 Linux
/dev/sda2           4095 234436544 117216225   5 Extended
/dev/sda5           4096   4192964   2094434+ 83 Linux
/dev/sda6      171978752 180152909   4087079  82 Linux swap / Solaris
/dev/sda7      180156416 234436544  27140064+ 83 Linux

Partition table entries are not in disk order.

Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 1FB3931F-D0F2-45C4-A61C-6E886D513BB0

Device           Start          End   Size Type
/dev/sdb1         2048       206847   100M EFI System
/dev/sdb2       206848       468991   128M Microsoft reserved
/dev/sdb3       468992    838862847 399.8G Microsoft basic data
/dev/sdb4    838862848    840959999     1G Microsoft basic data
/dev/sdb5    840960000    972031999  62.5G Microsoft basic data
/dev/sdb6    972032000   1496319999   250G Microsoft basic data

Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 059E108F-BC76-453C-9CA5-A939A4255E18

Device    Start          End Size Type
/dev/sdc1  2048   2156677119   1T Linux LVM

Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 7BAC7364-E807-4F1B-923C-53D157401D6E

Device    Start          End Size Type
/dev/sdd1  2048   2156677119   1T Linux LVM

Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 8EDDD864-C362-40C5-9F72-25A3A9CBB495

Device    Start          End Size Type
/dev/sde1  2048   2156677119   1T Linux LVM

Disk /dev/sdf: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D681678B-941B-4A1E-B848-B8DA4ED901A6

Device    Start          End Size Type
/dev/sdf1  2048   2156677119   1T Linux LVM

Disk /dev/mapper/HydrangeaVG-home--escape_rmeta_0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/HydrangeaVG-home--escape_rimage_0: 1 TiB, 1099511627776 bytes, 2147483648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/HydrangeaVG-home--escape_rmeta_1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/HydrangeaVG-home--escape_rimage_1: 1 TiB, 1099511627776 bytes, 2147483648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/HydrangeaVG-home--escape: 1 TiB, 1099511627776 bytes, 2147483648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Anyone know what a Grub is other than the critters in the ground? ;)

A long time client brought in a PC that was only a month old from their local church.

Things were not running properly on the system and they wanted us to clean things up.

The system booted into Windows XP with no issues.

We cleaned up the user setup, set security on the user profiles and the Line of Business (LoB) applications, and checked into the partitioning since there were two partitions on the machine with My Documents and their key LoB application moved and installed on the second partition respectively.

When we opened the Computer Management console and checked out the Disk Management console the partitioning was particularly strange.

The OS sat on a small C: partition at the beginning of the drive and the D: partition sat at the end of the drive.

There were two unknown partitions in between. Our client did not know what they were and, given the newness of the system, knew they were not supposed to be there. So, we deleted them, restructured the two partitions to take up the unused space and continued on our way.

When we rebooted the system after some updates though, we found out that there was a little more going on than a goofy partition scheme.

We saw:

Grub 1.5
Error 22
*blinking cursor*

Upon seeing that, the light came on upstairs: Linux.

How Linux was installed on the new machine was a mystery.

How to get our Windows XP back was also a bit of a mystery. A search on the Web brought us to instructions that we already knew: We needed to reset the MBR (Previous blog post).

Once we reset the MBR following the above instructions, we were greeted with the Windows XP boot screen and eventually the OS desktop.

Needless to say, access to that machine will be restricted and monitored from now on!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Для чего нужен безопасный режим windows 10
  • Schannel 36871 windows 11
  • Общественная сеть без доступа к интернету как исправить windows 10
  • Книга введение в windows server 2016
  • Wds образ windows xp