Grub installer failed on fresh install of 9.10

Bug #474592 reported by tarlos25
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

The system I am installing to has 2 hard drives, and my partitioning is:

/dev/sda1 /boot 100M
/dev/sda2 swap 2000M
/dev/sda3 / remainder of 80GB
/dev/sdb1 /home 80GB

This is the error message I received:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 457, in <module>
    main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 442, in main
    install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 245, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 440, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 865, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 2430, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 459, in run
    self.configure_bootloader()
  File "/usr/share/ubiquity/install.py", line 1801, in configure_bootloader
    "GrubInstaller failed with code %d" % ret)
InstallStepError: GrubInstaller failed with code 1

Revision history for this message
tarlos25 (tarlos25) wrote :
Revision history for this message
tarlos25 (tarlos25) wrote :

With some additional tinkering, I've found a few more bits of information. Using fdisk -l I found that /dev/sda1 was not set as bootable at the time of the failure. So I manually set it as bootable. Still failed. I recreated the partition and set it as bootable manually, then in the installation told the partitioner to not format that partition. Still failed. Finally, I told it to reformat as ext3 instead of ext2, and it installed successfully (as far as I can tell at this point).

Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 474592

and any other logs that are relevant for this particular issue.

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