Entering the grub rescue when the computer powers on

Rovidu Dhanasekara · 05-27-2018, 08:01 PM

My one is an uefi bios mode Dell laptop. I dual booted my laptop with kali linux and windows 10. The both operating systems runs smoothly. I can chose any operating from the grub. After going to windows, it says important updates install them. So I restart my laptop to update. It says in the bottom your pc may restart several times. After 75 % when it restarts it says error : file '/grub/x86_64-efi/ normal.mod ' not found.
After that it says entering rescue mode. Finally it shows grub rescue. I don't
Have a windows 10 installation cd. Please help.

frankbell · 05-27-2018, 09:21 PM

The first thing I'd try would be to boot to a Live CD of something-or-other Linux and run update-grub.

This thread from Ubuntu may help: https://askubuntu.com/questions/8481...machine/848614

Keep good notes on how that goes and, if it doesn't work, post what you did and what happened to this thread.

Oh, and welcome to LQ.

syg00 · 05-27-2018, 10:15 PM

I had similar a week or so ago.
This was a Win7 machine (EFI) that I updated to Win10. All went fine until the latest update and it trashed my Fedora dual boot. I had a Win7 recovery USB but not Win10. Also had a HP recovery USB I made when I got it.
Spent a couple of days attempting to recover Win10, but was a lost cause. I managed to get some files back, and decided to reconfigure the setup so Fedora had the entire disk with encryption.

tl;dr
I was unable to rescue Win10.

yancek · 05-28-2018, 07:44 AM

Quote:

After going to windows, it says important updates install them. So I restart my laptop to update

If you were already booted into windows, why would you need to restart? During these large windows updates, it often reboots to finish. Did you allow it to reboot on its own or make any changes on reboot, selecting from the boot menu for example. I find it unusual to say the least, that during the process of a windows upgrade it would suddenly start looking for what is obviously a Linux file? If I am reading your post correctly, your windows upgrade failed. Might have better luck finding a solution to that at a windows forum.l

colorpurple21859 · 05-28-2018, 09:28 AM

This assumes that the kali partition is still intack
at the grub-rescue prompt use

Code:

ls

to see what you have for paritions.
and then

Code:

ls (hd0,?)/

to see what is in the root of each partition, where the ? would be the number of a partition listed from the ls command. If you find the kali partition and

Code:

(hd0,?)/boot/grub/grub/x86_64-efi

exist, then enter the following

Code:

set prefix=(hd0,?)/boot/grub/x86_64-efi
set root=(hd0,?)
insmod normal
normal

once you get booted into kali then rerun grub-install
remember the ? would be the number of the partition from the ls command, the hd0 may also have to be changed accordingly if you have more than one disk.

AwesomeMachine · 05-29-2018, 05:19 PM

I think the Windows updates messed with the boot loader but didn't totally get rid of grub. When the system booted back up, it loaded grub, but the Windows update had deleted at least one grub file. So, if you boot the install disk, choose rescue, open a chroot shell in the installed root partition, and reinstall grub, everything should work again.