I was stuck with GRUB command line ... What I did was funny !

 What is GRUB?

GRUB, which stands for GRand Unified Bootloader, is a widely used boot loader for Linux-based operating systems. It's typically installed on the computer's hard drive or another storage device's boot sector. When you start your computer, GRUB is the first program that runs and allows you to choose which operating system or kernel configuration to boot into if you have multiple options installed on your system.

Is Grub necessary ?

As usual my Indian mind thought of uninstalling the problem maker. At the end, I saw the GRUB manual and figured out, its necessary (not optional). why?

1. GRUB loads the kernel and any necessary initial ramdisk (initrd) files into memory before handing control over to the kernel. Without GRUB, there wouldn't be a convenient way to initiate the boot process and load the operating system kernel.
2. GRUB features are highly beneficial for various use cases, including system maintenance, recovery, and troubleshooting.
3. GRUB is necessary if you want to boot from USB

My Thoughts Train - What is this?! I thought I can simply uninstall and fix my issue. Unknowingly googled about GRUB

SO What I did ?

Immediately I ran to StackOverFlow. Here is the fix,

Step 1: Find the partition in which your Linux partition is stored. We can use the ls command to check for available partitions and their filesystem. Linux operating systems usually use ext2/ext3/ext4 filesystems.

grub> ls

Note: If you don’t know which partition has Linux OS then you can check with the ls command as follows:

grub> ls (hdX, Y)

Here, X is disk number and Y is partition name. For Example: grub> ls (hd0, gpt3) or grub> ls (hd1, msdos5)

Step 2: After knowing the partition, set root and prefix variables:

root: Variable which points where the entire Linux OS is installed.
prefix: Variable which points where the GRUB is installed.

grub> set root=(hdX, Y)
grub> set prefix=(hdX, Y)/boot/grub

Step 3: Install normal module and load it:

normal: Linux mod file (linux.mod) used to load kernal. Command used to install mod : insmod

grub> insmod normal

Run this mod file the setup your GRUB:

grub> normal

Step 4: Update GRUB. After entering your Linux OS, reinstall GRUB and update it. Open the terminal and enter following commands:

sudo grub-install /dev/sdXY

sudo update-grub

Here, X is disk number and Y is partition number of EFI partition. If you don’t know which partition is an EFI partition, use Disks or GParted to check. Restart your PC and the Minimal GRUB error will be solved!!

Over ! Be Proud of Yourself.

Wait ! Wait ! Now you have to solve problems with your team.

There are other people who struggled to fix this, 

GRUB's Tales from the Boot Sector:

Here are a couple of interesting stories about the GRUB command line:

1. The Rescue Mission:

It was a dark and stormy night (well, it definitely felt that way). Sarah, a freelance web developer, was working on a critical project deadline. Suddenly, her computer sputtered and died. Panic surged as she restarted the system. Instead of the familiar boot screen, she was greeted by the stark white text of the GRUB command line. Her heart sank. She'd vaguely heard of GRUB, but its cryptic commands seemed like an alien language.

Desperate, Sarah searched online, scouring forums for solutions. With trembling fingers, she typed in commands, a mix of hope and fear with each keystroke. Thankfully, the commands to boot into a live Linux environment appeared on a forum. Relief washed over her as the familiar desktop loaded. Using the live environment, she diagnosed a failing boot sector. With a combination of GRUB commands and online tutorials, she painstakingly rebuilt the sector, her fingers flying across the keyboard. Finally, after what felt like an eternity, the familiar boot screen returned. Sarah had successfully rescued her system, all thanks to the power (and frustration) of the GRUB command line.

2. The Dual-Booting Duo:

Alex, a tech enthusiast, had always wanted to try Linux alongside his Windows system. He meticulously followed online guides, carefully partitioning his hard drive and configuring the GRUB bootloader. However, on his first reboot, disaster struck! The GRUB menu presented two identical entries, both labeled "Ubuntu." Panic ensued. Booting into either option resulted in the same error message.

Thinking back, Alex remembered a forum post mentioning a situation like his. Taking a deep breath, he launched into the GRUB command line. Using the ls command, he discovered a hidden partition, a leftover from a previous attempt. With a carefully crafted set command, he targeted the correct partition. Finally, upon rebooting, the GRUB menu displayed the two distinct entries: "Windows" and "Ubuntu." Relief washed over Alex as he successfully dual-booted his system, a testament to the power and precision of the GRUB command line.

These are just two examples of how the GRUB command line, often seen as a mysterious entity, can be a powerful tool in the hands of those willing to learn its ways. Whether it's rescuing a failing system or configuring a dual-boot setup, GRUB holds the key to the very foundation of a computer's boot process.