A second Maverick installation, in top of Windows/Maverick won't add a grub entry for self

Bug #604501 reported by Ara Pulido on 2010-07-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)

Bug Description

Binary package hint: grub

Testing Maverick Alpha 2.

In a machine with Win 7 installed, I installed Maverick Alpha 2 amd64, choosing the size by size installation. It finishes correctly and the Grub menu is correctly installed with dual boot Linux-Win (first_syslog).

On top of those two installations, I installed Maverick Alpha 2 i386, choosing again a size by size installation. Although the installation seems to finish correctly, the new grub entry is not correctly installed and, therefore, I cannot boot into the i386 installation (second_syslog).

Ara Pulido (ara) wrote :
description: updated
Ara Pulido (ara) wrote :
Steve Langasek (vorlon) on 2010-07-12
affects: grub (Ubuntu) → grub2 (Ubuntu)
Colin Watson (cjwatson) wrote :

Could you attach /boot/grub/grub.cfg from the second installed system, please? The second syslog seems to be showing that it at least detected the first system.

Changed in grub2 (Ubuntu):
status: New → Incomplete
Ara Pulido (ara) wrote :

I cannot access to that config file now (the system is no longer installed), but the problem is that it does not add an entry for the newly installed system (the second log).

After the installation of the first system we got:

Linux First (sda5)
Windows 7

After the installation of the second system we got:

Linux First (sda5)
Windows 7

(without an entry for the second system, installed at sda7)

Changed in grub2 (Ubuntu):
status: Incomplete → New
tags: added: iso-testing
Phillip Susi (psusi) wrote :

The requested information was never provided so this should have remained incomplete and expired.

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

Other bug subscribers