[Kubuntu 7.04] Grubinstaller failed with code 1, SATA

Bug #110292 reported by John Carlyle-Clarke
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Trying to use Live CD installer Kubuntu 7.04 (release) on a standard system. NF4 mainboard with one PATA and one SATA drive, installing to SATA. Have tried with PATA drive removed and effect is the same. Filesystem is ext3.

Installer debug output follows:

------------------------------------

Apr 26 14:14:40 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/usr/share/ubiquity/install.py']' for ubiquity.components.install.Install
Apr 26 14:14:40 ubiquity: Watching for question patterns ^.*/apt-install-failed$, migration-assistant/failed-unmount, grub-installer/install_to_xfs, CAPB, ERROR, PROGRESS

Apr 26 15:25:30 ubiquity: ['log-output', '-t', 'ubiquity', '--pass-stdout', '/usr/share/ubiquity/install.py'] exited with code 1

Exception in KDE frontend (invoking crash handler):

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 210, in <module>
    main()
  File "/usr/lib/ubiquity/bin/ubiquity", line 205, in main
    install(args[0])
  File "/usr/lib/ubiquity/bin/ubiquity", line 58, in install
    r
et = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 370, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 927, in process_step
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquit
y/frontend/kde-ui.py", line 708, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1565, in <module>
    install.run()
  File "/usr/share/ubiq
uity/install.py", line 391, in run
    self.configure_bootloader()
  File "/usr/share/ubiquity/install.py", line 1280, in configure_bootloader
    "GrubInstaller failed with code %d" % ret)
InstallStepError: GrubInstaller failed with code 1

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 210, in <module>

main()
  File "/usr/lib/ubiquity/bin/ubiquity", line 205, in main

install(args[0])
  File "/usr/lib/ubiquity/bin/ubiquity", line 58, in install

ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 370, in run

self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 927, in process_step

self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 708, in progress_loop

(ret, realtb))
RuntimeError
:
Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1565, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 391, in run
    self.configure_bootloader()
  File "/usr/sha
re/ubiquity/install.py", line 1280, in configure_bootloader
    "GrubInstaller failed with code %d" % ret)
InstallStepError: GrubInstaller failed with code 1

----------------
Added by Duncan-Lithgow so it can be edited:
These bugs all have probelms installing GRUB on a SATA disc. Some with PATA present, some without. I do not have enough technical understanding to find exact duplicates.
Bug #8497 bug #75676 bug #32357 bug #110292

Tags: grub sata
Revision history for this message
John Carlyle-Clarke (jpcc) wrote :

After this, I tried the Alternate Install CD but had the same problem.

I already had grub installed because I had an install of Edgy in another partition, so I re-ran alternate install and told it not to install any boot loader.

Then I tried to add the new install of Feisty to the existing grub, and got some errors reported.

The problem there was that the partition was still marked as being type "NTFS", even though the installer had re-formatted it to EXT3. I used fdisk to correct the type code, and grub worked. I suspect this may have been the same reason that the installer failed above.

description: updated
Revision history for this message
Thomas David (nemphis) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

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