ubiquity

Installer crashes when installing over existing LUKS or LVM

Bug #1727956 reported by Aku Pietikäinen on 2017-10-27

This bug affects 10 people

Affects		Status	Importance	Assigned to	Milestone
	ubiquity	New	Undecided	omid
	ubiquity (Ubuntu)	Fix Released	Critical	Unassigned

Bug Description

Trying to install Ubuntu over existing LUKS full disk encryption. Installer crashes when running grub-installer to /dev/dm-0.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CasperVersion: 1.380
Date: Fri Oct 27 10:24:45 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
TERM=unknown
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Aku Pietikäinen (daku) wrote on 2017-10-27:

Casper.txt Edit (1013 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (6.6 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (121.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
UbiquityDebug.txt Edit (29.7 KiB, text/plain; charset="utf-8")
UbiquityDm.txt Edit (3.6 KiB, text/plain; charset="utf-8")
UbiquityPartman.txt Edit (522.6 KiB, text/plain; charset="utf-8")
UbiquitySyslog.txt Edit (1.0 MiB, text/plain; charset="utf-8")

Revision history for this message

Phillip Susi (psusi) wrote on 2017-11-09:

Confirmed: having an existing LUKS or LVM install and trying to reinstall over it causes ubiquity to try to install grub to /dev/dm-0 instead of /dev/sda, which fails.

summary:	- Installer crashes when installing over existing LUKS encryption + Installer crashes when installing over existing LUKS or LVM
Changed in grub-installer (Ubuntu):
importance:	Undecided → Critical
status:	New → Triaged

Phillip Susi (psusi) on 2017-11-15

affects:

grub-installer (Ubuntu) → ubiquity (Ubuntu)

Revision history for this message

Sebastian Mangels (sebastian.mangels) wrote on 2019-02-22:

Hi there,

I'm new here so I do not know if posting a comment is the right way to check the status of this issue. Apologies if not.

As far as I understand the status of this issue it has not yet been fixed. Is there any workaround for this?

I am exyperimenting with

d-i grub-installer/bootdev string (hd0,1)

to force installing grub on the first harddisk.

But it does not seem to do the trick.

Is there anything else I can do as a workaround? Download another boot image? Anything?

omid (omidabdollahi52) on 2020-01-14

Changed in ubiquity:
assignee:	nobody → omid (omidabdollahi52)
Changed in ubiquity (Ubuntu):
status:	Triaged → Fix Released

Revision history for this message

clickwir (clickwir) wrote on 2020-01-14:

Fix Released?

omid is a new user as of 1-14-2020 and (without any details) says a fix is released.

Can we get some more information or confirmation this change was on purpose?

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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