Device or resource busy on shutdown

asked 2017-03-23 07:42:18 -0500

lhsm gravatar image

I have been experiencing some shutdown problems with my Fedora 25 Workstation. I am using LVM with Luks on a SSD, and I have seen this problem happening on a Debian, Ubuntu and Arch on same laptop.

Problem

I never figured out what is happening, and the problem happens almost every shutdown, then, I have to force the laptop halt by pressing the power off button. I do not know how to monitor if the system services, such as postgresl and bumblebee are property stopping, or stopping before the system to unmount the disk.

I also have this log:

mar 22 23:12:23 laptop systemd-journald[767]: Journal stopped
mar 22 23:12:23 laptop systemd-shutdown[1]: Sending SIGTERM to remaining processes...
mar 22 23:12:23 laptop systemd[1]: Shutting down.
mar 22 23:12:23 laptop systemd[1]: Starting Power-Off...
mar 22 23:12:23 laptop systemd[1]: Reached target Final Step.
mar 22 23:12:23 laptop systemd[1]: Reached target Shutdown.
mar 22 23:12:23 laptop systemd[1]: Removed slice system-systemd\x2dcryptsetup.slice.
mar 22 23:12:23 laptop kernel: audit: type=1130 audit(1490235143.176:803): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@luks\x2daa1f1230\x2d001e\x2d41e
mar 22 23:12:23 laptop kernel: audit_printk_skb: 30 callbacks suppressed
mar 22 23:12:23 laptop systemd[1]: Reached target Unmount All Filesystems.
mar 22 23:12:23 laptop systemd[1]: systemd-cryptsetup@luks\x2daa1f1230\x2d001e\x2d41e7\x2d94c1\x2de2ba60844095.service: Failed with result 'exit-code'.
mar 22 23:12:23 laptop systemd[1]: systemd-cryptsetup@luks\x2daa1f1230\x2d001e\x2d41e7\x2d94c1\x2de2ba60844095.service: Unit entered failed state.
mar 22 23:12:23 laptop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@luks\x2daa1f1230\x2d001e\x2d41e7\x2d94c1\x2de2ba60844095 co
mar 22 23:12:23 laptop systemd[1]: Stopped Cryptography Setup for luks-aa1f1230-001e-41e7-94c1-e2ba60844095.
mar 22 23:12:23 laptop systemd[1]: systemd-cryptsetup@luks\x2daa1f1230\x2d001e\x2d41e7\x2d94c1\x2de2ba60844095.service: Control process exited, code=exited status=1
mar 22 23:12:23 laptop systemd-cryptsetup[12325]: Failed to deactivate: Device or resource busy
mar 22 23:12:20 laptop systemd[1]: Received SIGRTMIN+20 from PID 12230 (plymouthd).
mar 22 23:12:20 laptop kernel: device-mapper: ioctl: unable to remove open device luks-aa1f1230-001e-41e7-94c1-e2ba60844095
mar 22 23:12:19 laptop kernel: device-mapper: ioctl: unable to remove open device luks-aa1f1230-001e-41e7-94c1-e2ba60844095
mar 22 23:12:19 laptop kernel: device-mapper: ioctl: unable to remove open device luks-aa1f1230-001e-41e7-94c1-e2ba60844095
mar 22 23:12:19 laptop kernel: device-mapper: ioctl: unable to remove open device luks-aa1f1230-001e-41e7-94c1-e2ba60844095
mar 22 23:12:19 laptop kernel: device-mapper: ioctl: unable to remove open device luks-aa1f1230-001e-41e7-94c1-e2ba60844095
mar 22 23:12:19 laptop kernel: device-mapper: ioctl: unable to remove open device luks-aa1f1230-001e-41e7-94c1-e2ba60844095
mar 22 23:12:18 laptop kernel: device-mapper: ioctl: unable to remove open device luks-aa1f1230-001e-41e7-94c1-e2ba60844095
mar 22 23:12:18 laptop kernel: device-mapper: ioctl: unable to remove open device luks-aa1f1230-001e-41e7-94c1-e2ba60844095
mar 22 23:12:18 laptop kernel ...
(more)
edit retag flag offensive close merge delete