Failed to install Edgy on 2GB USB pendrive

Bug #67376 reported by dogged
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Using the CD iso preceding RC1, I optimistically tried to install to a 2GB USB pendrive. It spent the better part of 3 hours copy files over from the CD to the pendrive. It was my second attempt, where the first had tried (and failed) to install GRUB to (hd0). This time I asked it to install (sd0) but it didn't manage that, falling off a long way into the installation. Serves me right I suppose for trying to run Edgy as my main system, without reformatting my whole hard drive. (I *think* I've been using ntfs for the past few years, but the first few dozen KB are inaccessible.)

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 123, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 328, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 790, in process_step
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 568, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s\n%s" %
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1347, in ?
    install.run()
  File "/usr/share/ubiquity/install.py", line 365, in run
    self.configure_bootloader()
  File "/usr/share/ubiquity/install.py", line 1070, in configure_bootloader
    raise InstallStepError(
InstallStepError: GrubInstaller failed with code 1

Revision history for this message
dogged (r-m) wrote :

/var/log/partman

Revision history for this message
dogged (r-m) wrote :

/var/log/syslog

Revision history for this message
Jeff Greene (jeffgreene) wrote :
Nanley Chery (nanoman)
Changed in ubiquity:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

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