Help: Grub lost Ubuntu partition after installing OpenSUSE

Setting up a multi-boot system and after installing OpenSUSE I can get into Windows XP (sda2), a Puppy Linux partition (sdb5), and OpenSuse (sdb6, sdb7).

Swap is set at sdb4 and Ubuntu lives on sdb3, but when I choose the Grub selection for Ubuntu, I get “error 15: file not found.”

From within OpenSUSE, fstab reads as follows:

van@linux-zcgq:/etc> cat fstab
/dev/disk/by-id/ata-WDC_WD6400AACS-00G8B1_WD-WCAUF3094719-part4 swap swap defaults 0 0
/dev/disk/by-id/ata-WDC_WD6400AACS-00G8B1_WD-WCAUF3094719-part6 / ext3 acl,user_xattr 1 1
/dev/disk/by-id/ata-WDC_WD6400AACS-00G8B1_WD-WCAUF3094719-part7 /home ext3 acl,user_xattr 1 2
/dev/disk/by-id/ata-SAMSUNG_HD080HJP_S0DEJ10YB71185-part2 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
/dev/disk/by-id/ata-WDC_WD6400AACS-00G8B1_WD-WCAUF3094719-part1 /windows/D ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0

fdisk -l gives back the following:

linux-zcgq:/etc # fdisk -l

Disk /dev/sda: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe686f016

Device Boot Start End Blocks Id System
/dev/sda1 1 6 48163+ de Dell Utility
/dev/sda2 * 7 9118 73192140 7 HPFS/NTFS
/dev/sda3 9120 9725 4867695 db CP/M / CTOS / …

Disk /dev/sdb: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000984a0

Device Boot Start End Blocks Id System
/dev/sdb1 1 12919 103771836 7 HPFS/NTFS
/dev/sdb2 39587 77825 307154767+ 5 Extended
/dev/sdb3 13557 39586 209085975 83 Linux
/dev/sdb4 12920 13556 5116702+ 82 Linux swap / Solaris
/dev/sdb5 58783 77825 152962897+ 83 Linux
/dev/sdb6 39587 42197 20972794+ 83 Linux
/dev/sdb7 42198 58782 133218981 83 Linux

On boot, the OpenSUSE installed Grub, when selected for Ubuntu, goes to the Ubuntu Grub (I think) and from there gives back the error, but Ubuntu loaded fine prior to installing Grub with the OpenSUSE install.

Any help on getting my Ubuntu partition back?

Danke!

Can you provide:

  • your PC’s openSUSE /boot/grub/menu.lst file contents? You will likely need to open it with root permissions in order to paste here. … and also …
  • your PC’s Ubuntu /boot/grub/menu.lst file (or what ever the ubuntu equivalent)? You may need to manually mount the sdb3 of Ubuntu before you can access its menu.lst file. Do you know how to do that manual mount of sdb3? or do you need help there also ?

Probably I do not know enough to help, but I suspect who ever helps you will want to know that information.

Thanks for the interest and assist! Here are the Grub menu files for OpenSUSE and Ubuntu:

The OpenSUSE “menu.lst” file:

# Modified by YaST2. Last modification on Tue Jul 28 15:40:16 CDT 2009
default 0
timeout 8
gfxmenu (hd1,5)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1
    root (hd1,5)
    kernel /boot/vmlinuz-2.6.27.7-9-default root=/dev/disk/by-id/ata-WDC_WD6400AACS-00G8B1_WD-WCAUF3094719-part6 resume=/dev/disk/by-id/ata-WDC_WD6400AACS-00G8B1_WD-WCAUF3094719-part4 splash=silent showopts vga=0x31a
    initrd /boot/initrd-2.6.27.7-9-default

###Don't change this comment - YaST2 identifier: Original name:  Ubuntu 9.04, kernel 2.6.28-13-generic (/dev/sdb3)###
title Ubuntu 9.04, kernel 2.6.28-13-generic (/dev/sdb3)
    root (hd1,2)
    configfile /boot/grub/menu.lst

###Don't change this comment - YaST2 identifier: Original name:  Ubuntu 9.04, kernel 2.6.28-11-generic (/dev/sdb5)###
title Ubuntu 9.04, kernel 2.6.28-11-generic (/dev/sdb5)
    root (hd1,4)
    configfile /boot/grub/menu.lst

###Don't change this comment - YaST2 identifier: Original name: windows 1###
title windows 1
    rootnoverify (hd0,1)
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: windows 2###
title windows 2
    map (hd1) (hd0)
    map (hd0) (hd1)
    rootnoverify (hd1,0)
    makeactive
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: windows 3###
title windows 3
    map (hd2) (hd0)
    map (hd0) (hd2)
    rootnoverify (hd2,0)
    makeactive
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.1
    root (hd1,5)
    kernel /boot/vmlinuz-2.6.27.7-9-default root=/dev/disk/by-id/ata-WDC_WD6400AACS-00G8B1_WD-WCAUF3094719-part6 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
    initrd /boot/initrd-2.6.27.7-9-default

The Ubuntu “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 use 'savedefault' 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		10

## 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=fa8527b8-5d31-4f48-a2df-3ceb2615ac90 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=fa8527b8-5d31-4f48-a2df-3ceb2615ac90

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

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
##      indomU=true
##      indomU=false
# indomU=detect

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

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title		Ubuntu 9.04, kernel 2.6.28-13-generic
uuid		fa8527b8-5d31-4f48-a2df-3ceb2615ac90
kernel		/boot/vmlinuz-2.6.28-13-generic root=UUID=fa8527b8-5d31-4f48-a2df-3ceb2615ac90 ro quiet splash 
initrd		/boot/initrd.img-2.6.28-13-generic
quiet

title		Ubuntu 9.04, kernel 2.6.28-13-generic (recovery mode)
uuid		fa8527b8-5d31-4f48-a2df-3ceb2615ac90
kernel		/boot/vmlinuz-2.6.28-13-generic root=UUID=fa8527b8-5d31-4f48-a2df-3ceb2615ac90 ro  single
initrd		/boot/initrd.img-2.6.28-13-generic

title		Ubuntu 9.04, kernel 2.6.28-11-generic
uuid		fa8527b8-5d31-4f48-a2df-3ceb2615ac90
kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=fa8527b8-5d31-4f48-a2df-3ceb2615ac90 ro quiet splash 
initrd		/boot/initrd.img-2.6.28-11-generic
quiet

title		Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid		fa8527b8-5d31-4f48-a2df-3ceb2615ac90
kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=fa8527b8-5d31-4f48-a2df-3ceb2615ac90 ro  single
initrd		/boot/initrd.img-2.6.28-11-generic

title		Ubuntu 9.04, memtest86+
uuid		fa8527b8-5d31-4f48-a2df-3ceb2615ac90
kernel		/boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title		Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title		Dell Utility Partition
root		(hd0,0)
savedefault
chainloader	+1


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda2
title		Windows XP Media Center Edition
rootnoverify	(hd0,1)
savedefault
chainloader	+1


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb5.
title		unknown Linux distribution (on /dev/sdb5)
root		(hd1,4)
kernel		/boot/vmlinuz root=/dev/sdb5 
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb5.
title		unknown Linux distribution (on /dev/sdb5)
root		(hd1,4)
kernel		/boot/vmlinuz root=/dev/sdb5 
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb6.
title		Ubuntu 9.04, kernel 2.6.28-11-generic (on /dev/sdb6)
root		(hd1,5)
kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=51b981a5-3e2f-4565-b00e-2c5334480dfb ro ROOTFLAGS=syncio quiet splash 
initrd		/boot/initrd.img-2.6.28-11-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb6.
title		Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode) (on /dev/sdb6)
root		(hd1,5)
kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=51b981a5-3e2f-4565-b00e-2c5334480dfb ro ROOTFLAGS=syncio single 
initrd		/boot/initrd.img-2.6.28-11-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb6.
title		Ubuntu 9.04, kernel 2.6.27-11-generic (on /dev/sdb6)
root		(hd1,5)
kernel		/boot/vmlinuz-2.6.27-11-generic root=UUID=51b981a5-3e2f-4565-b00e-2c5334480dfb ro ROOTFLAGS=syncio quiet splash 
initrd		/boot/initrd.img-2.6.27-11-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb6.
title		Ubuntu 9.04, kernel 2.6.27-11-generic (recovery mode) (on /dev/sdb6)
root		(hd1,5)
kernel		/boot/vmlinuz-2.6.27-11-generic root=UUID=51b981a5-3e2f-4565-b00e-2c5334480dfb ro ROOTFLAGS=syncio single 
initrd		/boot/initrd.img-2.6.27-11-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb6.
title		Ubuntu 9.04, memtest86+ (on /dev/sdb6)
root		(hd1,5)
kernel		/boot/memtest86+.bin  
savedefault
boot

Sorry previous post’s files weren’t wrapped in “CODE” for easier reading.

You stated Puppy is sdb5 and openSUSE is sdb6/sdb7 and Ubuntu is sdb3.

From what I can see (ignoring windows), the openSUSE menu.lst calls an [hd1,5] /boot/message, and
provides the Linux options to:

  • boot sdb3 [hd1,2] via its /boot/grub/mneu.lst (commented Ubuntu-9.04 2.6.28-13 kernel)
  • boot sdb5 [hd1,4] via its /boot/grub/menu.lst (commented Ubuntu-9.04 2.6.28-11 kernel)
  • boot [hd1,5] via /boot/vmlinux-2.6.27.7-9-default (openSUSE-11.1)
  • boot [hd1,5] via /boot/vmlinux-2.6.27.7-9-default (openSUSE-11.1 safe)
  • various windows that I don’t have a “handle” on

The Ubuntu Menu.lst has code I’m not familiar with (even more than the openSUSE menu.lst) and it appears to provide options to:

  • boot sdb5 [hd1,4] via /boot/vmlinuz - unknown linux - probably Puppy
  • boot sdb5 [hd1,4] via /boot/vmlinuz - unknown linux - probably Puppy
  • boot sdb6 [hd1,5] via /boot/vmlinuz-2.6.28-11-generic (called Ubuntu-9.0.4)
  • boot sdb6 [hd1,5] via /boot/vmlinuz-2.6.28-11-generic (recovery called Ubuntu-9.0.4)
  • boot sdb6 [hd1,5] via /boot/vmlinuz-2.6.28-11-generic (second entry - called Ubuntu-9.0.4)
  • boot sdb6 [hd1,5] via /boot/vmlinuz-2.6.28-11-generic (recovery) (second entry - called Ubuntu-9.04)
  • various windows [hd0,1]

Note Ubuntu and openSUSE care labeling the same partitions by different names. (see below for a suspicion of mine)

Its possible the files:

  • /boot/grub/device.map
  • /etc/grub.conf

on both your openSUSE and Ubuntu will explain the difference ? Or maybe there is a mistake in your Ubuntu menu.lst (in which case it was NOT the openSUSE update that broke your Ubuntu)

You note your Puppy Linux works. I see no Puppy Linux title. Just what do you select to boot Puppy Linux?

Reference your Ubuntu, do you know what kernel version you were using ?

I’m suspicious that the problem may not be with the openSUSE menu.lst but rather with the Ubuntu menu.lst.

I think people more qualified than I in this should give a suggestion.

One thing I note is it appears to me openSUSE and Ubuntu have different definitions as to what sdbx and [hd1,x] are. Could it be in your Ubuntu menu.lst you need to change the references to [hd1,5] to instead [hd1,3] ?

That should read:

Note Ubuntu and openSUSE are labeling the same partitions by different names. (see below for a suspicion of mine)

One possibility that occured to me when walking in the way to work this morning is if your Ubuntu menu.lst was correct (and Ubuntu was on [hd1,5] … ie sdb6 ) , then you made a mistake when accepting the openSUSE installer partition recommendation, and you accepted an inappropriate (per your plans) openSUSE installer recommendation to overwrite your Ubuntu.

Lets hope that is not the case, and hope that your Ubuntu is indeed on sdb3. It does not look good to me.

You can find out where ubuntu is by running these coommands in openSUSE. Open a terminal windo and enter: su, to become root. Then enter: grub, to go to a prompt like this: grub>
Then this:

find /initrd.img

You should get a response like (hd0,3) this one when I run mine:

grub> find /initrd.img
 (hd0,8)
grub>

openSUSE will not respond to that command whereas Ubuntu will respond.

Suppose for illustration that it returns (hd1,2) [which means sdb3]. You would create this entry in openSUSE’s menu.lst for Ubuntu:

#Don't change this comment - YaST2 identifier: Original name: none#
title Ubuntu booting via symlink in the root directory of sdb3
root (hd1,2)
kernel /vmlinuz root=/dev/sdb3 ro quiet splash
initrd /initrd.img

Adjust (hd1,2) and sdb3 to match what you get returned from: find /initrd.img
Good luck

Reference: HowTo Multiboot Ubuntu from openSUSE using the GRUB bootloader

I know it wasn’t me who posted, but thank you!!! My wife loves Ubuntu, but really liked openSUSE 11.2… we’ve both been trying to sort this boot problem for days. Your tip worksrotfl!

Thank you Swerdna

Good news. Glad for you.