On Wed, Mar 29, 2017 at 06:35:35AM +0200, Michael Biebl wrote: > Am 29.03.2017 um 06:03 schrieb Nathan Dorfman: > > Package: systemd > > Version: 232-19 > > Followup-For: Bug #848044 > > > > Just tried a fresh install using the stretch rc2 amd64 netinst ISO, > > and the guided/entire-disk LVM+LUKS install option. > > > > There's no delay at shutdown, but there are errors about stopping > > dm-crypt and LVM; see attached screenshot. These consistently > > occur at every shutdown, and so far, seem harmless. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854699
Thanks, Michael. I tried your test packages, and the first thing I noticed is that the shutdown messages are no longer visible; instead, I see some corrupted fragments of the startup messages (screenshot attached). The system still rebooted after a couple of seconds as expected, though. Anyway, I'm running with the persistent journal enabled, so I was able to look at journalctl -ab-1. Most of the errors are gone, but the final error, about systemd-cryptsetup@vda5_crypt.service, remains. Strangely, I see no mention of any kind of fsck of / in any of the journals -- might you happen to know why that would be, or how I can verify whether or not it was found to be clean? (I see the fscheck for /boot, on /dev/vda1, but not / on /dev/mapper/stretch--vg-root.) I've attached the full output of journalctl -ab-1, which is with your test packages, as well as the same from the last boot without them. To summarize, these are the errors that are no longer present with your changes: Mar 28 23:20:39 stretch systemd[1]: Stopped Create Volatile Files and Directories. Mar 28 23:20:39 stretch systemd[1]: Reloading. Mar 28 23:20:39 stretch systemd[1]: Stopped (with error) /dev/disk/by-id/dm-name-vda5_c rypt. Mar 28 23:20:39 stretch systemd[1]: Stopped (with error) /dev/disk/by-id/dm-uuid-CRYPT- LUKS1-f96f4a3e07a84aa48123d83ba6c24f53-vda5_crypt. Mar 28 23:20:39 stretch systemd[1]: Stopped (with error) /sys/devices/virtual/block/dm- 0. Mar 28 23:20:39 stretch systemd[1]: Stopped (with error) /dev/dm-0. Mar 28 23:20:39 stretch systemd[1]: Stopped (with error) /dev/mapper/vda5_crypt. Mar 28 23:20:39 stretch systemd[1]: Stopped (with error) /dev/disk/by-id/lvm-pv-uuid-ozNpTU-66St-dPt6-SXcq-BDtH-hwD1-hFXNvD. Mar 28 23:20:39 stretch systemd[1]: Stopped Raise network interfaces. And these are the ones that still are: Mar 28 23:49:59 stretch systemd[1]: Stopping LVM2 metadata daemon... Mar 28 23:49:59 stretch lvmetad[287]: Failed to accept connection errno 11. Mar 28 23:49:59 stretch systemd[1]: Stopped LVM2 metadata daemon. Mar 28 23:50:04 stretch systemd-cryptsetup[1075]: Failed to deactivate: Device or resource busy Mar 28 23:50:04 stretch systemd[1]: systemd-cryptsetup@vda5_crypt.service: Control process exited, code=exited status=1 Mar 28 23:50:04 stretch systemd[1]: Stopped Cryptography Setup for vda5_crypt. Mar 28 23:50:04 stretch systemd[1]: systemd-cryptsetup@vda5_crypt.service: Unit entered failed state. Mar 28 23:50:04 stretch systemd[1]: systemd-cryptsetup@vda5_crypt.service: Failed with result 'exit-code'. Mar 28 23:50:04 stretch systemd[1]: Reached target Unmount All Filesystems. -nd.
journalctl-ab-1_testpkgs.txt.gz
Description: application/gzip
journalctl-ab-6_unmodified.txt.gz
Description: application/gzip
