grub2 cannot find kernel in dual kubuntu/xubuntu 9.10 boot scenario

Bug #430659 reported by Jim Campbell
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Karmic by Jim Campbell

Bug Description

Binary package hint: grub2

I'm dual-booting Kubuntu and Xubuntu 9.10, but the auto-generated grub.cfg file from Kubuntu does not correctly identify the Xubuntu partition in a way that allows it to boot. I get an error message when trying to load the Xubuntu installation stating, "Error - you need to load the linux kernel first."

I had run the os-prober and update-grub2 from the Kubuntu installation, and the update-grub2 command does seem to recognize the Xubuntu installation. I've also checked the UUID of the Xubuntu install's root partition and compared it to the detail included in the grub.cfg file, and they match.

Here is some of the system detail:

jwc@nicodemus:/boot/grub$ sudo blkid
/dev/sda1: UUID="151902ed-9218-4bc9-9f53-ca7b55f14f04" TYPE="ext4" (Note: kubuntu root)
/dev/sda2: UUID="cf4eba13-d094-485c-a6b4-6e09eb7893e2" TYPE="ext3" (Note: kubuntu home)
/dev/sda5: UUID="795cab44-dc21-45d0-9681-eea67414de9c" SEC_TYPE="ext2" TYPE="ext3" (Note: xubuntu boot)
/dev/sda6: UUID="8cb0b4ef-ca5a-4eb3-b905-750096510dc1" TYPE="ext4" (Note: xubuntu root)
/dev/sda7: TYPE="swap" (swap!) :-)
/dev/sda8: UUID="1311ea8b-45f2-46c2-9fa3-c496e8e1014a" TYPE="ext4" (Note: xubuntu home)

-----------------------------------------------
$ jwc@nicodemus: cat 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 ###
load_env
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 151902ed-9218-4bc9-9f53-ca7b55f14f04
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
set timeout=10
### 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-10-generic" {
 set quiet=1
 insmod ext2
 set root=(hd0,1)
 search --no-floppy --fs-uuid --set 151902ed-9218-4bc9-9f53-ca7b55f14f04
 linux /boot/vmlinuz-2.6.31-10-generic root=UUID=151902ed-9218-4bc9-9f53-ca7b55f14f04 ro quiet splash
 initrd /boot/initrd.img-2.6.31-10-generic
}
menuentry "Ubuntu, Linux 2.6.31-10-generic (recovery mode)" {
 insmod ext2
 set root=(hd0,1)
 search --no-floppy --fs-uuid --set 151902ed-9218-4bc9-9f53-ca7b55f14f04
 linux /boot/vmlinuz-2.6.31-10-generic root=UUID=151902ed-9218-4bc9-9f53-ca7b55f14f04 ro single
 initrd /boot/initrd.img-2.6.31-10-generic
}
menuentry "Ubuntu, Linux 2.6.31-9-generic" {
 set quiet=1
 insmod ext2
 set root=(hd0,1)
 search --no-floppy --fs-uuid --set 151902ed-9218-4bc9-9f53-ca7b55f14f04
 linux /boot/vmlinuz-2.6.31-9-generic root=UUID=151902ed-9218-4bc9-9f53-ca7b55f14f04 ro quiet splash
 initrd /boot/initrd.img-2.6.31-9-generic
}
menuentry "Ubuntu, Linux 2.6.31-9-generic (recovery mode)" {
 insmod ext2
 set root=(hd0,1)
 search --no-floppy --fs-uuid --set 151902ed-9218-4bc9-9f53-ca7b55f14f04
 linux /boot/vmlinuz-2.6.31-9-generic root=UUID=151902ed-9218-4bc9-9f53-ca7b55f14f04 ro single
 initrd /boot/initrd.img-2.6.31-9-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 "Ubuntu karmic (development branch) (9.10) (on /dev/sda6)" {
 insmod ext2
 set root=(hd0,6)
 search --no-floppy --fs-uuid --set 8cb0b4ef-ca5a-4eb3-b905-750096510dc1
 linux /boot/vmlinuz-2.6.31-10-generic root=/dev/sda6
 initrd /boot/initrd.img-2.6.31-10-generic
}
menuentry "Ubuntu karmic (development branch) (9.10) (on /dev/sda6)" {
 insmod ext2
 set root=(hd0,6)
 search --no-floppy --fs-uuid --set 8cb0b4ef-ca5a-4eb3-b905-750096510dc1
 linux /boot/vmlinuz-2.6.31-9-generic root=/dev/sda6
 initrd /boot/initrd.img-2.6.31-9-generic
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###

jwc@nicodemus:/boot/grub$ sudo parted -l
Model: ATA HITACHI HTS72321 (scsi)
Disk /dev/sda: 160GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 32.3kB 10.5GB 10.5GB primary ext4 boot
 2 10.5GB 21.0GB 10.5GB primary ext3
 3 21.0GB 160GB 139GB extended
 5 21.0GB 21.1GB 132MB logical ext3
 6 21.1GB 33.6GB 12.5GB logical ext4
 7 33.6GB 36.8GB 3197MB logical linux-swap(new)
 8 36.8GB 160GB 123GB logical ext4

Please le tme know if you need additional info. Thanks!

summary: - grub2 cannot file kernel in dual kubuntu/xubuntu 9.10 boot scenario
+ grub2 cannot find kernel in dual kubuntu/xubuntu 9.10 boot scenario
Revision history for this message
Jim Campbell (jwcampbell) wrote :

The issue persists in grub v. 1.97~beta3-1ubuntu4 even after getting updated to the current version of grub (see below) and re-running os-prober and update-grub2.

jwc@nicodemus:~$ dpkg -l grub-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=====================-=====================-==========================================================
ii grub-common 1.97~beta3-1ubuntu4 GRand Unified Bootloader, version 2 (common files)

Revision history for this message
Renate (yollywau) wrote :

grub2 doesn't find the boot-partition of Fedora. update-grub finds the system-partition of Fedora. I can boot Fedora only in command mode of grub2.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If this is still an issue, we would appreciate if you could upload updated logs by running apport-collect 430659, and any other logs that are relevant for this particular issue.

We also would like you to attach the contents of /boot/grub/default as a plain-text file. Thanks for your patience and cooperation.

Changed in grub2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Leaving this open for the developers to use as needed. Would be better to have a response with more log information, but perhaps there is useful information in this report. Thanks

Changed in grub2 (Ubuntu):
status: Incomplete → New
Revision history for this message
Andrew Cranwell (andrew-cranwell) wrote :

Is this bug still present in any supported release?

Revision history for this message
Brian Proffitt (brian-proffitt) wrote : We always can get you the best on price you want.

CHRISTMAS SALE!!!

> You always dreamed of getting gorgeous watches as presents for christmas but couldn't pay for it? Thanks to our site anybody can have this comfort regardless his profits. We have lots of brands to decide from for men and women, for informal wear and special occasions. The watch of your vision has become reasonable today.

> We care about every our client as only the best presents with highest quality are offered to you by Prestige to chose the gifts to your relatives, friends and colleagues for Christmas and New Year holidays.

***************************************************
"By this e-mail I want to tell you that I have reiceived my two replica watches on last Wednesday. They are very nice. I hope I will buy someone more."

                     Margret Fletcher
***************************************************

CLICK HERE --->>> http://mahen.ru

------------------------
--------------
------
15% DISCOUNT FOR EVERY $250 OR MORE ORDER!!!

Revision history for this message
Aaron Luchko (aaron-luchko) wrote :

I can confirm this bug in 12.04.

I'm dual booting Ubuntu and Fedora both on logical volumes with a shared home directory. The auto-detected Fedora system always results in the error that it cannot find (or load?) the kernel. However, I am able to boot with the following entries in /etc/grub.d/40_custom

# cat /etc/grub.d/40_custom
! /bin/sh
set -e
echo "
menuentry 'Fedora-Ubuntu, with Linux 3.6.10-2' --class fedora --class gnu-linux --class gnu --class os {
        recordfail
        insmod gzio
        insmod lvm
        insmod part_msdos
        insmod ext2
        set root='(vg_losgar-lv_fedora)'
        search --no-floppy --fs-uuid --set=root e1726ee3-9b60-4d74-8995-fe714e94aec0
        linux /vmlinuz-3.6.10-2.fc17.x86_64 root=/dev/mapper/vg_losgar-lv_fedora ro quiet splash vt.handoff=7
        initrd /initramfs-3.6.10-2.fc17.x86_64.img
}
"

The issue with this workaround is it has to be manually updated and have update-grub re-run in Ubuntu everytime I update the fedora kernel.

The file /boot/grub/default no longer seems to be present

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
Revision history for this message
Phillip Susi (psusi) wrote :

The kernel should be in /boot, not /. Did you install fedora with its own /boot partition?

Changed in grub2 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Aaron Luchko (aaron-luchko) wrote :

This is what the fstab looks like

proc /proc proc defaults 0 0
/dev/mapper/vg_losgar-lv_ubuntu / ext4 errors=remount-ro 0 1
/dev/mapper/vg_losgar-lv_fedora /fedora ext4 defaults 0 2
/dev/mapper/vg_losgar-lv_home /home ext4 defaults,user_xattr 0 2
/dev/mapper/vg_losgar-lv_swap swap swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

I can't remember exactly how I set things up but it was one partition for fedora, one for ubuntu, and the boot loader got installed with Ubuntu (no specific boot partition for fedora that I can remember), I know at times in the past grub successfully detected and booted fedora but that failed when I upgraded to 12.04.

Revision history for this message
Phillip Susi (psusi) wrote :

What does the fstab in fedora look like and what are the contents of /boot?

Actually, can you run the boot info script and attach the results?

http://sourceforge.net/projects/bootinfoscript/

Revision history for this message
Aaron Luchko (aaron-luchko) wrote :

$ cat /fedora/etc/fstab

#
# /etc/fstab
# Created by anaconda on Mon Jan 4 23:45:04 2010
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/vg_losgar-lv_fedora / ext4 defaults 1 1
UUID=e1726ee3-9b60-4d74-8995-fe714e94aec0 /boot ext4 defaults 1 2
/dev/mapper/vg_losgar-lv_home /home ext4 defaults 1 2
/dev/mapper/vg_losgar-lv_ubuntu /ubuntu ext4 defaults 1 2
/dev/mapper/vg_losgar-lv_swap swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0

$ ls /boot/
abi-2.6.31-22-generic initrd.img-3.2.0-32-generic
abi-2.6.32-25-generic initrd.img-3.2.0-34-generic
abi-2.6.38-11-generic initrd.img-3.2.0-35-generic
abi-3.0.0-17-generic memtest86+.bin
abi-3.2.0-24-generic memtest86+_multiboot.bin
abi-3.2.0-25-generic System.map-2.6.31-22-generic
abi-3.2.0-26-generic System.map-2.6.32-25-generic
abi-3.2.0-27-generic System.map-2.6.38-11-generic
abi-3.2.0-32-generic System.map-3.0.0-17-generic
abi-3.2.0-34-generic System.map-3.2.0-24-generic
abi-3.2.0-35-generic System.map-3.2.0-25-generic
config-2.6.31-22-generic System.map-3.2.0-26-generic
config-2.6.32-25-generic System.map-3.2.0-27-generic
config-2.6.38-11-generic System.map-3.2.0-32-generic
config-3.0.0-17-generic System.map-3.2.0-34-generic
config-3.2.0-24-generic System.map-3.2.0-35-generic
config-3.2.0-25-generic vmcoreinfo-2.6.31-22-generic
config-3.2.0-26-generic vmcoreinfo-2.6.32-25-generic
config-3.2.0-27-generic vmcoreinfo-2.6.38-11-generic
config-3.2.0-32-generic vmcoreinfo-3.0.0-17-generic
config-3.2.0-34-generic vmlinuz-2.6.31-22-generic
config-3.2.0-35-generic vmlinuz-2.6.32-25-generic
grub vmlinuz-2.6.38-11-generic
initrd.img-2.6.31-22-generic vmlinuz-3.0.0-17-generic
initrd.img-2.6.32-25-generic vmlinuz-3.2.0-24-generic
initrd.img-2.6.38-11-generic vmlinuz-3.2.0-25-generic
initrd.img-3.0.0-17-generic vmlinuz-3.2.0-26-generic
initrd.img-3.2.0-24-generic vmlinuz-3.2.0-27-generic
initrd.img-3.2.0-25-generic vmlinuz-3.2.0-32-generic
initrd.img-3.2.0-26-generic vmlinuz-3.2.0-34-generic
initrd.img-3.2.0-27-generic vmlinuz-3.2.0-35-generic

Revision history for this message
Phillip Susi (psusi) wrote :

Yes, fedora appears to have its own /boot partition, and it does not contain the traditional /boot -> . symlink. When installing fedora you should not use a /boot partition unless you either want it to share one with Ubuntu. As a workaround, you should be able to create a symlink in the fedora /boot partition pointing to "."

Changed in grub2 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.