26.06.2016 05:00, Michael Biebl пишет: > Hi, > > I'm using a luks encrypted lvm setup. One volume group which is > unlocked in the intramfs (initramfs-tools), and logical volumes for /, > /home and swap. > > > On shutdown I get > Jun 26 03:35:30 pluto systemd[1]: Stopped target Local File Systems. > Jun 26 03:35:30 pluto systemd[1]: Unmounting /boot... > Jun 26 03:35:30 pluto systemd[1]: Unmounting Temporary Directory... > Jun 26 03:35:30 pluto systemd[1]: Unmounting /home... > Jun 26 03:35:30 pluto systemd[1]: Unset automount mnt-data.automount. > Jun 26 03:35:30 pluto systemd[1]: Unmounting /run/user/109... > Jun 26 03:35:30 pluto systemd[1]: Unmounted Temporary Directory. > Jun 26 03:35:30 pluto systemd[1]: Unmounted /run/user/109. > Jun 26 03:35:30 pluto systemd[1]: Unmounted /boot. > Jun 26 03:35:30 pluto systemd[1]: Stopped File System Check on > /dev/disk/by-uuid/78cfffe0-a86e-4345-bb5e-98be4226e334. > Jun 26 03:35:30 pluto systemd[1]: Unmounted /home. > Jun 26 03:35:30 pluto systemd[1]: Stopped File System Check on > /dev/mapper/vg-home. > Jun 26 03:35:30 pluto systemd[1]: Removed slice system-systemd\x2dfsck.slice. > Jun 26 03:35:30 pluto systemd[1]: Stopped target Local File Systems (Pre). > Jun 26 03:35:30 pluto systemd[1]: Stopped Create Static Device Nodes in /dev. > Jun 26 03:35:30 pluto systemd[1]: Stopping Monitoring of LVM2 mirrors, > snapshots etc. using dmeventd or progress polling... > Jun 26 03:35:30 pluto systemd[1]: Stopped Remount Root and Kernel File > Systems. > Jun 26 03:35:30 pluto lvm[2585]: 5 logical volume(s) in volume group > "vg" unmonitored > Jun 26 03:35:30 pluto systemd[1]: Stopped Monitoring of LVM2 mirrors, > snapshots etc. using dmeventd or progress polling. > Jun 26 03:35:30 pluto systemd[1]: Stopping LVM2 metadata daemon... > Jun 26 03:35:30 pluto systemd[1]: Stopped LVM2 metadata daemon. > Jun 26 03:35:35 pluto systemd-cryptsetup[2542]: Failed to deactivate: > Device or resource busy > Jun 26 03:35:35 pluto systemd[1]: > systemd-cryptsetup@sda5_crypt.service: Control process exited, > code=exited status=1 > Jun 26 03:35:35 pluto systemd[1]: Stopped Cryptography Setup for sda5_crypt. > Jun 26 03:35:35 pluto systemd[1]: > systemd-cryptsetup@sda5_crypt.service: Unit entered failed state. > Jun 26 03:35:35 pluto systemd[1]: > systemd-cryptsetup@sda5_crypt.service: Failed with result 'exit-code'. > Jun 26 03:35:35 pluto systemd[1]: Reached target Unmount All Filesystems. > Jun 26 03:35:35 pluto systemd[1]: Removed slice > system-systemd\x2dcryptsetup.slice. > Jun 26 03:35:35 pluto systemd[1]: Reached target Shutdown. > Jun 26 03:35:35 pluto systemd[1]: Reached target Final Step. > Jun 26 03:35:35 pluto systemd[1]: Starting Halt... > Jun 26 03:35:35 pluto systemd[1]: Shutting down. > Jun 26 03:35:35 pluto systemd-shutdown[1]: Sending SIGTERM to > remaining processes... > Jun 26 03:35:35 pluto systemd-journald[397]: Journal stopped > > And idea why the systemd-cryptsetup service fails and how I can fix this? >
You obviously cannot deactivate crypto container that has your root. The only fix here is to exempt it from stopping on shutdown or return to initramfs to do it. _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
