"GRUB_" Ubuntu Boot Error

[geeksquad1516]

I reinstalled Ubuntu on a primary partition. This is how my HD looks now:
-45 GB Primary NTFS (Windows 7 RC)
-230 GB Primary NTFS (Windows XP)
-45 GB Extended
-41 GB Logical EXT3 (Ubuntu 9.04 /)
-4 GB Logical SWAP

When I select Ubuntu in the Windows Boot Manager, it still takes me to a black screen with "GRUB _" in the upper left corner.

I tried to add it to the Boot Manager using EasyBCD with the "GRUB isn't installed to MBR" box check, but that just flashed a screen at me and led me to a prompt.

BTW, when I tried to install GRUB right to the HD, I got an "Error 18" on "Stage1.5"

Hope this helps!

 

[asilkey]

Vista REcovery HELP!

Help! I"m trying to download the 64 bit vista recovery to burn and try to restore my corrupted PC. However the computer I am on uses XP and for some reason won't let me get past the inital stage. It downloaded the disc.iso file but then it just directs me to save the iso.torrent file but when i try to open it just directs me to a page saying I don't have a program to open and download it. I did it no problem on my MAC to find out my mac doesn't have a CD burner. How do I make this PC download this program so I can save my other pC? HELP! thank you

 

[Coolname007]

I reinstalled Ubuntu on a primary partition. This is how my HD looks now:
-45 GB Primary NTFS (Windows 7 RC)
-230 GB Primary NTFS (Windows XP)
-45 GB Extended
-41 GB Logical EXT3 (Ubuntu 9.04 /)
-4 GB Logical SWAP

Sure looks like Ubuntu is still installed to a logical (not primary) partition...:brows:
Anyway, try build 61 of EasyBCD 2.0 Beta, and use it to re-add the Linux partition. Since Ubuntu is still on the same HDD as Windows, don't check the "Grub is not installed to the MBR/bootsector" box under the Linux tab in the Add/Remove Entries section of EasyBCD. Just make sure to point it at the correct drive and partition Ubuntu is installed to under the "Device" drop-down menu.

Jake

Addendum:

Help! I"m trying to download the 64 bit vista recovery to burn and try to restore my corrupted PC. However the computer I am on uses XP and for some reason won't let me get past the inital stage. It downloaded the disc.iso file but then it just directs me to save the iso.torrent file but when i try to open it just directs me to a page saying I don't have a program to open and download it. I did it no problem on my MAC to find out my mac doesn't have a CD burner. How do I make this PC download this program so I can save my other pC? HELP! thank you

Hello, asilkey, welcome to NST.
Generally, it is a good idea to start your own thread on the issue, rather than posting in someone else's thread, if its not related...
You will need a Bittorrent client (such as uTorrent) in order to download the actual .iso file via the torrent. Once you install one, you simply "add" the file, and tell it to start downloading the file.
The reason you were able to do it on your Mac without having to go through this is because OS X has a built-in torrent client, I think.

 

[geeksquad1516]

Sorry, I copied that from my first post and forgot to edit it.

It should read:
-45 GB Primary NTFS (Windows 7 RC)
-230 GB Primary NTFS (Windows XP)
-41 GB Primary EXT3 (Ubuntu 9.04 /)
-4 GB Primary SWAP

I have build 60, so I'll try 61.

Do you think that my problem now is related to the "Error 18" that pops up when I install GRUB straight to the hard drive (the default option)?

Thanks!

Addendum:

There must be a difference with Build 61, because my entry created in Build 60 reads:

Entry #3
Name: Ubuntu 9.04
BCD ID: {0d819f0d-3b83-11de-b13e-9061df42a40f}
Drive: D:\
Bootloader Path: \NST\nst_linux.mbr

And the one created by Build 61 reads:

Entry #4
Name: Ubuntu 9.04 Build 61
BCD ID: {0d819f0f-3b83-11de-b13e-9061df42a40f}
Drive: D:\
Bootloader Path: \NST\nst_linux-0A494EFAFAC8CC13902E04153B53F13F.mbr

Wish me luck on my maiden reboot!

 

[Coolname007]

Do you think that my problem now is related to the "Error 18" that pops up when I install GRUB straight to the hard drive (the default option)?

Which method did you use to (attempt to) install Grub? The installer when you were installing Ubuntu the second time, or via the command line from the LiveCD?
And what do you mean when you say "when I install Grub straight to the hard drive"? Do you mean to the MBR instead of the bootsector of the Linux partition?

 

[geeksquad1516]

I tried to reboot after reentering the entry with Build 61 and got the same result.

I installed GRUB at the last step of Ubuntu's graphical installer (7 of 7). I chose "Advanced" and told it to install GRUB to the partition that it was going to install Ubuntu to.

When I say"Install GRUB straight to the HD" I mean the MBR. When I install GRUB to the MBR (which is the default during the Ubuntu installation) I get "Error 18" during "Stage1.5"

 

[Coolname007]

I tried to reboot after reentering the entry with Build 61 and got the same result.

I installed GRUB at the last step of Ubuntu's graphical installer (7 of 7). I chose "Advanced" and told it to install GRUB to the partition that it was going to install Ubuntu to.

This was the first time you installed Ubuntu that you installed it to the partition instead of the MBR?

When I say"Install GRUB straight to the HD" I mean the MBR. When I install GRUB to the MBR (which is the default during the Ubuntu installation) I get "Error 18" during "Stage1.5"

You had it right the first time. Installing Grub to the MBR on the same HDD as Windows means it will overwrite the Windows MBR, meaning you will get the Grub menu first when you multiboot, not the Win 7 menu. So you should definitely install Grub to the Ubuntu partition if you want the Windows bootloader to retain control of the boot.
So does that mean you did not install Grub at all the second time you installed Ubuntu?

 

[geeksquad1516]

Here is the order of my three installs:
1. I installed Ubuntu on a logical partition and installed GRUB to the MBR. When I tried to boot, I got "Error 18" on "Stage1.5." I then ran my XP Install Disc in Recovery Console and executed "fixmbr" and "fixboot" to clear out the MBR. THIS ALL HAPPENNED BEFORE I STARTED THIS THREAD.

2. I installed Ubuntu on the same logical partition, but I chose to install GRUB to the partition that I was installing Ubuntu to. I followed the tutorial on this webites Wiki, and I got the "Grub _" after I chose the Ubuntu option in my Windows Boot Manager.

3. I did the same as #2, but I installed Ubuntu to a primary partition, with the same results.

I hope this clears some stuff up.

Addendum:

I really don't care if in the end I use Windows Boot Manager to link to GRUB or use just GRUB on the MBR. I just want to be able to boot into Ubuntu (which I have yet to do).

 

[Coolname007]

Here is the order of my three installs:
1. I installed Ubuntu on a logical partition and installed GRUB to the MBR. When I tried to boot, I got "Error 18" on "Stage1.5." I then ran my XP Install Disc in Recovery Console and executed "fixmbr" and "fixboot" to clear out the MBR. THIS ALL HAPPENNED BEFORE I STARTED THIS THREAD.

2. I installed Ubuntu on the same logical partition, but I chose to install GRUB to the partition that I was installing Ubuntu to. I followed the tutorial on this webites Wiki, and I got the "Grub _" after I chose the Ubuntu option in my Windows Boot Manager.

3. I did the same as #2, but I installed Ubuntu to a primary partition, with the same results.

I hope this clears some stuff up.

Yes, indeed it does...
But, when you were re-adding the Linux entry with build 61, did you remember to not check the box that says "Grub is not installed to the MBR/bootsector" under the Linux tab in the Add/Remove Entries section of EasyBCD?
Only other thing that I can think of right now that should work is to configure NeoGrub manually if you did indeed not check the "Grub is not installed..." box.

Addendum:

I really don't care if in the end I use Windows Boot Manager to link to GRUB or use just GRUB on the MBR. I just want to be able to boot into Ubuntu (which I have yet to do).

Good! Grub is much easier to setup in the long run (sometimes) than the Windows boot loader. At least the stuff is usually consistent, and works as long as the entries are pointed at the right place. (BTW, stupid question, but did you make sure to point your Linux entry in EasyBCD at the correct drive and partition Ubuntu is installed to under the "Device" drop-down menu under the Linux tab?)
If you're willing to post your new Ubuntu's menu.lst contents (which you access with a LiveCD), along with the output of the "sudo fdisk -l" command (without the quotes--the last letter is a lowercase "L") run from Applications>Accessories>Terminal in the Live session, I can help you configure it correctly, and install Grub to the MBR.

 

[geeksquad1516]

I am sure that I DID NOT check the box, and I am sure that I chose the right HD (it was the only 41 GB one).

I'll try those steps ASAP.

Addendum:

The menu.lst of my Ubuntu installation reads:

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=cb17c562-ec35-4105-af0e-fa0f52d25f13 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=cb17c562-ec35-4105-af0e-fa0f52d25f13

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
## indomU=true
## indomU=false
# indomU=detect

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid cb17c562-ec35-4105-af0e-fa0f52d25f13
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=cb17c562-ec35-4105-af0e-fa0f52d25f13 ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

title Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid cb17c562-ec35-4105-af0e-fa0f52d25f13
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=cb17c562-ec35-4105-af0e-fa0f52d25f13 ro single
initrd /boot/initrd.img-2.6.28-11-generic

title Ubuntu 9.04, memtest86+
uuid cb17c562-ec35-4105-af0e-fa0f52d25f13
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Windows Vista (loader)
rootnoverify (hd0,0)
savedefault
chainloader +1


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda2
title Microsoft Windows XP Professional
rootnoverify (hd0,1)
savedefault
chainloader +1

And the "sudo fdisk -l" command shoots out the following:

ubuntu@ubuntu:~$ sudo fdisk -l



Disk /dev/sda: 320.0 GB, 320072933376 bytes

255 heads, 63 sectors/track, 38913 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk identifier: 0x000645d6



Device Boot Start End Blocks Id System

/dev/sda1 * 1 5874 47182873+ 7 HPFS/NTFS

/dev/sda2 5875 33039 218202862+ 7 HPFS/NTFS

/dev/sda3 33040 38391 42989940 83 Linux

/dev/sda4 38392 38913 4192965 82 Linux swap / Solaris

 

[Coolname007]

Ok, so do this...
Boot from the LiveCD, get to the desktop, open up the Terminal, and run the following commands:

sudo grub
root (hd0,2)
setup (hd0)
quit
exit

That should install Grub to the MBR, and allow you to access the Grub menu first at startup. Then you will need to test the entries to make sure they all work, as they should.
Post back with the results.

Cheers.

Jake

 

[geeksquad1516]

I'll try it, but last time I installed GRUB to the MBR, I got "Error 18" on "Stage1.5"

I'll try it though...

Addendum:

Oh joy, a different error! Well, at least its not the same one.

The boot screen says:

GRUB loading stage1.5


GRUB loading, please wait . . .
Error 17

 

[JustinW]

Error 17 means the entry in menu.lst isnt pointing to the correct location. You probably need to adjust x in "root (hdx,y) of the entry until you find the correct disk and maybe y if its reading the partition order differently.

 

[geeksquad1516]

Well, this is what I got earlier:

ubuntu@ubuntu:~$ sudo fdisk -l



Disk /dev/sda: 320.0 GB, 320072933376 bytes

255 heads, 63 sectors/track, 38913 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk identifier: 0x000645d6



Device Boot Start End Blocks Id System

/dev/sda1 * 1 5874 47182873+ 7 HPFS/NTFS

/dev/sda2 5875 33039 218202862+ 7 HPFS/NTFS

/dev/sda3 33040 38391 42989940 83 Linux

/dev/sda4 38392 38913 4192965 82 Linux swap / Solaris

What should my "y" be? I only have one HD.

 

[Coolname007]

It should be

root (hd0,2)

for Ubuntu.
I would have suggested that earlier of course, but I was thinking the UUID lines should have worked for Ubuntu. Do you get this error when attempting to boot into Ubuntu or at a different stage?

 

[geeksquad1516]

I get this error first thing when I start up.

 

[Coolname007]

Ok, sorry. I forgot one small detail...
You will need to set the Ubuntu partition as the "boot" (active) partition with Gparted, then it should work.

 

[geeksquad1516]

I can do that

Addendum:

Still get the same error. If GRUB is getting an error, would changing the boot partition do anything anyways?

Now I have Grub installed on the partition with Ubuntu, GRUB on the MBR, and the Ubuntu partition set as active (boot). What else is there to try?

 

[Coolname007]

Ok, time to re-post what I already wrote, but later edited, and replaced with what's currently in my last post...:brows:
The way I see it, you have two options now:

One, to use Grub without the stage 1.5 file (which is possible only if the boot partition for Linux is not above the 1024 cylinder threshold...roughly 8GBs, which unfortunately, your Ubuntu partition is well beyond that because it is the third partition on the disk). If you choose this method, you will need to either reinstall Ubuntu, or delete your first partition, and create a new one (it only needs to be big enough to store Grub), formatting it as ext3, copy the "boot" folder over into that partition, set it to "active", and use it as your boot partition. Probably not something you want to do...
The other option is actually only a possibilty, because I don't know if its true or not. But, reading this link, I found mention of the possible cause of why your stage 1.5 file is failing you. This file is stored at sectors 2 to about 16 (the first partition starts at sector 63, the MBR is the first sector), and exists between your MBR and first partition, on the disk. After reading that link, I came across information that may explain your problem. According to "MPH", there are at least two Highpoint ATA controllers, the Y2K era HPT366 chip and the RocketRAID 152x SATA Host Adapter, which write on the first track of a hard drive just like GRUB stage 1.5 does. The latter controller’s manual (http://www.highpoint-tech.com/PDF/RR1522a/RR152x_User_Manual.pdf) states, “For SuSE 10.x, please format the /boot partition using ext3 format (default is reiserfs). Otherwise, the GRUB boot loader will overwrite the RAID information stored on sector 9 and cause your RAID array to be broken”.
If that is the truth, it means data is being written by your harddrive controller in the same place that stage 1.5 is stored, meaning it is getting corrupted. Now what MPH did in the scenario, is he moved the stage 1_5 file out of the /boot/grub folder, and in a different location (in case he needed it later on), and reinstalled Grub to the MBR, which he said allowed him to boot.
But, there may be some way to stop your hard drive controller from writing to that location on the disk, but that it is a very slim possibilty at best.

Not a whole lot else for you in terms of options, that I see...

Jake

 

[geeksquad1516]

I have a spare HD (not in my laptop right now), so I could test that boot partition thing.

Addendum:

If I wanted to install Ubuntu using that first method on its own HD, how would I go along doing that?