crash when reinstalling broken lubuntu install - encrypted home on separate partition

Bug #1509877 reported by Xvani
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Critical
Unassigned
Nominated for Wily by Alberto Salvia Novella

Bug Description

Previous install was a 15.04 that upgraded to 15.10, but failed and now I get black screen on boot.

crash occured when reinstalling broken lubuntu 15.10 install - encrypted home on separate partition.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubiquity 2.21.37
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
ApportVersion: 2.19.1-0ubuntu3
Architecture: i386
CasperVersion: 1.365
Date: Sun Oct 25 18:00:31 2015
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Xvani (fredrile+launchpad) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
GizmoChicken (gizmochicken) wrote :

Although perhaps not a "duplicate" of Bug #1523194 that I reported, the two bugs at least seems related.

Have you tried installing only into boot (/boot) and root (/), and then moving home to a separate auto-mountable encrypted partition after installation has completed? (To get this to work, you'll also need to skip creating a swap partition during installation, and then create a swap partition, or a swap file, once installation has completed.)

For more details, see https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1523194

Changed in ubiquity (Ubuntu):
importance: Undecided → Critical
Revision history for this message
GizmoChicken (gizmochicken) wrote :

This bug may also be related to Bug #1531387.

Revision history for this message
Phillip Susi (psusi) wrote :

You appear to be trying to upgrade an existing installation that is broken. You will need to repair the existing installation, or do a clean install instead of an upgrade.

Changed in ubiquity (Ubuntu):
status: Confirmed → Invalid
Changed in ubiquity (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
GizmoChicken (gizmochicken) wrote :

The existing installation isn't broken. Rather, it is also not possible to install /home into separate LUKS encrypted volume during upgrade OR during a clean install. I've tried with Ubuntu 15.10 and 16.04, Lubuntu 15.10, and Kubuntu 15.10. Please see Bug #1523194 for my report regarding Ubuntu.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Bug #1066480 could be related.

Changed in ubiquity (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Phillip Susi (psusi) wrote :

They are separate issues and this one is still invalid for the reason mentioned before. Even if they are the same, we don't need two bug reports on the same thing.

Changed in ubiquity (Ubuntu):
status: Triaged → Invalid
Revision history for this message
GizmoChicken (gizmochicken) wrote :

Phillip,

I don't mean to speak for the original reporter of this bug. But my guess is that his mention of reinstalling a "broken" installation is a bit of a distracting.

As I reported in Bug #1523194, even during a clean install, I am unable to install /home into separate LUKS encrypted volume. Moreover, I have noticed that I am unable to upgrade from a working (non-broken) installation of Ubuntu 15.04 in which /home has been previously installed into separate LUKS encrypted volume, which bug sounds an awful lot like the bug reported here.

A you suggest, if they are the same, we don't need two bug reports on the same thing.

Although this bug was reported first, given that original reporter of this bug hasn't commented since his first post, I marked this bug as a duplicate of Bug #1523194, which I hope will remain active until a fix is released.

Best regards,
GizmoChicken

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.