Partitioning error when doing normal install after encrypted lvm install

Bug #1229432 reported by Paul Larson on 2013-09-23
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
Andy Whitcroft
ubiquity (Ubuntu)

Bug Description

Image: 20130923.1 amd64 desktop

1. boot to livecd, install with lvm + encrypted selected
2. boot to live cd, install with erase and reinstall (normal install)

At the next screen (the tz selection screen) I get a popup that I can't get rid of even if I select ignore:

error informing the kernel about modifications to partition /dev/sda1 -- Device or resource busy. This means Linux won't know about any changes you made to /dev/sda1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting.
(Screenshot attached)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity 2.15.19
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CasperVersion: 1.336
Date: Mon Sep 23 21:30:51 2013
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130923.1)
MarkForUpload: True
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Paul Larson (pwlars) wrote :
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Paul Larson (pwlars) wrote :

Confirming this is still in the 20130923.2 image. Also, after a few more attempts I now believe that this doesn't have so much to do with lmv/crypt being installed previously. I was able to reproduce it again when the previous install had been a normal install. Instead. I believe it is related more to selecting live session from the *text* menu, rather than from the gui menu. If I select live from the gui menu, or if I select the install option, it seems to work ok. But if I select live session from the text menu, ubiquity never comes up after trying to launch it.

Paul Larson (pwlars) wrote :

Please ignore that last comment, it was intended for another one of the bugs I opened today... This one is certainly related to installing after lvm/crypt

Elfy (elfy) wrote :

Not sure this is specific to lvm installs - had the same without - commented on

Adam Conrad (adconrad) wrote :

FWIW, I've seen this on pure debian-installer runs as well, but I was blaming it on a potentially sketchy kernel or hardware. This is probably not a ubiquity bug, but something fundamentally goofy in partman.

Also, not necessarily related to LVM, as I've seen it installing on disks that just happened to be pre-partitioned, period. Might have something to do with the swap re-use magic?

Paul Larson (pwlars) wrote :

Yeah, I'm seeing it on server also sometimes

Manuel Cuadra (manuelcua) wrote :

I've got this error too, it only show when the installer mounts the HDD to detect another OS, if the HDD is not partitioned or no OS is installed, then it installs ok.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Scott Kitterman (kitterman) wrote :

Candidate for release notes. I believe I've had this issue when installing too and I just had to back up to the partitioning page and try again. If we can come up with a reasonable suggestion about what to do if this happens, it should definitely go in the release notes.

Andy Whitcroft (apw) wrote :

We believestrongly that the parted error emmitted here is triggered by the issue as described in bug #1240532 in ubiquity. It would be good to retest and confirm whether the final images expose this. For now I am closing the release notes tasks on the assumption this retest will be positive. Please reopen if not.

Changed in ubuntu-release-notes:
assignee: nobody → Andy Whitcroft (apw)
status: New → In Progress
status: In Progress → Invalid
Colin Watson (cjwatson) wrote :

This is indeed a duplicate of a fixed bug, but of bug 1220165, not bug 1240532.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers