Grub2 made my systeum unbootable



Rashly, after today's upgrade I followed the exhortation in the grub
legacy package to move to grub2. I now cannot boot at all; I just get
the message "Grub" and nothing more.

Looking at /boot/grub with my rescue disk I see all sorts of files I
don't recognize but no menu.lst.

Is there any way to restore things? Please don't tell me I have to
reinstall!

Anthony

--
Anthony Campbell - ac@xxxxxxxxxxxxxxxx
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk (blog, book reviews,
and sceptical articles)


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx



Relevant Pages

  • Re: Thinkpad T60P: bricked by grub transition
    ... no access to the broken system (since it wouldn't boot) to provide the kind ... |>> Upon a recent routine upgrade, ... |>> thought that I should try grub2 as I was encouraged to do. ... No menu and no grub command-line prompt. ...
    (Debian-User)
  • Re: GRUB problem after upgrading to 10.04
    ... I am using 9.04 even after installing 10.04 - I tried both alternate and ... desktop installs and got same grub2 problems, ... Now I can only get 9.04 to boot and see no boot menu any longer. ... So I am forced to use 9.04, and it seems as I am using grub as bootloader. ...
    (Ubuntu)
  • Re: GRUB problem after upgrading to 10.04
    ... desktop installs and got same grub2 problems, ... Now I can only get 9.04 to boot and see no boot menu any longer. ... So I am forced to use 9.04, and it seems as I am using grub as bootloader. ...
    (Ubuntu)
  • Re: GRUB failure
    ... me to the GRUB prompt, ... I cannot boot the computer into any operating system. ... subject of "unsubscribe". ... Trouble? ...
    (Debian-User)
  • Re: Error rebooting after upgrade from 2.6.12-i36 to 2.6.15-i686
    ... and a busybox shell appears. ... Have the latest grub in unstable. ... Boot into 2.6.12 kernel and then do this: ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)