public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] another grub problem
Date: Sun, 06 Jul 2008 20:02:08 -0400	[thread overview]
Message-ID: <yu9fxqmmuin.fsf@nyu.edu> (raw)

The newest update of grub from 0.97-r5 to 0.97-r6 contained the 

     *** IMPORTANT NOTE: you must run grub and install
     the new version's stage1 to your MBR.  Until you do,
     stage1 and stage2 will still be the old version, but
     later stages will be the new version, which could
     cause problems such as an unbootable system.

Since this is only a change in the -r, I suspect that it is not
necessary to reinstall stage1, but I tried anyway and had trouble.
Since I thought I repeated steps that worked before, I am asking for
help/explanations.

I run grub and then the following dialog.

       GNU GRUB  version 0.97  (640K lower / 7168K upper memory)
   
    [ Minimal BASH-like line editing is supported.  For the first
      word, TAB lists possible command completions.  Anywhere else TAB
      lists the possible completions of a device/filename. ]
   
    grub> find /boot/grub/stage1
     (hd0,2)

As expected hd0 is the disk

    grub> setup (hd   <TAB>
     Possible disks are:  hd0 hd1

Again confirming that hd0 is a valid disk (as is hd1, but that is an
external scsi that does not contain stage1)

But now comes the problem.  (I want grub in the MBR.)

    grub> setup (hd0)

    Error 12: Invalid device requested

What is wrong?

I should add that I am following directions for installing grub
natively, which is supposed to be done using a "GRUB boot disk".  I
was trying it directly under gentoo, since I *think* that is what I
did last time.

I realize that the grub doc says that installing under the OS needs
grub-install.  I don't think I did this because of the somewhat
frightening

    *Caution:* This procedure is definitely less safe, because there
    are several ways in which your computer can become unbootable. For
    example, most operating systems don't tell GRUB how to map BIOS
    drives to OS devices correctly--GRUB merely "guesses" the
    mapping. This will succeed in most cases, but not
    always. Therefore, GRUB provides you with a map file called the
    "device map", which you must fix if it is wrong. *Note Device
    map::, for more details.

However, if that is everyone's recommendation I will of course try it.

(I don't have a floppy drive.  I do have a DVD+-RW, which naturally
works as a CDR.  So could use this if I could figure out how to use
xcdroast to create it).

thanks,
allan
-- 
gentoo-user@lists.gentoo.org mailing list



             reply	other threads:[~2008-07-07  0:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07  0:02 Allan Gottlieb [this message]
2008-07-07  2:15 ` [gentoo-user] Re: another grub problem Allan Gottlieb
2008-07-07 15:23   ` [gentoo-user] Re: another grub problem: SOLVED Allan Gottlieb
2008-07-07  6:47 ` [gentoo-user] another grub problem Sebastian Günther
2008-07-07  7:46 ` Neil Bothwick

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=yu9fxqmmuin.fsf@nyu.edu \
    --to=gottlieb@nyu.edu \
    --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