grub stage 1.5 error 15

[darkod]

OK, time for the heavy artillery. Something is messed up with your install. Boot with the LiveCD again. Download the script in my signature, move it on desktop for example, and execute it with:
sudo bash ~/Desktop/boot_info_script*.sh

It will create results.txt file with your whole boot process. Copy the content here and wrap it in CODE tags for easier reading (with the text selected hit the # button in the toolbar above).

[idom]

Hi I do not know how to do it in Code tags

And I have another problem Live ubuntu CD is a friends and his ubuntu has crashed to he needs the CD
I will reboot after this with 9.04 live Cd instead of 9.1 cd

Thanks again

ubuntu@ubuntu:~$ cp /home/ubuntu/Downloads/boot_info_script041.sh /home/ubuntu/Desktop/
ubuntu@ubuntu:~$ sudo bash ~/Desktop/boot_info_script*.sh
Identifying MBRs...
Computing Partition Table of /dev/sda...
Searching sda1 for information...
Searching sda2 for information...
Searching sda3 for information...
Searching sda4 for information...
Searching sda5 for information...
Searching sda6 for information...
Finished. The results are in the file RESULTS.txt located in /home/ubuntu/Desktop
ubuntu@ubuntu:~$ more /home/ubuntu/Desktop/RESULTS.txt
============================= Boot Info Summary: ==============================

=> Grub 1.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #1 for /boot/grub.

sda1: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 9.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda2: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:

sda3: __________________________________________________ _______________________

File system: vfat
Boot sector type: -
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs:

sda4: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:

sda6: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ _________________________________________________
____

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00094ad6

Partition Boot Start End Size Id System

/dev/sda1 63 80,084,024 80,083,962 83 Linux
/dev/sda2 80,084,025 156,248,189 76,164,165 83 Linux
/dev/sda3 156,248,190 195,318,269 39,070,080 b W95 FAT32
/dev/sda4 195,318,270 312,576,704 117,258,435 5 Extended
/dev/sda5 195,318,333 306,648,719 111,330,387 83 Linux
/dev/sda6 306,648,783 312,576,704 5,927,922 82 Linux swap / Solar
is


blkid -c /dev/null: __________________________________________________ __________

/dev/loop0: TYPE="squashfs"
/dev/sda1: UUID="1c500e30-2f7c-4cf3-8ba8-7c1043d59bcd" TYPE="ext4"
/dev/sda2: UUID="5b971240-6b6f-4308-9b76-45573d027c18" TYPE="ext4"
/dev/sda3: UUID="D0EC-E24E" TYPE="vfat"
/dev/sda5: UUID="ca234d80-afc9-4490-9f7a-dc0ccf3234f2" TYPE="ext4"
/dev/sda6: UUID="6fb6becc-cafd-46d0-ab37-2e76d08e6c87" TYPE="swap"

=============================== "mount" output: ===============================

aufs on / type aufs (rw)
none on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
/dev/sr0 on /cdrom type iso9660 (rw)
/dev/loop0 on /rofs type squashfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev
)
gvfs-fuse-daemon on /home/ubuntu/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nod
ev,user=ubuntu)


=========================== sda1/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 1c500e30-2f7c-4cf3-8ba8-7c1043d59bcd
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ ${timeout} != -1 ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

=============================== sda1/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=1c500e30-2f7c-4cf3-8ba8-7c1043d59bcd / ext4 errors=remount
-ro 0 1
# /data was on /dev/sda5 during installation
UUID=ca234d80-afc9-4490-9f7a-dc0ccf3234f2 /data ext4 defaults
0 2
# /proj was on /dev/sda2 during installation
UUID=5b971240-6b6f-4308-9b76-45573d027c18 /proj ext4 defaults
0 2
# /win was on /dev/sda3 during installation
UUID=D0EC-E24E /win vfat utf8,umask=007,gid=46 0 1
# swap was on /dev/sda6 during installation
UUID=6fb6becc-cafd-46d0-ab37-2e76d08e6c87 none swap sw
0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

=================== sda1: Location of files loaded by Grub: ===================


.0GB: boot/grub/grub.cfg

OK, time for the heavy artillery. Something is messed up with your install. Boot with the LiveCD again. Download the script in my signature, move it on desktop for example, and execute it with:
sudo bash ~/Desktop/boot_info_script*.sh

It will create results.txt file with your whole boot process. Copy the content here and wrap it in CODE tags for easier reading (with the text selected hit the # button in the toolbar above).

[darkod]

I'm getting out of ideas. It looks normal. Grub2 is now installed on the MBR but it doesn't seem to "see" your Ubuntu on /dev/sda1. That's why only memtest is reported when doing update-grub and when you boot memtest starts automatically.
I really don't know what could be wrong with this. Sorry.

[presence1960]

I'm getting out of ideas. It looks normal. Grub2 is now installed on the MBR but it doesn't seem to "see" your Ubuntu on /dev/sda1. That's why only memtest is reported when doing update-grub and when you boot memtest starts automatically.
I really don't know what could be wrong with this. Sorry.

Darko, his grub.cfg has no linux entries. I can't help right now as we are having a major snowstorm and have to dig my car out and shovel my home front.

[oldfred]

Something is wrong with the install as the last entry shows no boot files.

This is his:

.0GB: boot/grub/grub.cfg

There does not seem to be any boot files???

This is mine ( from a week or two ago):
107.7GB: boot/grub/grub.cfg
107.3GB: boot/initrd.img-2.6.31-14-generic
107.6GB: boot/initrd.img-2.6.31-15-generic
107.4GB: boot/vmlinuz-2.6.31-14-generic
107.2GB: boot/vmlinuz-2.6.31-15-generic
107.6GB: initrd.img
107.3GB: initrd.img.old
107.2GB: vmlinuz
107.4GB: vmlinuz.old

Can you check from the liveCD and see if /boot has any vmlinuz or initrd.img files?

[darkod]

My point exactly. I noticed there are no linux entries in the grub/cfg but that's because update-grub doesn't find them. As far as I know the OP doesn't have separate /boot partition.
I don't know ubuntu enough to figure this out. I guess reinstall would be the next step.

[idom]

even I was thinking that there must be something wrong with the initrdfile as my installation in the first place did not go through
completely.

..
ubuntu@ubuntu:~$ ls -alrt /media/1c500e30-2f7c-4cf3-8ba8-7c1043d59bcd/boot/
total 2500
-rw-r--r-- 1 root root 1664737 2009-10-16 18:03 System.map-2.6.31-14-generic
-rw-r--r-- 1 root root 111371 2009-10-16 18:03 config-2.6.31-14-generic
-rw-r--r-- 1 root root 629174 2009-10-16 18:03 abi-2.6.31-14-generic
-rw-r--r-- 1 root root 1196 2009-10-16 18:06 vmcoreinfo-2.6.31-14-generic
-rw-r--r-- 1 root root 128796 2009-10-23 16:11 memtest86+.bin
drwxr-xr-x 24 root root 4096 2009-12-18 19:50 ..
drwxr-xr-x 3 root root 4096 2009-12-18 19:50 .
drwxr-xr-x 2 root root 4096 2009-12-19 15:47 grub


so what choice do I have now ?

Something is wrong with the install as the last entry shows no boot files.

This is his:

.0GB: boot/grub/grub.cfg

There does not seem to be any boot files???

This is mine ( from a week or two ago):
107.7GB: boot/grub/grub.cfg
107.3GB: boot/initrd.img-2.6.31-14-generic
107.6GB: boot/initrd.img-2.6.31-15-generic
107.4GB: boot/vmlinuz-2.6.31-14-generic
107.2GB: boot/vmlinuz-2.6.31-15-generic
107.6GB: initrd.img
107.3GB: initrd.img.old
107.2GB: vmlinuz
107.4GB: vmlinuz.old

Can you check from the liveCD and see if /boot has any vmlinuz or initrd.img files?

[oldfred]

Boot files are rather important. I do not know if you can chroot into your system and do a full update and it will install them or if you just have to do a total reinstall?

I would try the chroot which is similar to Darko's except I add commands for internet connection:

sudo mount /dev/sda1 /mnt
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo cp /etc/resolv.conf /mnt/etc/resolv.conf #(may or may not be necessary to establish an internet connection)
sudo chroot /mnt
#Then run whatever commands needed - no sudo needed (maybe good to run "df- H" and "cat /etc/issue" to be certain you mounted the correct partition).
apt-get update
apt-get upgrade
#When done:
exit
sudo umount /mnt/dev
sudo umount /mnt/proc
sudo umount /mnt

update: Also run the update-grub while chrooted.

[idom]

apt-get update gives following error

root@ubuntu:/# apt-get update
E: Could not open lock file /var/lib/apt/lists/lock - open (2: No such file or directory)
E: Unable to lock the list directory
root@ubuntu:/# apt-get upgrade
E: Could not open lock file /var/lib/dpkg/lock - open (2: No such file or directory)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

I am rather hesitant for the full install because last night I had tried full install twice and both time it got stuck at some point ( laptop was hung so I do not know what is point at which it got stuck, laptop was in the same state for some 4 hours and after that I did poweroff )
I did disc checking and it was ok so I do not know if I do full install 3rd time it will be successful.

Also internet command
root@ubuntu:/# cp /etc/resolv.conf /mnt/etc/resolv.conf
cp: cannot stat `/etc/resolv.conf': No such file or directory
also had error, hence I am afraid that installation is completely messed up.

Boot files are rather important. I do not know if you can chroot into your system and do a full update and it will install them or if you just have to do a total reinstall?

I would try the chroot which is similar to Darko's except I add commands for internet connection:

sudo mount /dev/sda1 /mnt
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo cp /etc/resolv.conf /mnt/etc/resolv.conf #(may or may not be necessary to establish an internet connection)
sudo chroot /mnt
#Then run whatever commands needed - no sudo needed (maybe good to run "df- H" and "cat /etc/issue" to be certain you mounted the correct partition).
apt-get update
apt-get upgrade
#When done:
exit
sudo umount /mnt/dev
sudo umount /mnt/proc
sudo umount /mnt

[kansasnoob]

I'd try one of two things (or try the first and if it fails try the second) before reinstalling:

#1: Physically reinstall grub2 (packages and all).

#2: Revert to legacy grub.

To update the package list and remove/install packages we need to add a few steps to the mount & chroot. Look here please for full explanation:

http://ubuntuforums.org/showpost.php...2&postcount=10

Whether you choose option #1 or #2 first make sure we're properly mounted, etc:

sudo umount /mnt/dev/pts && sudo umount /mnt/dev && sudo umount /mnt/proc && sudo umount /mnt

Yes those steps are to unmount but I want to know if that returns any errors, if so refer to the aforementioned link about individual commands to properly unmount.

Then mount and chroot:

sudo mount /dev/sda1 /mnt && sudo mount --bind /dev /mnt/dev && sudo mount --bind /proc /mnt/proc && sudo mount --bind /dev/pts /mnt/dev/pts && sudo cp /etc/resolv.conf /mnt/etc/resolv.conf && sudo chroot /mnt

dpkg-divert --local --rename --add /sbin/initctl

ln -s /bin/true /sbin/initctl

Now, just to gather more info about partitions:

df -H

and:

parted /dev/sda print

Then backup the old grub folder and create a new one:

mv /boot/grub /boot/grub_backup

mkdir /boot/grub

Then purge grub2:

apt-get --purge remove grub-pc grub-common os-prober

Now if you chose option #1 only if you want to give grub2 another try:

apt-get update && apt-get install grub-pc

update-grub

grub-install /dev/sda

If that appeared to succeed or you just want to see if the system will boot:

exit

sudo umount /mnt/dev/pts && sudo umount /mnt/dev && sudo umount /mnt/proc && sudo umount /mnt

If you chose to try option #1 and it failed mount & chroot again and we'll try legacy grub:

sudo mount /dev/sda1 /mnt && sudo mount --bind /dev /mnt/dev && sudo mount --bind /proc /mnt/proc && sudo mount --bind /dev/pts /mnt/dev/pts && sudo cp /etc/resolv.conf /mnt/etc/resolv.conf && sudo chroot /mnt

dpkg-divert --local --rename --add /sbin/initctl

ln -s /bin/true /sbin/initctl

Then once again backup the old grub folder and create a new one (I'm assuming that /boot/grub_backup has already been used):

mv /boot/grub /boot/grub_backup2

mkdir /boot/grub

apt-get --purge remove grub-pc grub-common os-prober

apt-get update && apt-get install grub

update-grub

You'll be asked if you want to create a /boot/grub/menu.lst - yes, you do, so type y and enter!

grub-install /dev/sda

Now we need a grub shell:

grub

find /boot/grub/stage1

Should show (hd0,0) so:

root (hd0,0)

setup (hd0)

quit

exit

sudo umount /mnt/dev/pts && sudo umount /mnt/dev && sudo umount /mnt/proc && sudo umount /mnt

And if all went well you should have a bootable OS.

Is that clear as mud? Maybe I should have separated the steps for option #1 and #2 better

Sometimes I almost confuse myself