[Bug 1045812] Re: Partitioner failed with "Failed to partition hard drive" with LVM selected

Launchpad Bug Tracker 1045812 at bugs.launchpad.net
Tue Sep 4 18:11:38 UTC 2012

This bug was fixed in the package ubiquity - 2.11.29

ubiquity (2.11.29) quantal; urgency=low

  [ Colin Watson ]
  * Fix missing parentheses that caused removable installation media
    sometimes to be selected as the default GRUB device (LP: #987418).
  * Update translations from Launchpad (LP: #1045695).

  [ Dmitrijs Ledkovs ]
  * Automatic update of included source packages: partman-auto-lvm
    45ubuntu2. (LP: #1045812)
 -- Dmitrijs Ledkovs <dmitrij.ledkov at ubuntu.com>   Tue, 04 Sep 2012 18:48:04 +0100

** Changed in: ubiquity (Ubuntu)
       Status: Triaged => Fix Released

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to partman-auto-lvm in Ubuntu.

  Partitioner failed with "Failed to partition hard drive" with LVM

Status in “partman-auto-lvm” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Fix Released

Bug description:
  Quantal Desktop 20120903.4

  1. Boot from Quantal Desktop ISO
  2. At ubiquity-dm select "French" and press "Essayer Ubuntu"
  3. Let the live session start and start ubiquity
  4. Proceed to partman and check "LVM"
  5. Press "Continue"

  Expected Result:
  Installation continue

  Actual Result:
  This failure with the error message in attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity 2.11.28 [modified: lib/partman/automatically_partition/question]
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.321
  Date: Tue Sep  4 13:08:09 2012
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120903.4)
   PATH=(custom, no user)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list