Bug#920234: systemd: insufficient log options when there is a bad /etc/crypttab entry

[Michael Biebl]

On Wed, 23 Jan 2019 11:42:57 +1100 Russell Coker <russell at coker.com.au>
wrote:
> Package: systemd
> Version: 240-4
> Severity: normal
> 
> When I have a bogus /etc/crypttab entry (for example when converting an
> encrypted laptop to a virtual machine that's not encrypted) the boot process
> hangs for 90 seconds for no obvious reason.
> 
> [    **] A start job is running for /dev/dis·9597-dbdb2fedbd1f (24s / 1min 30s)
> 
> When seeing the above anyone who doesn't know that "grep -R dbdb2fedbd1f /etc"
> is necessary will have trouble determining the cause of this.
> 
> # systemd-analyze blame
> Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
> Please try again later.
> Hint: Use 'systemctl list-jobs' to see active jobs
> # systemctl list-jobs
> JOB UNIT                                                           TYPE  STATE  
> 181 dev-disk-by\x2duuid-…75\x2d410c\x2d9597\x2ddbdb2fedbd1f.device start running
> 179 systemd-cryptsetup at nvme0n1p2_crypt.service                     start waiting

Can you provide the journal -alb log from such a boot?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190310/82cd830a/attachment.sig>