[Bug 1802617] Re: After upgrade to 18.10 boot fails on waiting for encrypted source device
Neven Luetic
neven at luetic.de
Fri May 8 18:42:49 UTC 2020
First, besides the active swapfile, that caused the trouble, I found an
additional uncommented line in my fstab, referencing /dev/mapper/yoga
--vg-swap_1. Whether this was used before or is just a relict I cannot
tell.
So I went with /dev/mapper/cryptswap1, which was active; also checked
that the device really exists in /dev/mapper.
To not lose encrypted swap, I followed the advice from #10:
* uncommented swap in /etc/fstab and /etc/crypttab
* rebooted
* restored the uncommented lines
* update-initramfs -c
* update-grub
After this I could reboot without issues.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1802617
Title:
After upgrade to 18.10 boot fails on waiting for encrypted source
device
Status in cryptsetup package in Ubuntu:
Confirmed
Bug description:
After upgrading from 18.04.1 LTS to 18.10, all reboots of the system
give a boot screen with the error:
"cryptsetup: Waiting for encrypted source device /swapfile..."
After a minute or so, the graphical boot screen with that message is
replaced with a console screen reading:
"ALERT! encrypted source device /swapfile does not exist, can't unlock cryptswap1.
Check cryptopts=source= bootarg: cat /proc/cmdline
or missing modules, devices: cat /proc/modules; ls /dev
Dropping to a shell
BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _"
Typing exit at the initramfs prompt gets the boot to continue. The
boot continues to a working system and graphical login.
The system was configured in 18.04.1 LTS to have encrypted home
directories and no swap file.
It looks like the /etc/fstab got a new swapfile line somewhere during
the upgrade process. However, commenting that out and rebooting does
not affect this issue.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-release-upgrader-core 1:18.10.11.1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Fri Nov 9 20:22:09 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-12 (454 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to cosmic on 2018-11-09 (0 days ago)
VarLogDistupgradeTermlog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1802617/+subscriptions
More information about the foundations-bugs
mailing list