PDA

View Full Version : [ubuntu] upgraded to 2.6.31-19 kernel today and will not boot



ak331
February 5th, 2010, 06:24 PM
this the second time it has happened after the security upgrade to kernel 2.6.31-19 with a clean shut down it goes into the grub menu and will not boot. help ????????

ratcheer
February 5th, 2010, 06:50 PM
Maybe grub just didn't get reconfigured, correctly. See this thread on making sure grub is correctly set up:

http://ubuntuforums.org/showthread.php?t=1195275

Tim

ak331
February 5th, 2010, 07:40 PM
I did see the thread and followed the instructions and tried first to load kernel 2.6.31-19 and then 2.6.31-17 and got a message file not found.

kansasnoob
February 5th, 2010, 08:03 PM
Rather than ask a lot of questions would you run the Boot Info script and post the results:

http://bootinfoscript.sourceforge.net/

I assume you're running the Live CD.

kansasnoob
February 5th, 2010, 08:11 PM
I see 2.6.31-19 has been held back on the US server. Maybe I should be glad :)

2hot6ft2
February 5th, 2010, 08:35 PM
I see 2.6.31-19 has been held back on the US server. Maybe I should be glad :)
My other pc updated to it earlier using the Chicago server but this one didn't using the Duke server so that's not entirely true.

I had no problem after the reboot. Keeping my fingers crossed now though.

ottosykora
February 5th, 2010, 08:42 PM
I have observed something different:
the update manager stated that there is new kernel -19 and wanted update it. But somehow it was not able to find the ppropper files or what, anyway, nothing was updated, no trace of the -19 kernel on my laptop, so no entry was done into the grub menu.
Tried second time the update manager, but it said all is uptodate.

kansasnoob
February 5th, 2010, 08:51 PM
I'm doing some testing in Lucid right now but I'm going to boot my Karmic and check things out.

ak331
February 5th, 2010, 08:52 PM
here is the text generated by boot info script as follows:




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

=> Grub 2 is installed in the MBR of /dev/sda and looks for
(UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e)/boot/grub.
=> No boot loader is installed in the MBR of /dev/sdb
=> Grub 0.97 is installed in the MBR of /dev/sdc and looks on boot drive #3
in partition #2 for /boot/grub/stage2 and /boot/grub/menu.lst.
sda1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows XP
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files/dirs: /boot.ini /ntldr /NTDETECT.COM /IO.SYS /MSDOS.SYS

sdb1: __________________________________________________ _______________________

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

sdb2: __________________________________________________ _______________________

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

sdb5: __________________________________________________ _______________________

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

sdb6: __________________________________________________ _______________________

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

sdc1: __________________________________________________ _______________________

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

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 60.0 GB, 60022480896 bytes
240 heads, 63 sectors/track, 7753 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x05040503

Partition Boot Start End Size Id System

/dev/sda1 * 63 117,210,239 117,210,177 7 HPFS/NTFS


Drive: sdb ___________________ __________________________________________________ ___

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

Partition Boot Start End Size Id System

/dev/sdb1 * 63 228,039,839 228,039,777 7 HPFS/NTFS
/dev/sdb2 228,042,675 312,576,704 84,534,030 5 Extended
/dev/sdb5 228,042,738 302,262,974 74,220,237 83 Linux
/dev/sdb6 302,263,038 312,576,704 10,313,667 82 Linux swap / Solaris


Drive: sdc ___________________ __________________________________________________ ___

Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x017b966e

Partition Boot Start End Size Id System

/dev/sdc1 * 63 488,392,064 488,392,002 7 HPFS/NTFS


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/ramzswap0 swap
/dev/sda1 E64CDC034CDBCC85 ntfs
/dev/sdb1 E0BB33A78D49FF39 ntfs
/dev/sdb5 b13cf3d2-5d4e-4205-8193-053ca464ea5e ext4
/dev/sdb6 015b66fb-edf7-4c3d-9f27-58e47be7af60 swap
/dev/sdc1 52BC2931BC2910D1 ntfs Drive

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

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sr1 /cdrom iso9660 (rw)
/dev/loop0 /rofs squashfs (rw)


================================ sda1/boot.ini: ================================

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(1)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect



=========================== sdb5/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=(hd1,5)
search --no-floppy --fs-uuid --set b13cf3d2-5d4e-4205-8193-053ca464ea5e
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 ###
menuentry "Ubuntu, Linux 2.6.31-19-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set b13cf3d2-5d4e-4205-8193-053ca464ea5e
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e ro quiet splash
initrd /boot/initrd.img-2.6.31-19-generic
}
menuentry "Ubuntu, Linux 2.6.31-19-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set b13cf3d2-5d4e-4205-8193-053ca464ea5e
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e ro single
initrd /boot/initrd.img-2.6.31-19-generic
}
menuentry "Ubuntu, Linux 2.6.31-17-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set b13cf3d2-5d4e-4205-8193-053ca464ea5e
linux /boot/vmlinuz-2.6.31-17-generic root=UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e ro quiet splash
initrd /boot/initrd.img-2.6.31-17-generic
}
menuentry "Ubuntu, Linux 2.6.31-17-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set b13cf3d2-5d4e-4205-8193-053ca464ea5e
linux /boot/vmlinuz-2.6.31-17-generic root=UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e ro single
initrd /boot/initrd.img-2.6.31-17-generic
}
menuentry "Ubuntu, Linux 2.6.31-16-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set b13cf3d2-5d4e-4205-8193-053ca464ea5e
linux /boot/vmlinuz-2.6.31-16-generic root=UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e ro quiet splash
initrd /boot/initrd.img-2.6.31-16-generic
}
menuentry "Ubuntu, Linux 2.6.31-16-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set b13cf3d2-5d4e-4205-8193-053ca464ea5e
linux /boot/vmlinuz-2.6.31-16-generic root=UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e ro single
initrd /boot/initrd.img-2.6.31-16-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set b13cf3d2-5d4e-4205-8193-053ca464ea5e
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set b13cf3d2-5d4e-4205-8193-053ca464ea5e
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
### 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 ###
menuentry "Microsoft Windows XP Professional (on /dev/sda1)" {
insmod ntfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set e64cdc034cdbcc85
drivemap -s (hd0) ${root}
chainloader +1
}
### 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 ###

=============================== sdb5/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/sdb5 during installation
UUID=b13cf3d2-5d4e-4205-8193-053ca464ea5e / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb6 during installation
UUID=015b66fb-edf7-4c3d-9f27-58e47be7af60 none swap sw 0 0
/dev/scd1 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

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


116.7GB: boot/grub/core.img
116.7GB: boot/grub/grub.cfg
116.7GB: boot/initrd.img-2.6.31-14-generic
116.7GB: boot/initrd.img-2.6.31-16-generic
116.7GB: boot/initrd.img-2.6.31-17-generic
116.7GB: boot/initrd.img-2.6.31-19-generic
116.7GB: boot/vmlinuz-2.6.31-14-generic
116.7GB: boot/vmlinuz-2.6.31-16-generic
116.7GB: boot/vmlinuz-2.6.31-17-generic
116.7GB: boot/vmlinuz-2.6.31-19-generic
116.7GB: initrd.img
116.7GB: initrd.img.old
116.7GB: vmlinuz
116.7GB: vmlinuz.old

2hot6ft2
February 5th, 2010, 09:05 PM
Here's a similar thread that seems it may point to a solution.
Karmic Update to 2.6.31-19 & Grub, Boot Help (http://ubuntuforums.org/showthread.php?t=1399135)

kansasnoob
February 6th, 2010, 12:35 AM
Well I don't see anything obvious wrong with that.

I'm multi-booting Lucid, Karmic, Jaunty, Hardy, Mint Gloria, and Windows and Lucid's grub2 had control.

After upgrading to 2.6.31-19 in Karmic and running "sudo update-grub" I booted into Lucid and again ran "sudo update-grub" and then booted into Karmic's new kernel just fine.

Then while booted into Karmic I handed boot off to it by:


sudo grub-install /dev/sda

After a "sudo update-grub" everything but Karmic & Lucid would boot, after handing boot back to Lucid, Karmic & Lucid would boot just fine.

I also tried booting from legacy grub and that worked fine, so I guess kernel 2.6.31-19 and Karmic's grub2 don't agree with each other.

I have tried to get grub2 upgraded in Karmic:

https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/485457

And nominated the upgrade for Karmic here:

https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/509438

For now I guess either cherry pick packages or revert to legacy grub:

http://ubuntuforums.org/showthread.php?t=1298932

I don't have the patience to fiddle with it anymore.

bscbrit
February 6th, 2010, 03:34 PM
I have the same problem.

I have managed to identify that it only occurs on my computers that have a mixture of PATA (IDE) and SATA drives fitted. The other computers boot fine.

I'm wondering if this is a regression of the problem that existed a few months ago regarding the difference in numbering of drives/partitions between the BIOS and Grub2.

Meanwhile, I have reverted to 31-17 which has at least returned all my computers to workings machines again.

jamere
February 6th, 2010, 05:34 PM
ak331,kansasnoob and bscbrit,

I have the same problem. Currently on 9.10, kernel 2.6.31-16. My system is up-to-date. Update Mgr presented kernel 2.6.31-19 this morning and my system was upgraded without a hitch and asked for a "restart", which I did. Grub2 did not show the new kernel after the restart. I'm running a dual boot Win XP and 9.10 on an Acer Netbook. Not sure what's going on with this kernel update. Hopefully a fix will be presented soon.:confused:

oldfred
February 6th, 2010, 05:55 PM
ak331 - do you have mixed Sata & pata drives like bscbrit mentioned?

Your script shows grub2 in sda and the install in sdc5 but grub2 shows booting from drive (hd1,5)? I would expect it to be drive 2.

Grub also has had an issue with about 20 second delay while it goes off to scan drives whenever it is not on the same drive as the install. I would reinstall grub2 to sdc and change the boot order in BIOS.

https://help.ubuntu.com/community/Grub2#Reinstalling%20GRUB%202
https://wiki.ubuntu.com/Grub2#Recover%20Grub%202%20via%20LiveCD

You may also want to run this command that sets a location for where grub is to be installed.
from a working system:
reinstalls grub and allows choice of which drive to install to. Choose boot drive if not sda, also allows settings in grub file, accept defaults normally.
sudo dpkg-reconfigure grub-pc