Link to home
Start Free TrialLog in
Avatar of David
DavidFlag for United States of America

asked on

Linux Grub and Grub2 interaction

I've had several Linux distro's installed on my computer for several months now, and I'm now installing Arch, and the problem i've run in to previously is that it seems with each new installation, the installation program write it's own boot commands on it's own partition?  does this sound right?  and I've had luck in the past with update-grub2 recognizing them and somehow compiling them all and putting them into what I see every time i boot my system --which i'm perfectly satisfied with --despite knowing it's not perfect (i'm still very new to linux)

So, today I installed--or attempted to install Arch Linux onto a new partition.  and i believe it overwrote the MBR or the GPT table... not quite sure which one I used a couple months ago.

and, now all I get its a

error: no such device: 5#@%@#%@#% --some number
Entering rescue mde...
grub rescue

I've found some documentation and i type in the following commands:

grub rescue> set prefix=(hd0,1)/boot/grub
grub rescue> set root=(hd0,1)
grub rescue> insmod normal
grub rescue> normal
grub rescue> insmod linux
grub rescue> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1
grub rescue> initrd /boot/initrd.img-3.13.0-29-generic
grub rescue> boot

and it brings me back to my usual boot loader (in fact, all i have to type are the first  4 lines)

at which point the first thing I do is log in to my Linux, and 'sudo update-grub2', which finds most of my linux distributions, but when I reboot it now goes back to the

grub rescue prompt


please help... did i overwrite grub2 with grub1?

-dj
Avatar of Dr. Klahn
Dr. Klahn

did i overwrite grub2 with grub1?

Probably not.  It's an annoying little "detail" that grub2 prompts with grub, which imo it certainly should not - looking at that does not indicate which grub is in use.

I think what may have happened here is that (a) no grub repair was done once the system was up and running, and (b) no "update-grub" was done after that.  So while it boots once, the corrupt configuration is still on disk.

You also might want to look at the page below, which has an enormous amount of useful information on troubleshooting grub2 problems.

https://help.ubuntu.com/community/Grub2/Troubleshooting
ASKER CERTIFIED SOLUTION
Avatar of noci
noci

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.