No 2.6.17-10-386 entry after Dapper -> Edgy upgrade

Bug #67965 reported by Quim Gil
4
Affects Status Importance Assigned to Milestone
grub (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I upgraded from Dapper to Edgy. Fine. However, after rebooting grub doesn't show the 2.6.17-10-386 entry. Everything is in place, and if I edit any existing entry I can boot without a problem.

menu.lst attached, the 2.6.17-10-386 entry is there.

Just in case it has any relation: in another partition I have an older edgy installed. In the grub menu I see the entries for both partitions, plus the Windows XP. As far as I can see menu.lst doesn't include the entries of the other partition with Edgy installed.

Revision history for this message
Quim Gil (qgil) wrote :
Revision history for this message
jeremy ross (jeremy-ross) wrote :

I have this exact problem. However, I have a simpler setup -- Edgy is my only OS. I also upgraded from Dapper.

Revision history for this message
jeremy ross (jeremy-ross) wrote :

I just discovered this was being caused due to sda1 and sda2 having the same UUID. I have no idea how this happened, but Grub and the Linux kernel had differing opinions on which partition to look at for the jacked up UUID.

Revision history for this message
Mike Dahlgren (dahlgren) wrote :

Since Edgy is no longer a supported platform I am marking this bug as invalid. If you believe this is in error, please feel free to change it back.

 Thanks,
    ~ Mike

Changed in grub:
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.