Gutsy install failure (from live CD install)

Bug #155528 reported by HL
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

How the problem occurs (could be reproduced on one PC, see further down, all worked well on another machine):

I installed from Gutsy live CD on an existing partition. Told installer to format the drive with ext3 and set mount point to /. The installation finished but did not ask to reboot (as it did with the successful installation on another PC). I restarted manually and got the error:

grub stage 1.5 error 15

Some more info:
- I noticed that after installation but before booting, the system mounted most of my partitions to the same directory /target
- I have one SATA HD on controller plug 2 and an ATA CD-drive
- I have four Windows partitions (dev/sda1, sda5, sda6, sda7), swap (sda8), and fife linux partitions (sda9 - sda13)

I was able to repair grub manually and bottet my old feisty. I searched all the Linux partitions but nowhere were any files from Gutsy installed
so that was the reason for the grub error, the real error must be in the mount/partitioning

Revision history for this message
HL (hansl) wrote :

Correction:

I rechecked the partitions and found an installation of 7.10 in /dev/sda11 (which I chose for installation formatting and mount point /).
There is however no grub directory in /boot and only a .bak file of initrd.img.2.6.22-14-generic.bak
I copied this to initrd.img.2.6.22-14-generic, updated the menu.lst of my feisty (on /dev/sda13) and was able to boot into Gutsy ;-)

To sum up:

The problem was that grub got installed but the partition /dev/sda11 did not contain the grub files

Revision history for this message
Mario Young (mayeco) wrote :

This is a update manager problem
Thank you!

Revision history for this message
HL (hansl) wrote :

I did some browsing in the bug database. This might be a duplicate of

33106
14135
148014
153019

I don't understand: I did a clean install with formatting the / partition. Is update manager still used for that?

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

Thanks for your bugreport.

I reassign to ubiquity, this is not a update-manager bug.

Revision history for this message
Miguel Ruiz (mruiz) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your description didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments by visiting your bug's web page. Thanks in advance.

Changed in ubiquity:
status: New → Incomplete
Revision history for this message
TerryG (tgalati4) wrote :

GRUB has problems with many partitions and multiple OS's. The fact that the reporter exited the installer abnormally, left the machine in an indeterminate state which is unfortunate. Many times the installation can be recovered by either reinstalling GRUB or fixing the menu.lst configuration file. Because ubiquity relies on GRUB as the final step (successful reboot) any errors here results in a frustrating user experience.

Revision history for this message
TerryG (tgalati4) wrote :

Marking as Confirmed to preserve edge use case.

Changed in ubiquity:
status: Incomplete → Confirmed
Revision history for this message
Robert Roth (evfool) wrote :

Thank you for reporting this bug to Ubuntu. Gutsy reached EOL on April 18th, 2009..
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Oneiric and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.