[Regression] Installing to USB drive, proposes MBR to be written to internal disk

Bug #549756 reported by komputes
82
This bug affects 20 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Colin Watson
Lucid
Fix Released
High
Colin Watson

Bug Description

Binary package hint: ubiquity

I am using Ubiquity to install to USB Drive.

At the partitioning step I chose to use the entire disk and point it to the USB stick.

At the last step I click I the advanced option says /dev/sda instead of /dev/sdb. Changing it to /dev/sdb using the contextual menu fails and does not change the drive. User must click on the text field and manually type sdb.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: ubiquity 2.2.9
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Sat Mar 27 13:58:48 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.utf8
 SHELL=/bin/bash
SourcePackage: ubiquity

Revision history for this message
komputes (komputes) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Confirmed, this can be easily reproduced. Marking as Medium importance since this bug has a strong potential for data destruction in the case someone was to try such an action.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Evan (ev)
Changed in ubiquity (Ubuntu):
assignee: nobody → Evan Dandrea (ev)
milestone: none → ubuntu-10.04.1
Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu):
importance: Medium → High
Changed in ubiquity (Ubuntu Lucid):
status: New → Triaged
assignee: nobody → Evan Dandrea (ev)
importance: Undecided → High
milestone: none → ubuntu-10.04.1
Changed in ubiquity (Ubuntu):
status: Confirmed → Triaged
milestone: ubuntu-10.04.1 → none
Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu):
assignee: Evan Dandrea (ev) → Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu Lucid):
assignee: Evan Dandrea (ev) → Colin Watson (cjwatson)
tags: added: iso-testing
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted ubiquity into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in ubiquity (Ubuntu Lucid):
status: Triaged → Fix Committed
tags: added: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.3.3

---------------
ubiquity (2.3.3) maverick; urgency=low

  [ Mario Limonciello ]
  * Disable the "Installing the System" title before Ubiquity comes up
    in automatic mode to prevent confusion before it actually does damage
    in case there are any confirmation screens that should come up first.
  * Allow setting a custom title via ubiquity/custom_title_text.
  * If a package that was marked for installation is upgradable (and thus
    already installed), mark it for upgrade. (LP: #604585)
  * install.py: Update APT usage from deprecated functions and variables.
  * Automatic update of included source packages: bterm-unifont 1.2,
    flash-kernel 2.28ubuntu4, grub-installer 1.49ubuntu12, partman-auto
    91ubuntu3.

  [ Colin Watson ]
  * Refactor default boot device calculation, bringing it into sync with
    grub-installer. This should ensure that when installing to a removable
    device we always default to installing GRUB to that same device as well,
    while leaving the situation for installations to hard disks unchanged
    (LP: #549756).
 -- Mario Limonciello <email address hidden> Sat, 24 Jul 2010 17:49:20 -0500

Changed in ubiquity (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
databubble (phil-linttell) wrote :

I believe this is actually a duplicate of the earlier bug #414996, marked critical against grub2 (do to it's potential for data loss or making a system unable to boot.) However, I've marked the earlier bug as duplicate as this likely correctly identifies ubiquity as the project.

Revision history for this message
Robbie Williamson (robbiew) wrote :

This fix for Lucid (10.04) was verified by komputes.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.2.25

---------------
ubiquity (2.2.25) lucid-proposed; urgency=low

  * Refactor default boot device calculation, bringing it into sync with
    grub-installer. This should ensure that when installing to a removable
    device we always default to installing GRUB to that same device as well,
    while leaving the situation for installations to hard disks unchanged
    (LP: #549756).
 -- Colin Watson <email address hidden> Fri, 23 Jul 2010 16:50:40 +0100

Changed in ubiquity (Ubuntu Lucid):
status: Fix Committed → Fix Released
Revision history for this message
komputes (komputes) wrote :

I have tested the 10.04.1 pre-release daily and this seems to be fixed. Fix confirmed.

arturm (arturm)
Changed in ubiquity (Ubuntu Lucid):
status: Fix Released → Confirmed
Omer Akram (om26er)
Changed in ubiquity (Ubuntu Lucid):
status: Confirmed → Fix Released
Changed in ubiquity (Ubuntu Lucid):
status: Fix Released → Fix Committed
Steve Langasek (vorlon)
Changed in ubiquity (Ubuntu Lucid):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.