Ubiquity installer crashes with manual partition layout - looks like a regression
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
If one manually creates a partition layout (btrfs on dm-crypt) and starts the ubiquity installer, one is able to select all partitons and set everything up as desired. Upon starting the actual installation (when filesystems get set up/created/mounted) ubiquity crashes It displays the timezone dialog briefly before that.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.3
ProcVersionSign
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.347
CurrentDesktop: KDE
Date: Mon Jan 12 19:56:26 2015
InstallCmdLine: file=/cdrom/
LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150112)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
Please excuse, that I did not got to a workaround before reporting this bug.
It is indeed possible to have a custom partition layout with the ubiquity installer on the KDE Live CD, when the layout is created manually. If the deisred root ("/") filesystem is btrfs it needs to be completely fresh or created by the installer.
The reason for the issue seems to be that I had a custom subvolume ("sv_root") and that I set that subvolume as the default subvolume to mount. Whereas the installer wants to use a subvolume named "@" as the system's root. There seems to be no way to deviate from this during installation.
I perfectly understand that names are a question of taste. Yet there is no reason to not support custom subvolume names.
To get a working system: tools/conf. d/cryptroot file; this is the step I missed at first
* Do not select updates/extras
* Open manually created LVM/dm-crypt volumes
* Select your volumes - choose to format your /boot-device and the device containing /
* Install
* The installer crashes when it needs to install the bootloader (at least it looks that way)
* Quit the installer
* Mount the target into /target with dev, dev/pts, proc, sys, boot; this needs to match the planned layout, which will be put in fstab and crypttab, *EXACTLY*
* Add /etc/crypttab to reflect the crypted devices correctly
* Edit /etc/fstab to reflect the system correctly
* Create /etc/initramfs-
* update-initramfs -u -k all
* update-grub
* Unmount everything
* reboot
Thank you for taking the time to read this report. Please forgive my grammar, since I am not a native speaker.