Originally Posted by yancek
If you changed the command above to the one below, you should see the grub directory because it is in the /boot directory.
Oh man, really?
When I couldn't find the grub directory, I wanted to do the following commands:
But when I input 'insmod normal' - I got an error message.
I can't remember the message, but are the above commands ok to get grub back from the grub rescue prompt?
The grub rescue prompt is encouraging to see.
But there appears to be no tutorials on how to use it simply to get grub working again.
Any system using Grub (Legacy or Grub2) has almost all the boot files on the partition and just a small part of the code in the MBR.
This makes sense.
But why was grub not able to boot after I deleted my failed install on sda3?
I thought grub must've transferred to sda3, and so when I cleared sda3 I had also cleared the grub bootloader.
If you use a separate /boot partition, then the majority of the Grub files are there so it does this as part of the installation of the bootloader. This is with MBR BIOS setups.
I don't have a seperate boot partition yet. I also have BIOS.
With grub now re-installed, I can access all my partitions.
But the grub page has now changed.
It's saying Win7 is now sda1. But it is actually sdb1.
A simple 'lsblk' on the terminal shows that all my partitions are unchanged and correct.
How can I get grub to refer to the partitions by their correct names on the bootloader page?
I ran os-prober and then did 'update-grub' but it hasn't worked.
Also come to think of it, there are a bunch of 'memtest' options and now a 'multiboot' option.
I don't know what they mean and why they're there.
Sorry for all the questions.