Xenial fails to boot because of cryptsetup keyfiles.

[Arbiel Perlacremaz]

I always install fresh configurations apart from my working system, on logical volumes of my "victor" logical group. I always use four logical volumes per distribution : boot (clear), root (crypted), home (crypted) and usr (clear), naming them differently from a distribution to another one. Xenial logical volumes are archos (boot), odos (root), oikia (home) and trophe (usr). Only odos and oikia are concerned.

To avoid typing cryptsetup keys, I rely on keyfiles. It turns out that, for reasons outside of this report, I did install grub on removable USB keys, and did not alter Windows booting procedure on my hard disk. I also record my key-files on that same device. This means that my USB key is always connected to my PC when I boot Ubuntu.

My working system is Ubuntu Trusty with the 3.13.0.106-generic kernel. It does not suffer the bug I'm reporting (I discarted 3.13.0.108-generic for a reason I forgot, but it also works, as regards to the present report).

Xenial does not boot, apparently because it hangs waiting for the USB device. The present bug is then a regression bug.

I attached the output of "journalctl -xb" in which one can read (I translated french sentences in brakets[])

###########################################################
-- L'unité (unit) boot.mount a commencé à démarrer. [unit boot.mount started]
mars 25 12:22:37 remi-Vostro-3550 systemd-udevd[666]: Process '/sbin/crda' failed with exit code 249.
mars 25 12:22:37 remi-Vostro-3550 kernel: EXT4-fs (dm-12): mounting ext2 file system using the ext4 subsystem
mars 25 12:22:37 remi-Vostro-3550 kernel: EXT4-fs (dm-12): mounted filesystem without journal. Opts: (null)
mars 25 12:22:37 remi-Vostro-3550 systemd[1]: Mounted /boot.
-- Subject: L'unité (unit) boot.mount a terminé son démarrage [unit boot.mount has finished]
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- L'unité (unit) boot.mount a terminé son démarrage, avec le résultat done.[unit boot.mount has finished and reported done]
mars 25 12:23:58 remi-Vostro-3550 systemd[1]: dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device: Job dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device/start timed out.
mars 25 12:23:58 remi-Vostro-3550 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device.
-- Subject: L'unité (unit) dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device a échoué [unit dev-disk…-victor\x2dodos:1.device failed]
-- Defined-By: systemd
############################################################

For testing purposes, I also installed a Xenial-B on a clear logical volume. I have being able, after boot of Xenial-B, to "cryptdisks_start" crypted logical volumes defined with the crypttab's "noauto" option.

Removing the "noauto" option, without mounting the corresponding volumes with fstab, did not prevent Xenial-B to boot, but the same message as the one I mentionned ealier, appeared into the "journalctl -xb" output.

I also discovered that cryptdisks_start fails if the USB key happens to be mounted.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-106-generic 3.13.0-106.153
ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
Uname: Linux 3.13.0-106-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: remi 3564 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Mar 28 22:15:20 2018
InstallationDate: Installed on 2014-05-30 (1397 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Vostro 3550
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-106-generic root=/dev/mapper/victor-root ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-106-generic N/A
 linux-backports-modules-3.13.0-106-generic N/A
 linux-firmware 1.127.23
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3550
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc7

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]