Your message dated Tue, 3 Sep 2019 00:51:08 +0200
with message-id <[email protected]>
and subject line Re: systemd: plain dm-crypt volumes not brought up on boot
has caused the Debian Bug report #801342,
regarding systemd: plain dm-crypt volumes not brought up on boot
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.)
--
801342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801342
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-17+deb8u2
Severity: normal
[This was originally meant as a followup to #712439 which has been
archived.]
Dear maintainers,
I upgraded a laptop from wheezy to jessie last weekend using
dist-upgrade which installed systemd as the init system. Since the
upgrade plain dm-crypt volumes are no longer brought up on boot. LUKS
volumes only work without errors if no plain dm-crypt volumes are
configured.
If a single, plain encrypted swap partition is present (alongside a
LUKS volume) this causes the machine to hang for the infamous 90
seconds and drop me into emergency mode. systemd then reports the
following status:
# systemctl status dev-mapper-swap.device
● dev-mapper-swap.device
Loaded: loaded
Active: inactive (dead)
Oct 08 20:53:16 laptop systemd[1]: Job dev-mapper-swap.device/start
timed out.
Oct 08 20:53:16 laptop systemd[1]: Timed out waiting for device
dev-mapper-swap.device.
# systemctl status dev-mapper-swap.swap
● dev-mapper-swap.swap - /dev/mapper/swap
Loaded: loaded (/etc/fstab)
Active: inactive (dead)
What: /dev/mapper/swap
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Oct 08 20:53:16 laptop systemd[1]: Dependency failed for /dev/mapper/swap.
If I then manually run "cryptdisks_start swap" such that cryptsetup is
called appropriately this changes as follows:
# systemctl status dev-mapper-swap.device
● dev-mapper-swap.device - /dev/mapper/swap
Follow: unit currently follows state of
sys-devices-virtual-block-dm\x2d3.device
Loaded: loaded
Active: active (plugged) since Thu 2015-10-08 20:54:55 CEST; 8s ago
Device: /sys/devices/virtual/block/dm-3
# systemctl status dev-mapper-swap.swap
● dev-mapper-swap.swap - /dev/mapper/swap
Loaded: loaded (/etc/fstab)
Active: failed (Result: exit-code) since Thu 2015-10-08 20:54:55
CEST; 39s ago
What: /dev/mapper/swap
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 797 ExecActivate=/sbin/swapon /dev/mapper/swap (code=exited,
status=255)
At this stage I can resume the boot process via "systemctl default" and
this leads to a working system.
# systemctl status dev-mapper-swap.swap
● dev-mapper-swap.swap - /dev/mapper/swap
Loaded: loaded (/etc/fstab)
Active: active since Thu 2015-10-08 20:56:11 CEST; 14min ago
What: /dev/mapper/swap
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 824 ExecActivate=/sbin/swapon /dev/mapper/swap (code=exited,
status=0/SUCCESS)
The configuration has been working for years, so I believe this is a
regression in jessie.
# dpkg -l dmsetup
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii dmsetup 2:1.02.90-2. amd64 Linux Kernel Device Mapper
usersp
# grep swap /etc/crypttab
swap /dev/sda5 /dev/random swap,cipher=aes-xts-plain,size=512
[For the record, this is not an entropy problem. Changing the key file
to /dev/urandom does not improve the situation.]
# grep swap /etc/fstab
/dev/mapper/swap none swap sw 0 0
# journalctl -b -p 3
[...]
Oct 08 20:53:16 laptop systemd[1]: Timed out waiting for device
dev-mapper-swap.device.
Oct 08 20:53:16 laptop systemd[1]: Dependency failed for Cryptography
Setup for swap.
Oct 08 20:53:16 laptop systemd[1]: Dependency failed for Encrypted Volumes.
Oct 08 20:53:16 laptop systemd[1]: Dependency failed for /dev/mapper/swap.
Oct 08 20:53:16 laptop systemd[1]: Dependency failed for Swap.
[...]
systemd also logs identically looking errors about other filesystems on
an encrypted lvm volume. Oddly enough, those go away and the system
boots normally if I remove the swap configuration.
Any help in tracking this down would be appreciated!
Cheers,
Rene
--- End Message ---
--- Begin Message ---
On Mon, 29 Oct 2018 10:56:25 +0100 Michael Biebl <[email protected]> wrote:
> Control: tags -1 + moreinfo
>
> On Thu, 08 Oct 2015 21:21:36 +0200 =?UTF-8?B?UmVuw6kgV2FnbmVy?=
> <[email protected]> wrote:
> > Package: systemd
> > Version: 215-17+deb8u2
> > Severity: normal
> >
> > [This was originally meant as a followup to #712439 which has been
> > archived.]
> >
> > Dear maintainers,
> >
> > I upgraded a laptop from wheezy to jessie last weekend using
> > dist-upgrade which installed systemd as the init system. Since the
> > upgrade plain dm-crypt volumes are no longer brought up on boot. LUKS
> > volumes only work without errors if no plain dm-crypt volumes are
> > configured.
> >
> > If a single, plain encrypted swap partition is present (alongside a
> > LUKS volume) this causes the machine to hang for the infamous 90
> > seconds and drop me into emergency mode. systemd then reports the
> > following status:
> >
>
> Is this bug report still reproducible with a recent version of systemd?
> If so, your /etc/crypttab and /etc/fstab would be useful.
No further feedback, so closing this old bug report at this point.
If you still run into problems with a recent version of systemd, please
file a new bug report.
Regards,
Michael
--
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]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
