fresh 10.10 install and update loads to grub propt

[warch]

I'm getting a tad frustrated.

Having gone down a dead end on this thread:
http://www.uluga.ubuntuforums.org/showthread.php?p=10321060#post10321060

I reloaded 10.10, wiping out previous install. Everything was working as it should. I then updated (today, Sept 16, 2011)

When rebooted, the system went right to a grub prompt.

Again, MOST frustrating. If you have any sure fire help to cure this, please understand that I am not a computer wiz kid, I am learning, but I need precise instructions and explanations.

Thanks in advance.

[wilee-nilee]

So from a booted live Ubuntu cd or thumbdrive lets see the bootscript read out; in my signature just click on it and follow the instructions. Come back to the thread and click on the (#) in the reply panel this makes code tags paste all the text in between.

[warch]

here it is:


Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

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

sda1: __________________________________________________ _______________________

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

sda2: __________________________________________________ _______________________

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

sda5: __________________________________________________ _______________________

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

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 164.7 GB, 164696555520 bytes
255 heads, 63 sectors/track, 20023 cylinders, total 321672960 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 * 2,048 315,531,263 315,529,216 83 Linux
/dev/sda2 315,533,310 321,671,167 6,137,858 5 Extended
/dev/sda5 315,533,312 321,671,167 6,137,856 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 b2ea4a2a-7998-41ce-982e-a614b5589eb4 ext4
/dev/sda2: PTTYPE="dos"
/dev/sda5 8cf82531-157e-4a24-ac97-1977704f0122 swap
/dev/sda: PTTYPE="dos"

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sr0 /cdrom iso9660 (ro,noatime)
/dev/loop0 /rofs squashfs (ro,noatime)


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

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

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set b2ea4a2a-7998-41ce-982e-a614b5589eb4
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set b2ea4a2a-7998-41ce-982e-a614b5589eb4
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
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/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set b2ea4a2a-7998-41ce-982e-a614b5589eb4
linux /boot/vmlinuz-2.6.35-24-generic root=UUID=b2ea4a2a-7998-41ce-982e-a614b5589eb4 ro quiet splash
initrd /boot/initrd.img-2.6.35-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set b2ea4a2a-7998-41ce-982e-a614b5589eb4
echo 'Loading Linux 2.6.35-24-generic ...'
linux /boot/vmlinuz-2.6.35-24-generic root=UUID=b2ea4a2a-7998-41ce-982e-a614b5589eb4 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set b2ea4a2a-7998-41ce-982e-a614b5589eb4
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=b2ea4a2a-7998-41ce-982e-a614b5589eb4 ro quiet splash
initrd /boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set b2ea4a2a-7998-41ce-982e-a614b5589eb4
echo 'Loading Linux 2.6.35-22-generic ...'
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=b2ea4a2a-7998-41ce-982e-a614b5589eb4 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set b2ea4a2a-7998-41ce-982e-a614b5589eb4
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set b2ea4a2a-7998-41ce-982e-a614b5589eb4
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ "x${timeout}" != "x-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 ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_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 nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=b2ea4a2a-7998-41ce-982e-a614b5589eb4 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=8cf82531-157e-4a24-ac97-1977704f0122 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

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


98.9GB: boot/grub/core.img
146.2GB: boot/grub/grub.cfg
1.1GB: boot/initrd.img-2.6.35-22-generic
1.2GB: boot/initrd.img-2.6.35-24-generic
98.9GB: boot/vmlinuz-2.6.35-22-generic
98.9GB: boot/vmlinuz-2.6.35-24-generic
1.2GB: initrd.img
1.1GB: initrd.img.old
98.9GB: vmlinuz
98.9GB: vmlinuz.old

[warch]

sorry, server issues - repost

[warch]

sorry for reposts, really bad connection problems. Just will not load, so I tried thrice. It's not even saving the edit

[kansasnoob]

The forum server is getting full :(

Regarding your boot problem try pressing the left Shift key as soon as BIOS/System screen passes on reboot and try selecting the older kernel "2.6.35-22-generic".

I'm guessing you have some kind of hardware conflict with the newer kernel.

[warch]

don't see where that would be applicable - no BIOS/system screen unless I hit F2.

If I hit F2 and enter setup, upon exit, it goes right to grub prompt.

Can I load an older kernel from the grub prompt?

[wilee-nilee]

don't see where that would be applicable - no BIOS/system screen unless I hit F2.

If I hit F2 and enter setup, upon exit, it goes right to grub prompt.

Can I load an older kernel from the grub prompt?

As soon as you turn the computer on hold down the shift key to see if you get the grub menu, if so choose the older kernel. The script looks as if you should boot okay.

Since all looks well we have to get creative, as it seems your problem would not be applicable, but it is, does that make sense to you.

[warch]

NOPE, "Keyboard Failure", I release the shift key and then grub prompt

[wilee-nilee]

NOPE, "Keyboard Failure", I release the shift key and then grub prompt

One of the better tools to have is a supergrub disc, down load 2 the middle one it may get you into the install. There you would run
sudo update-grub
reboot to see if you were reloaded, and the grub menu now appears.
http://www.supergrubdisk.org/

The are also manual methods, and just reloading grub to the mbr as well. If the supergrub discs works it is a bit easier way to just get in if needed, at this point probably.

[warch]

not sure what you mean.

The menu for the supergrub 2 disk gives options such as

Detect any OS
Detect any Grub2 configuration file
Detect any Grub2 installation (even if mbr is over written)
Detect loop bootable isos (in /boot-isos or /boot/boot-isos)
etc etc


when I hit "c" for command line I get a grub prompt which does not recognize the command you suggested - unknown command "sudo"

I have a copy of Reskatux, should I try to reload Grub2 with that ?

[warch]

Now wait a minute

When I hit detect any OS, it shows earlier kernel (22) and booted succesfully !!!!

[warch]

Reboot puts me into grub prompt.

How do I remove errant kernel (2.6.35-24-generic)

[wilee-nilee]

Now wait a minute

When I hit detect any OS, it shows earlier kernel (22) and booted succesfully !!!!

So it may be as kansasnoob suggested the 24 kernel maybe having a problem, so run the
sudo update-grub
reboot and mess around trying the 24, and 22 kernel. You have a way to boot in as of now. This is if the grub menu shows.

[warch]

24 kernel will not boot. Need to remove or fix it.

suggestions?

[warch]

repost

[warch]

repost

these long load times are frustrating :D

[wilee-nilee]

Reboot puts me into grub prompt.

How do I remove errant kernel (2.6.35-24-generic)

I use ubuntu tweak it has a kernel remove section, but make sure your removing the correct one.
http://ubuntu-tweak.com/downloads/

If you scroll down the page you will see a command that will load the ppa and the key for it.

sudo add-apt-repository ppa:tualatrix/ppa

Then run
sudo apt-get update.
then
sudo apt-get install ubuntu tweak

It will be in menu-system tools, look in the package cleaner.

Not sure if just removing it will fix this but it is up to you. Not sure of a fix for the 24 either. You might just hold tight, since you can boot in with the supergrub disc, until kansasnoob posts again or another knowledgeable person. Things are a bit slower on the weekend.

[Rebelli0us]

The same happened with my brand new mobo 890gx, new install went fine from CD but then booted to Grub rescue. Version 10.10 has since caught up with new hardware and works fine now, make sure you're using the latest ISO (especially if you have AMD SB850 + USB 3.0).

[warch]

thanks,

I figure if I try a removal and it doesn't work, I'll just reload from the CD and not do an update. This is not my main box, it was to get me familiar with Ubuntu, and this re-install was fresh, so there was nothing critical on it.

Maybe I'll wait for April and try Natty Narwhal instead of the updates for 10.10

[warch]

I do not know what I was doing wrong even though I thought I was following the instructions you listed and the ones found on ubuntu-tweak.com. I just was not able to load Ubuntu Tweak. I am not good at this.

I finally stepped away for a bit, returned, and followed what drs305 wrote here
http://ubuntuforums.org/showthread.php?t=1587462
Ubuntu Tweak loaded and the kernel in question was removed with no problems. The machine boots flawlessly to the workable kernel: 2.6.35-22-generic

Thank you for your patience, time, and help.

[wilee-nilee]

I do not know what I was doing wrong even though I thought I was following the instructions you listed and the ones found on ubuntu-tweak.com. I just was not able to load Ubuntu Tweak. I am not good at this.

I finally stepped away for a bit, returned, and followed what drs305 wrote here
http://ubuntuforums.org/showthread.php?t=1587462
Ubuntu Tweak loaded and the kernel in question was removed with no problems. The machine boots flawlessly to the workable kernel: 2.6.35-22-generic

Thank you for your patience, time, and help.

drs305 is a great help to all of us, glad your all set.

[Quackers]

From memory I think the -24 kernel has been known to generate some problems with some hardware.

[warch]

From memory I think the -24 kernel has been known to generate some problems with some hardware.

I'll attest to that ;)

Do you have any idea where I could learn more about what hardware causes issues?

Or should I list as much as I know about my machine so others can use as reference?