From: BandiPat <magicpage91@earthlink.net>
To: GRUB 2 <grub-devel@gnu.org>
Subject: Re: Help with Grub2
Date: Sun, 01 Feb 2009 10:05:09 -0500 [thread overview]
Message-ID: <4985BA25.4080506@earthlink.net> (raw)
In-Reply-To: <498561A1.4090407@nic.fi>
Vesa Jääskeläinen wrote:
> BandiPat wrote:
>> Compiled and installed grub2. Remove LILO from MBR. Ran grub-install
>> /dev/sda. Run grub-setup /dev/sda. Ran update-grub to let it create a
>> grub.cfg file. So far, so good and checking everything, it all looks
>> great according to the instructions I have been able to find. By the
>> way, I have done a lot of researching these past 2 days! That's how I
>> came to find this mail list, but wanted to wait to finish my testing
>> before using it.
>
> you should only need to use grub-install and update-grub (or grub-mkconfig)
>
> Running grub-setup after grub-install without matching arguments given
> by grub-install to grub-setup it can create non-working setup.
>
> So commands needed are:
>
> grub-install
> update-grub (or grub-mkconfig, or manually create grub.cfg)
>
> Now if you get stuck to rescue console you probably want to start
> loading normal mode first (insmod normal.mod) and required modules
> needed for booting. I think we should write something about rescue
> console to wiki.
>
> Here is what probably happened:
>
> When you issues grub-setup manually you probably forgot to specify
> filesystems and such so grub cannot load natively from MBR your system.
>
> As grub-setup is advanced tool it should not be used manually, please
> try with only grub-install and see if it help.
> _______________________________________________
Ok, thanks for the suggestion and I do wish it had been that easy, but I
still get the grub rescue prompt only. If I try to do "insmod normal",
I get "error: out of partition".
Here is my lsmod results:
_chain 1
biodisk 1
pc 1
xfs 1
fshelp 1
That appears to be getting most of the needed modules, but again, I'm
new to this, so not sure. I only used "grub-install /dev/sda" and then
did "update-grub /dev/sda" to get my grub.cfg file. All that seems to
produce good results, no error messages. One time I did grub-install
wrong and got an error message about the core.img. I think that was
"grub-install "(hd0,2)", which give me that error, but using /dev/sda
worked as it should.
Any other info you need, I'll try to supply, but I continue to remain
baffled. :-\
Thanks,
Pat
next prev parent reply other threads:[~2009-02-01 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 4:32 Help with Grub2 BandiPat
2009-02-01 8:47 ` Vesa Jääskeläinen
2009-02-01 15:05 ` BandiPat [this message]
2009-02-01 15:23 ` Felix Zielcke
2009-02-01 16:11 ` BandiPat
2009-02-01 16:13 ` Felix Zielcke
2009-02-01 18:00 ` BandiPat
2009-02-01 18:16 ` Felix Zielcke
2009-02-01 19:09 ` BandiPat
2009-02-01 19:10 ` Felix Zielcke
2009-02-01 22:17 ` BandiPat
2009-02-02 7:26 ` Felix Zielcke
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=4985BA25.4080506@earthlink.net \
--to=magicpage91@earthlink.net \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.