GRUB Hard disk error

Can you copy and paste here:
sudo fdisk -l
and
sudo gedit /boot/grub/menu.lst

Thank you

sudo fdisk -1

Disk /dev/sda: 36.4 GB, 36401479680 bytes
255 heads, 63 sectors/track, 4425 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 4238 34041703+ 83 Linux
/dev/sda2 4239 4425 1502077+ 5 Extended
/dev/sda5 4239 4425 1502046 82 Linux swap / Solaris

sudo gedit /boot/grub/menu.lst

# 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 change this entry to 'saved' 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 3

## 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=369c0e1c-bba1-4ac6-85de-73cc61fc8398 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## 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

## 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

## ## End Default Options ##

title Ubuntu, kernel 2.6.20-15-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=369c0e1c-bba1-4ac6-85de-73cc61fc8398 ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=369c0e1c-bba1-4ac6-85de-73cc61fc8398 ro single
initrd /boot/initrd.img-2.6.20-15-generic

title Ubuntu, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

It seems good do you have some bios boot antivirus protection active...?
If yes disable it.

I have similar problem with sda identified hard disk i ha solved it by reinstalling grub with the below steps:

Boot from Ubuntu live cd try to reinstall GRUB by opening a terminal and typing:

You type: sudo grub
System answer: grub>

You type: find /boot/grub/stage1
System answer: (hdx,y) <-- here you values

You type: root (hdx,y) <-- change the hdx,y values

You type: setup (hdx) <-- change the hdx value

Then exit and reboot the system without live cd.

HTH

Grub manual says this:

"Hard Disk Error
    The stage2 or stage1.5 is being read from a hard disk, and the attempt to determine the size and geometry of the hard disk failed. "

Some bios settings can be wrong, or the bios may just be old or buggy. There are some reports of solving this with a bios upgrade, but your set up looks rather new, what about the motherboard and bios version?

I have no AV running, unless Ubuntu comes with AV already running.

I have already tried these steps before. But will do again.
Here is the output:
grub> find /boot/grub/stage1
 (hd0,0)

grub> root(hd0,0)

Error 27: Unrecognized command

grub> root (hd0,0)

grub> setup (hd0)
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/e2fs_stage1_5" exists... yes
 Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded.
succeeded
 Running "install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,0)/boot/grub/stage2
/boot/grub/menu.lst"... succeeded
Done.

Exit and reboot. That did not work.

Do you have any other suggestions? I really appreciate the help.

I don't mean Antivirus when i say bios antivirus protection but i mean a bios option that protect boot sector from writing. Look for it into your bios setting and disable it if it is on.

Regards

Antivirus protection in bios could interfere writing master boot record (rather not because this grub update suceeds)

You can enter bios setup by pressing F1, F2, or delete (or something other but it should be printed) just after the computer starts. Things there are rather advanced, so don't go lightly changing everything. You should have a manual explaining all these options.

I looked around in the bios and noticed the AV. It was already disabled. The BIOS said CMOS Setup Utility Award Software. The date was 07/15/2003. I also saw there is bios for SCSI. Adaptec SCSI BIOS V3.10 that had a date of 2001. So, I guess these are kind of old.

As more back reference I bought this PC used. When I got it, Fedora Core (6 I think) was installed. I tried to install Ubuntu over Fedora as the only OS. I heard Ubuntu is better :)

Can you copy and paste:
cat /boot/grub/device.map
here.
Thank you.

This is what got.

(hd0) /dev/sda

Thanks,
Skyler

FYI -- I noticed that when I boot from the live cd, using the 'boot from first hard disk' option Grub pops up very briefly and then the OS loads. Does this mean the problem is in the BIOS? If so what are updates/settings changes I could perform?

I'm trying to understand my problem a little bit better, and help drive out a solution. What is the purpose of the GRUB? From reading it seems it's used for multi-boot situations. So if I'm only booting one OS why do I need it?

Would there be a work around or another solution besides using Grub. Would it be possible to remove GRUB and install LILO if so, how?

The problem can be with bios, but it's really hard to tell. You could update your bios, but it's a procedure you want to take as rarely as possible -- this means electronically updating firmware on the motherboard.

Check your motherboard or bios manufacturer for a flash utility and newer bios image. If you can provide me some bios numbers i might be able to check for you if there are updates that would fix something like that.

Adaptec support: http://www.adaptec.com/en-US/support/
Award bios can come from different manufacturers, so more details are needed to identify it.

In any case you need some bootloader, windows also has one, some basic explanation of the boot process can be found here:
https://wiki.ubuntu.com/Booting

You could replace grub with any other bootloader, but you would probably have to figure out yourself how to configure it, and this can be not so easy. Some other boot loaders may not work too.

You could use anything like a floppy or usb stick for booting (as far as your bios would allow this :).

Is there possibly a problem with Ubuntu and SCSI drives? or with my particular configuration of SCSI drives? Any documentation on Ubuntu and SCSI drives?

Thanks for all the help. I honestly, really appreciate it.

It is a problem with grub/bios, but changing some settings of the drive in bios could help. I don't think there's any special documentation on ubuntu & scsi or grub & scsi -- in most cases it just works. Maybe you could try using older ubuntu, older grub.

I would try to:
- try to change some settings of the drive in bios, experiment a bit with those settings (make sure your disk works in lba mode for example)
- reinstall grub (see chapter 16 in http://www.gnu.org/software/grub/manual/grub.html), maybe using the force lba option
- update bios or live with starting from cd :)

I've looked through the bugs and there are some similar but nothing exactly like that, i guess you can report it if you wish. But before that could you give those bios numbers and probably drive name/model?

I came up with a solution/hack to fix this problem. When my computer loaded I pressed Ctrl A to load the SCSI bios. I then changed the SCSI device controller from 7 to 0. I don't think this is really a fix as device 0 is my hard drive, but it is a work around. I think now I would have problems if I tried to add another hard drive. Basically, I don't know if that would be recognized. Does this work around identify what the problem was, and is there a more long term fix? Any ideas?

What the former option (controller 7) meant? If you could provide me with some link to a manual to your drive, or it's model it would be much easier to tell anything. I don't really know those scsi bioses by heart ;)

The former option, 7, was the SCSI id of the SCSI controller. Have changed that to 0 which is also the SCSI id of my boot disk and my first hard drive. I have no idea how or why it works.

My hard drive is IBM ESXS ST33660SLU. I have an Adaptec SCSI controller, don't know the model number.

Here is a link for the system bios from Award Software
www.phoenix.com/NR/rdonlyres/7F44FBD3-A0C2-4E50-BD40-3232D4F9F322/0/biosaward82440bx.pdf

Not sure if this is for the specific SCSI controller I have, but the part about called 'Configuring with SCSI Select' is correct as to what the SCSI bios looks like.
http://support.gateway.com/support/manlib/cmponts/control/8502749/

Mostly just adding this stuff so if anyone ever comes across this problem they'll have an idea where to look. I don't know if there is a solution to this problem.

I found the model number for the SCSI controller it is AIC 7899W

Have you check if your bios have some option to boot from scsi if it don't have try to remove any defined old or recognized by bios hard disk. Then try to boot.
HTH

Have you a real SCSI attached hard-disk or your disk is a sata disk normally recognized by system as sda as SCSI if you dont have a real SCSI disk i suggest to remove SCSI card from the system and try to boot.

HTH

For bios updates, would that be suitable for your system?:
http://www-304.ibm.com/jct01004c/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-39663&brandind=5000004
I'm not sure, it's probably best to check by some parts' numbers. Anyway nothing in the change log that looks like it would help with your problem.

For the scsi bios it's worse, can't find anything at all, maybe you'll have more luck. Adaptec's support: http://www.adaptec.com/en-US/support/, i haven't found anything there. But maybe the controller comes from a different manufacturer, gateway has something like this, but without any updates too: http://support.gateway.com/s/Servers/COMPO/MOTHERBD/4000791/4000791mvr31.shtml.