Failed to deactivate: Device or resource busy

Bug #1853780 reported by Jarno Suni
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd
New
Unknown
cryptsetup (Ubuntu)
Invalid
Undecided
Unassigned
Bionic
New
Undecided
Unassigned
systemd (Ubuntu)
Fix Released
Undecided
Unassigned
Bionic
New
Undecided
Unassigned

Bug Description

Fails to deactivate on shutdown

$ LC_ALL=C journalctl -b -1
Nov 23 18:49:13 jarnos-OptiPlex-745 systemd-cryptsetup[4335]: Failed to deactivate: Device or resource busy
Nov 23 18:49:13 jarnos-OptiPlex-745 systemd[1]: systemd-cryptsetup@sda5_crypt.service: Control process exited, code=exited status=1
Nov 23 18:49:13 jarnos-OptiPlex-745 systemd[1]: systemd-cryptsetup@sda5_crypt.service: Failed with result 'exit-code'.
Nov 23 18:49:13 jarnos-OptiPlex-745 systemd[1]: Stopped Cryptography Setup for sda5_crypt.
Nov 23 18:49:13 jarnos-OptiPlex-745 systemd[1]: Removed slice system-systemd\x2dcryptsetup.slice.

Seems to be this issue: https://github.com/systemd/systemd/issues/8472

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cryptsetup 2:2.0.2-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
Uname: Linux 4.15.0-70-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Nov 24 23:43:10 2019
InstallationDate: Installed on 2019-07-08 (139 days ago)
InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
cmdline: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=/dev/mapper/xubuntu--vg-root ro video=vesafb:mtrr:3,ywrap splash
crypttab: sda5_crypt UUID=5ef951e6-e0fc-4377-be56-d63ec7a865be none luks,discard

Revision history for this message
Jarno Suni (jarnos) wrote :
Changed in systemd:
status: Unknown → New
Dan Streetman (ddstreet)
tags: added: ddstreet
Dan Streetman (ddstreet)
Changed in cryptsetup (Ubuntu):
status: New → Invalid
Changed in systemd (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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