Ubuntu
grub package

Grub Error #17, numerous prior installations

Asked by williambunker

I have reinstalled linux numerous times on my hard disk and each time it says Grub Error 17.

I just wiped the drive again and used GNOME partition editor to change the drive from MSDOS disklabeltype to dvh. I don't know what dvh is but maybe it'll be better, and I've got some time. I would think an msdos disk would not run the ubuntu linux.

Bottoms up.

I want the reinstallation to solve this problem and for the networking portion of the computers to solve themselves. Make a tool to fix these things, or automatically configure, or to deal with error messages for users.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu grub Edit question
Assignee:
No assignee Edit question
Solved by:
marcobra (Marco Braida)
Solved:
Last query:
Last reply:
Revision history for this message
Best marcobra (Marco Braida) (marcobra) said : 		#1

GRUB error 17 usually means that GRUB cannot locate the menu file (/boot/grub/menu.lst).
The easiest way to fix this is with a live CD.

   1. Boot your Ubuntu live CD
   2. Open a terminal (applications -> accessories -> terminal)
   3. Type
          * sudo grub
   4. Type
          * find /boot/grub/stage1
   5. That should return something like (HD0) or (HD0,3). Make note of what is returned. This is the location of the GRUB files.
   6. Type
          * root (HD0,3) or whatever was returned
   7. Type
          * setup (HD0)
   8. Do not type (HD0,3) on the setup line. That will not put GRUB on the master boot record (MBR) of the drive so it will not be seen by the BIOS when booting the computer. In order for GRUB to work correctly, it has to be installed to the MBR.

If all went well, you should have GRUB properly set up now. Upon rebooting, you should see the GRUB menu. This will allow you to select which operating system to boot (assuming you have more than one). If you can see the menu but still cannot boot an OS there are likely issues with your /boot/grub/menu.lst file. We’ll look at fixing that later. However, if it’s a matter of just a bit of editing, open your terminal and type

    * sudo gedit /boot/grub/menu.lst

and make the necessary changes. Save the file and reboot.

HTH

Revision history for this message
williambunker (burritovision) said : 		#2

thank you for your help!

"need more pillaging? get it when you go to the store."

I typed the commands and restarted. I was delighted to find that it continued further, but it said:

check root = bootarg cat /proc/cmdline ... missingmodules, devices: cat /proc/modules ...

alert! /dev/disk/by-uuid/b7... [#######] does not exist. dropping to a shell!

busybox v1.1.3 [commands]

/bin/sh: can't access tty; job control turned off.

and then type help for a list of commands and the shell is available.

what does this mean, and how can i fix that too? I will repost this on the forum. this may be a two-fer.

--- On Mon, 9/1/08, marcobra <email address hidden> wrote:
From: marcobra <email address hidden>
Subject: Re: [Question #43835]: Grub Error #17, numerous prior installations
To: <email address hidden>
Date: Monday, September 1, 2008, 11:38 AM

Your question #43835 on grub in ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/grub/+question/43835

    Status: Open => Answered

marcobra proposed the following answer:
GRUB error 17 usually means that GRUB cannot locate the menu file
(/boot/grub/menu.lst).
The easiest way to fix this is with a live CD.

   1. Boot your Ubuntu live CD
   2. Open a terminal (applications -> accessories -> terminal)
   3. Type
          * sudo grub
   4. Type
          * find /boot/grub/stage1
   5. That should return something like (HD0) or (HD0,3). Make note of what is
returned. This is the location of the GRUB files.
   6. Type
          * root (HD0,3) or whatever was returned
   7. Type
          * setup (HD0)
   8. Do not type (HD0,3) on the setup line. That will not put GRUB on the
master boot record (MBR) of the drive so it will not be seen by the BIOS when
booting the computer. In order for GRUB to work correctly, it has to be
installed to the MBR.

If all went well, you should have GRUB properly set up now. Upon
rebooting, you should see the GRUB menu. This will allow you to select
which operating system to boot (assuming you have more than one). If you
can see the menu but still cannot boot an OS there are likely issues
with your /boot/grub/menu.lst file. We’ll look at fixing that later.
However, if it’s a matter of just a bit of editing, open your terminal
and type

    * sudo gedit /boot/grub/menu.lst

and make the necessary changes. Save the file and reboot.

HTH

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/ubuntu/+source/grub/+question/43835/+confirm?answer_id=0

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/ubuntu/+source/grub/+question/43835

You received this question notification because you are a direct
subscriber of the question.

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#3

Please read this solved http://ubuntuforums.org/showthread.php?t=813090 thread.

Thank you

Revision history for this message
williambunker (burritovision) said : 		#4

it appearsthat the menu file is empty when i open it. what should it be filled with? just the uuis?

--- On Mon, 9/1/08, williambunker <email address hidden> wrote:
From: williambunker <email address hidden>
Subject: Re: [Question #43835]: Grub Error #17, numerous prior installations
To: <email address hidden>
Date: Monday, September 1, 2008, 12:30 PM

Your question #43835 on grub in ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/grub/+question/43835

    Status: Answered => Open

You are still having a problem:
thank you for your help!

"need more pillaging? get it when you go to the store."

I typed the commands and restarted. I was delighted to find that it
continued further, but it said:

check root = bootarg cat /proc/cmdline ... missingmodules, devices: cat
/proc/modules ...

alert! /dev/disk/by-uuid/b7... [#######] does not exist. dropping to a
shell!

busybox v1.1.3 [commands]

/bin/sh: can't access tty; job control turned off.

and then type help for a list of commands and the shell is available.

what does this mean, and how can i fix that too? I will repost this on
the forum. this may be a two-fer.

--- On Mon, 9/1/08, marcobra <email address hidden> wrote:
From: marcobra <email address hidden>
Subject: Re: [Question #43835]: Grub Error #17, numerous prior installations
To: <email address hidden>
Date: Monday, September 1, 2008, 11:38 AM

Your question #43835 on grub in ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/grub/+question/43835

    Status: Open => Answered

marcobra proposed the following answer:
GRUB error 17 usually means that GRUB cannot locate the menu file
(/boot/grub/menu.lst).
The easiest way to fix this is with a live CD.

   1. Boot your Ubuntu live CD
   2. Open a terminal (applications -> accessories -> terminal)
   3. Type
          * sudo grub
   4. Type
          * find /boot/grub/stage1
   5. That should return something like (HD0) or (HD0,3). Make note of what is
returned. This is the location of the GRUB files.
   6. Type
          * root (HD0,3) or whatever was returned
   7. Type
          * setup (HD0)
   8. Do not type (HD0,3) on the setup line. That will not put GRUB on the
master boot record (MBR) of the drive so it will not be seen by the BIOS when
booting the computer. In order for GRUB to work correctly, it has to be
installed to the MBR.

If all went well, you should have GRUB properly set up now. Upon
rebooting, you should see the GRUB menu. This will allow you to select
which operating system to boot (assuming you have more than one). If you
can see the menu but still cannot boot an OS there are likely issues
with your /boot/grub/menu.lst file. We’ll look at fixing that later.
However, if it’s a matter of just a bit of editing, open your terminal
and type

    * sudo gedit /boot/grub/menu.lst

and make the necessary changes. Save the file and reboot.

HTH

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/ubuntu/+source/grub/+question/43835/+confirm?answer_id=0

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/ubuntu/+source/grub/+question/43835

You received this question notification because you are a direct
subscriber of the question.

You received this question notification because you are a direct
subscriber of the question.

Revision history for this message
williambunker (burritovision) said : 		#5

Thank you Mr Cobra. This has solved the problem that I was describing. A new problem took its place which Iam working on solving. I appreciate your assistance.