19.04 lubuntu install - Full disk install with encryption on a EFI system without secure boot resulted in gnu-grub

[Chris Guiver]

Lubuntu 19.04 x86_64 install
Working on https://phab.lubuntu.me/w/release-team/testing-checklist/?v=17
Install : "Full disk install with encryption on a EFI system without secure boot"
System : sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT)

Install was as expected; on reboot however I was at GNU Grub version .. Minimal BASH ..

It has not been re-attempted (the install), and I can't recall what I saw when I rebooted the thumb-drive (apologies, I was meant to look before I started next install for next item on the checklist) so it will have been destroyed already.

If useful, I'll perform the install again on request to gain more information.

This `ubuntu-bug` report was on same device using 'live' media; but logs will not be useful on anything specific sorry.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: calamares 3.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
.etc.calamares.modules.automirror.conf:
 ---
 baseUrl: archive.ubuntu.com
 distribution: Lubuntu
 geoIpUrl: https://ipapi.co/json
.etc.calamares.modules.finished.conf:
 ---
 restartNowChecked: true
 restartNowEnabled: true
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.partition.conf:
 efiSystemPartition: "/boot/efi"
 enableLuksAutomatedPartitioning: true
 neverCreateSwap: true
 drawNestedPartitions: true
.etc.calamares.modules.shellprocess_logs.conf:
 ---
 dontChroot: true
 timeout: 30
 script:
     - calamares-logs-helper @@ROOT@@
.etc.calamares.modules.unpackfs.conf:
 ---
 unpack:
     - source: "/cdrom/casper/filesystem.squashfs"
         sourcefs: "squashfs"
         destination: ""
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CasperVersion: 1.402
CurrentDesktop: LXQt
Date: Sat Mar 30 08:30:51 2019
LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:19.04.3
 calamares-settings-lubuntu 1:19.04.3
 xfsprogs 4.15.1-1ubuntu1
 btrfs-progs 4.20.2-1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu QA Website (ubuntuqa)]

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

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1822409

[Chris Guiver (guiverc)]

Attempted again on box :
sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT)

using Lubuntu 19.04 daily x86_64 (20190330)
install, reboot & gnu grub 2.02 minimal bash..

Another attempt again on box
using Lubuntu 19.04 daily x86_64 (20190330)
sudo add-apt-repository ppa:lubuntu-ci/unstable-ci
sudo apt full-upgrade
logout, login again then install
again result after reboot is gnu grub 2.02 minimal bash..

[Chris Guiver (guiverc)]

I have booted the live-installer & then opened the sdd using `pcmanfm-qt`, I was asked for my passphrase 'please' and it opened the partition. All looks like I believe it should (for an installed system).

I don't know how it's supposed to get me to unlock the partition (ie. asking for my 'please' passphrase) but that did not occur.

Some detail from `fdisk -l`

Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Disk model: SAMSUNG MZNTD128
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C75ABBF3-6D94-4CD6-8AF5-F16EE2A7630F

Device Start End Sectors Size Type
/dev/sda1 4096 618495 614400 300M EFI System
/dev/sda2 618496 250067789 249449294 119G Linux filesystem

Other commands I felt may be helpful (EFI directories)

lubuntu@lubuntu:~$ sudo mount /dev/sda1 /mnt

lubuntu@lubuntu:/mnt/EFI$ ls -la
total 16
drwxr-xr-x 4 root root 4096 Mar 31 20:04 .
drwxr-xr-x 3 root root 4096 Jan 1 1970 ..
drwxr-xr-x 2 root root 4096 Mar 31 20:04 BOOT
drwxr-xr-x 2 root root 4096 Mar 31 20:04 ubuntu

lubuntu@lubuntu:/mnt/EFI$ ls -la ubuntu/ BOOT/
BOOT/:
total 3852
drwxr-xr-x 2 root root 4096 Mar 31 20:04 .
drwxr-xr-x 4 root root 4096 Mar 31 20:04 ..
-rwxr-xr-x 1 root root 1447800 Mar 31 20:04 BOOTX64.EFI
-rwxr-xr-x 1 root root 1213032 Mar 31 20:04 fbx64.efi
-rwxr-xr-x 1 root root 1269496 Mar 31 20:04 mmx64.efi

ubuntu/:
total 3976
drwxr-xr-x 2 root root 4096 Mar 31 20:04 .
drwxr-xr-x 4 root root 4096 Mar 31 20:04 ..
-rwxr-xr-x 1 root root 108 Mar 31 20:04 BOOTX64.CSV
-rwxr-xr-x 1 root root 117 Mar 31 20:04 grub.cfg
-rwxr-xr-x 1 root root 1447800 Mar 31 20:04 grubx64.efi
-rwxr-xr-x 1 root root 1269496 Mar 31 20:04 mmx64.efi
-rwxr-xr-x 1 root root 1334816 Mar 31 20:04 shimx64.efi

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

As it turns out, this was a double-whammy. The new Calamares used a cryptsetup that defaulted to luks2, which grub2 does not support. Ubiquity gets around this by using an unencrypted /boot (ewww). However, you can get cryptsetup to explicitly use one version or the other of luks rather than relying on whatever the default version is. The library used to partition, kpmcore, was modified to do exactly this. Problem fixed:

kpmcore (3.3.0-5) unstable; urgency=medium

  * Use luks1 format only

 -- Jonathan Carter <email address hidden> Sat, 06 Apr 2019 12:40:05 +0200