grub menu has duplicate entries

Bug #419044 reported by Stilor
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
grub-installer (Ubuntu)
Fix Released
Undecided
Colin Watson
grub2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: grub2

Installed Kubuntu 9.10 alpha 4 on a system which already has Kubuntu 8.04.3 and Windows Vista installed, noticed several issues with GRUB2:

1. If after an installation I run update-grub, there are duplicate entries for those other systems (Kubuntu 8.04.3 and Vista). One set of entries comes from 30_otheros and another is added by 30_os-prober.

2. There is no option in /etc/default/grub to disable memtest entries; only by removing /etc/grub.d/20_memtest86+ file.

avn@etoile:~$ lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10
avn@etoile:~$ apt-cache policy grub2
grub2:
  Installed: (none)
  Candidate: 1.96+20090725-1ubuntu2
  Version table:
     1.96+20090725-1ubuntu2 0
        500 http://us.archive.ubuntu.com karmic/universe Packages

Revision history for this message
Stilor (stilor) wrote :

Also,

3. There is no way to have all entries generaged with "savedefault" command with GRUB2.

Revision history for this message
Colin Watson (cjwatson) wrote :

Thanks for your report. Please file separate problems (your numbers 1, 2, and 3) in separate bug reports in future, as they're likely to be addressed at different times. For the time being, I'm only going to address number 1; number 3 may happen in the near future; and I don't think work on number 2 is planned at the moment.

Revision history for this message
Colin Watson (cjwatson) wrote :

Fix for #1 committed to Debian's grub-installer

Changed in grub-installer (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
status: New → Fix Committed
Revision history for this message
Stilor (stilor) wrote :

Thanks for quick fix!

I submitted a separate bug 420967 for the 2nd problem.

For the 3rd issue, there is an existing bug 216178.

Revision history for this message
Stilor (stilor) wrote :

BTW, bug 420967 has a proposed patch attached to it.

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.7 KiB)

This bug was fixed in the package grub-installer - 1.42ubuntu1

---------------
grub-installer (1.42ubuntu1) karmic; urgency=low

  * Resynchronise with Debian. Remaining changes:
    - Show the grub menu and raise the menu timeout if other operating
      systems are installed (only for GRUB Legacy right now).
    - Ask grub-installer/only_debian at medium priority.
    - Remove splash boot parameter unless debian-installer/framebuffer=true.
    - If / or /boot are on a removable device, install GRUB there by
      default.
    - Only mount /target/proc if it isn't already mounted.
    - Support setting OVERRIDE_UNSUPPORTED_OS in the environment to force
      grub-installer to use its default MBR selection method despite there
      being unsupported operating systems on the disk.
    - Unless grub-installer/make_active is preseeded to false, mark the
      partition to which GRUB is being installed as bootable, or failing
      that the first available primary partition on the disk to which GRUB
      is being installed.
    - Support grub-installer/bootdev_directory preseeding to make use of the
      relative path feature of grub4dos, so that we can point grub4dos at
      part of a disk for Wubi. Setting this disables normal grub
      installation, but still generates a device.map; it also hides the
      menu.
    - Handle cases where /boot is bind-mounted.
    - Add support for writing an GRUB Legacy MBR on each disk in an
      mdadm-managed RAID providing /boot. (GRUB 2 can handle this already.)
    - Properly make use of output from os-prober to configure the booting of
      other operating systems on dmraid arrays. Attempt to guess where in
      the device map the array belongs, by substituting the first drive in
      the dmraid array for the dmraid array device node itself, and removing
      any reference to other member disks of the array.
    - Set a sensible default boot device when /cdrom is not iso9660, as this
      is probably a USB install and (hd0) does not make sense when
      installing from a removable disk.
    - Go back to using update-grub -y for GRUB Legacy for now; our grub
      package is a bit old and still requires this.
    - Default to grub2 for GPT systems.
    - Allow grub/grub2 choice for ext4, though still default to grub2.
  * Restrict code to generate device.map for loop installations to GRUB
    Legacy (LP: #421873).
  * Fix said code to run grub chrooted into /target.

grub-installer (1.42) unstable; urgency=low

  [ Felix Zielcke ]
  * Check that /etc/kernel-img.conf exists before running sed over it.

  [ Colin Watson ]
  * Don't create /etc/grub.d/30_otheros if os-prober is already installed
    for grub2 to use (LP: #419044).
  * Pass user parameters to grub2 (closes: #470894).
  * Add myself to Uploaders.

  [ Updated translations ]
  * Korean (ko.po) by Changwoo Ryu

grub-installer (1.41) unstable; urgency=low

  [ Colin Watson ]
  * Merge from Ubuntu:
    - Add support for Ubuntu's lpia architecture ("Low-Power Intel
      Architecture").
  * Upgrade to debhelper v7.

  [ Felix Zielcke ]
  * Add support for /dev/rs/c[0-9]d[0-9] style devices.

  [ Luca Favatella ]
  * Add support for /d...

Read more...

Changed in grub-installer (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
JimUSA (jim-sylvania) wrote :

This sounds similar to a problem I have. I had a problem with the ubuntu 9.1 installation and I repeated the installation repeatedly and the partitioner screen indicated that I had multiple ubuntu 9.1 installations on the disk. It appeared to add additional copies instead of overwriting. I deleted the partitions, even formatted them, but the grub menu lists ubuntu 9.1 twice, along with the xp partition. Is this the same bug?

Revision history for this message
Omer Akram (om26er) wrote :

closing the grub task as the problem was fixed in grub installer.

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