Karmic Koala Upgrade Uninstalls Grub 2

Bug #449679 reported by Jamie Kitson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: update-manager

Upgrading from Jaunty to Karmic uninstalled Grub 2 and reinstalled Grub 1. The latest kernel was also not added to menu.lst (see bug 407750). Once I had reinstalled Grub 2 the latest kernel was added to menu.lst. Unfortunately my /var/log/dist-upgrade/ directory is empty.

To reproduce:

Have a system running Jaunty (kernel 2.6.28) and Grub 2.
Upgrade to Karmic Koala.

Expected:

A system booting Grub 2 and kernel 2.6.31.

What happened:

A system booting Grub 1 and kernel 2.6.28.

ProblemType: Bug
Architecture: amd64
Date: Mon Oct 12 17:37:09 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: update-manager 1:0.126
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SourcePackage: update-manager
Uname: Linux 2.6.31-13-generic x86_64

Revision history for this message
Jamie Kitson (jamie-kitson) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Could you please attach the logs from /var/log/dist-upgrade/* ?

Changed in update-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Jamie Kitson (jamie-kitson) wrote :

Unfortunately that directory is empty.

Revision history for this message
Daniel Drummond (dmdrummondx) wrote :

I had this problem too. Installed Jaunty from the alternate install cd, and was asked if I wanted to install Grub 2. Figured I would to save any hassle later. Then I ran an upgrade to Karmic, which installed grub 1, and didn't update the menu.lst with the correct kernel. Had to edit the grub boot lines to boot the correct one.

Revision history for this message
Jamie Kitson (jamie-kitson) wrote :

Daniel, do you have anything you can post in /var/log/dist-upgrade/?

Revision history for this message
Raph (rabelanger) wrote :

Same thing happened to me, I was running Jaunty with Grub 2. Got an error with memtest while installing upgrade and a few errors at the very end of update. Then a few errors had then end of the update. Couldnt boot after. Same for me, directory /var/log/dist-upgrade/ is empty.

Revision history for this message
Brian Murray (brian-murray) wrote :

I tried recreating this by upgrade a Jaunty system to Karmic today and grub2 was still installed and grub was not. Additionally, '/var/log/dist-upgrade/' did exist.

Revision history for this message
Jamie Kitson (jamie-kitson) wrote :

Is the dist-upgrade directory used by apt or a gnome application? I used apt-get dist-upgrade. I did find /var/log/apt/term.log which may be of use.

Cheers, Jamie

Revision history for this message
Michael Vogt (mvo) wrote :

@Raph: the memtest that gave errors during install is fixed.

@Jamie: thanks for the log. it shows indeed that grub2 is removed. But unfortunately it does not tell why apt did it. The release upgrade writes out the "problemResolver" log so that those issues can be better analyized. I will try to reproduce the removal in a VM now.

Revision history for this message
Michael Vogt (mvo) wrote :
Changed in update-manager (Ubuntu):
status: Incomplete → In Progress
affects: update-manager (Ubuntu) → grub2 (Ubuntu)
Changed in grub2 (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Michael Vogt (mvo) wrote :

Its enough to just change the override file, I subscribe ubuntu-archive for this. It just needs a change from priority "extra" to "optional" (to match the priority of grub).

Revision history for this message
Steve Langasek (vorlon) wrote :

I've bumped the priority of grub2 source and the grub-{pc,common} binaries in the karmic archive to 'optional'. That will take care of this problem for any users upgradng from the network, but this problem may still affect anyone upgrading from a local karmic alternate CD, since those are not expected to be regenerated between now and release.

It's appropriate to get the priority as listed in the source package updated, but this is not at all urgent.

Changed in grub2 (Ubuntu):
status: In Progress → Triaged
importance: Medium → Low
Colin Watson (cjwatson)
Changed in grub2 (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package grub2 - 1.98~20100128-1ubuntu2

---------------
grub2 (1.98~20100128-1ubuntu2) lucid; urgency=low

  [ Michael Vogt ]
  * Change the priority to optional to match the priority of grub. This
    prevents grub-pc getting removed in favour of grub (LP: #449679).

  [ Colin Watson ]
  * Stop the postinst failing if there are no devices.
 -- Colin Watson <email address hidden> Thu, 04 Feb 2010 12:44:29 -0800

Changed in grub2 (Ubuntu):
status: Fix Committed → Fix Released
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.