public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Grub broke out of the blue
Date: Tue, 17 Feb 2009 06:49:56 +0200	[thread overview]
Message-ID: <gndflj$h6j$1@ger.gmane.org> (raw)
In-Reply-To: <gnddo3$doq$1@ger.gmane.org>

Nikos Chantziaras wrote:
> I've no idea how it broke, but after an emerge --sync, a kernel 
> (gentoo-sources) update was there.  After I compiled the kernel, I did 
> the usual "make modules_install && make install".  I edited grub.conf 
> only to the point of changing the booted kernel to the new one (just a 
> matter of changing -r1 to -r2 at the end of the kernel filename).  I 
> reboot, Grub stops working.  It just displays "GRUB" and hangs there.
> 
> What might have cause this?  /boot is a 50MB ext3 partition with 14MB 
> free.  I had to boot from a live CD and make sda1 bootable (Windows XP) 
> so I can get online and burn a repair CD that supports ext4 (/).

Back.  Grub was booting inside a VM under XP even though it refused to 
boot for "real".  So I booted in a VM and reinstalled Grub from there. 
I'm left to wonder now how copying a new kernel into /boot with "make 
install" can possibly make Grub go fubar...




  parent reply	other threads:[~2009-02-17  4:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17  4:17 [gentoo-user] Grub broke out of the blue Nikos Chantziaras
2009-02-17  4:44 ` Stroller
2009-02-17  4:51   ` [gentoo-user] " Nikos Chantziaras
2009-02-17  5:01     ` Stroller
2009-02-17 17:30   ` [gentoo-user] " Dirk Heinrichs
2009-02-17  4:49 ` Nikos Chantziaras [this message]
2009-02-17  8:08 ` Neil Bothwick
2009-02-17 17:21   ` [gentoo-user] " Nikos Chantziaras
2009-02-19  8:21     ` Mick
2009-02-17  8:18 ` [gentoo-user] " Roy Wright

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gndflj$h6j$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox