Your message dated Fri, 16 Dec 2016 05:51:58 +0100
with message-id <[email protected]>
and subject line Re: Bug#751585: systemd: opens emergency shell after prompting
for unnecessary dm-crypt passwords
has caused the Debian Bug report #751622,
regarding systemd: shows unnecessary password prompts for encrypted disks
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
751622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751622
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 204-10
Severity: critical
After installing systemd today and rebooting, I saw a few lines (not
errors) about systemd-fsck on xfs filesystems, and then I was prompted
for dm-crypt passwords for 4 disks that are not necessary to boot the
system. I pressed enter to bypass each prompt, and then saw I message
that I'd be dropped to an emergency shell. It took about a minute to
open this shell each time (the shell died a few times while I was
working).
The disks it had prompted about were marked 'noauto' in /etc/crypttab,
and all had keyfiles available on the root filesystem (which is
encrypted but had been successfully mounted at the time); so no prompts
should have been shown.
I've marked this as critical because I was unable to use the system
until switching back to sysvinit. Unfortunately, no logs of the event
seem to be available now, so it's not clear why systemd considered there
to be an emergency.
- Michael
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-1
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-53
ii libacl1 2.2.52-1
ii libaudit1 1:2.3.6-1
ii libc6 2.19-1
ii libcap2 1:2.22-1.2
ii libcap2-bin 1:2.22-1.2
ii libcryptsetup4 2:1.6.4-4
ii libdbus-1-3 1.8.2-1
ii libgcrypt11 1.5.3-4
ii libkmod2 17-2
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.8-3
ii libselinux1 2.3-1
ii libsystemd-daemon0 204-10
ii libsystemd-journal0 204-10
ii libsystemd-login0 204-10
ii libudev1 204-10
ii libwrap0 7.6.q-25
ii sysv-rc 2.88dsf-53
ii udev 204-10
ii util-linux 2.20.1-5.8
Versions of packages systemd recommends:
pn libpam-systemd <none>
Versions of packages systemd suggests:
pn systemd-ui <none>
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Sat, 14 Jun 2014 16:41:37 -0400 Michael Gold <[email protected]>
wrote:
> severity 751585 normal
> clone 751585 -1 -2 -3
> retitle -1 systemd: shows unnecessary password prompts for encrypted disks
> severity -1 normal
> retitle -2 systemd: should print reason for starting emergency shell
> severity -2 wishlist
> retitle -3 systemd: emergency shell takes several minutes to start
> severity -3 normal
> thanks
>
> On Sat, Jun 14, 2014 at 17:30:30 +0200, Michael Biebl wrote:
> > Thanks.
> > I noticed that you don't have those crypt devices marked as noauto (or
> > nofail) in /etc/fstab.
> > This means, if they fail to show up during boot systemd will drop you in
> > an emergency shell (which is what happened in your case).
> >
> > Try booting with systemd where those devices are marked accordingly in
> > fstab.
>
> It turns that /media/bootkey was missing, and putting "nofail" there got
> the system booting successfully. This was just a regular unencrypted
> USB flash drive, which had spontaneously zeroed itself a few months ago
> but was still listed in my fstab. Running journalctl showed a message
> about it, but it wasn't obvious--there was some similarly-highlighted
> text about a missing /bin/plymouth (apparently not an actual problem)
> and a bunch of other verbosity that filled up the screen.
Ok, so this was a misconfiguration. The release-notes [1] talk about
this issue, so closing this bug report
Regards,
Michael
[1]
https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.de.html#systemd-auto-mounts-incompat
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
