Your message dated Sat, 18 Jun 2011 17:59:31 +0100
with message-id <1308416371.1710.1.camel@wintermute>
and subject line Re: Bug#622300: systemd: fails to bring up encrypted swap
has caused the Debian Bug report #622300,
regarding systemd: fails to bring up encrypted swap
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.)
--
622300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622300
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 20-1
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
$ grep swap0 /etc/fstab
/dev/mapper/swap0 none swap sw 0 0
$ cat /etc/crypttab
# <target name> <source device> <key file> <options>
swap0 /dev/sdb1 /dev/urandom swap
$ systemctl show [email protected]
[email protected]
[email protected]
BindTo=dev-sdb1.device dev-mapper-swap0.device
RequiredBy=dev-mapper-swap0.device
WantedBy=cryptsetup.target dev-sdb1.device
Before=dev-mapper-swap0.device shutdown.target cryptsetup.target
After=systemd-readahead-collect.service systemd-readahead-replay.service
dev-sdb1.device systemd-random-seed-load.service
Description=Cryptography Setup for swap0
LoadState=loaded
ActiveState=failed
SubState=failed
FragmentPath=/dev/.systemd/generator-YrAzJw/[email protected]
InactiveExitTimestamp=Mon, 11 Apr 2011 22:41:55 +0100
InactiveEnterTimestamp=Mon, 11 Apr 2011 22:41:55 +0100
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=no
DefaultControlGroup=name=systemd:/system/[email protected]/swap0
ControlGroup=cpu:/system/[email protected]/swap0
name=systemd:/system/[email protected]/swap0
NeedDaemonReload=no
JobTimeoutUSec=0
Type=oneshot
Restart=no
NotifyAccess=none
RestartUSec=100ms
TimeoutUSec=3min
ExecStart={ path=/lib/systemd/systemd-cryptsetup ;
argv[]=/lib/systemd/systemd-cryptsetup attach swap0 /dev/sdb1 /dev/urandom swap
; ignore=no ; start_time=[n/a] ; stop_time=[Mon, 11 Apr 2011 22:41:55 +0100] ;
pid=20217 ; code=exited ; status=1 }
ExecStartPost={ path=/sbin/mkswap ; argv[]=/sbin/mkswap /dev/mapper/swap0 ;
ignore=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ;
status=0/ }
ExecStop={ path=/lib/systemd/systemd-cryptsetup ;
argv[]=/lib/systemd/systemd-cryptsetup detach swap0 ; ignore=no ;
start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/ }
UMask=0002
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=1024
LimitAS=18446744073709551615
LimitNPROC=31650
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=31650
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=inherit
StandardError=inherit
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSetDrop=0
MountFlags=1048576
PrivateTmp=no
SameProcessGroup=no
KillMode=control-group
KillSignal=15
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=yes
GuessMainPID=yes
ExecMainPID=20217
ExecMainCode=1
ExecMainStatus=1
MainPID=0
ControlPID=0
SysVStartPriority=-1
FsckPassNo=0
$ sudo systemctl start [email protected]
Job failed. See system logs and 'systemctl status' for details.
$ tail /var/log/syslog
Apr 11 22:47:40 wintermute systemd-cryptsetup[20574]: crypt_init() failed:
Function not implemented
Apr 11 22:47:40 wintermute systemd[1]: [email protected]: main process
exited, code=exited, status=1
Apr 11 22:47:40 wintermute systemd[1]: Unit [email protected] entered
failed state.
- -- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (550, 'stable-updates'), (550, 'stable'), (540, 'testing'), (530,
'unstable'), (520, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii libaudit0 1.7.13-1+b2 Dynamic library for security audit
ii libc6 2.13-0exp5 Embedded GNU C Library: Shared lib
ii libcap2 1:2.19-3 support for getting/setting POSIX.
ii libcryptsetup1 2:1.2.0-2 libcryptsetup shared library
ii libdbus-1-3 1.2.24-4 simple interprocess messaging syst
ii libpam0g 1.1.1-6.1 Pluggable Authentication Modules l
ii libselinux1 2.0.96-1 SELinux runtime shared libraries
ii libudev0 167-1 libudev shared library
ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra
ii util-linux 2.17.2-9.1 Miscellaneous system utilities
Versions of packages systemd recommends:
ii libpam-systemd 20-1 system and service manager - PAM m
Versions of packages systemd suggests:
ii systemd-gui 20-1 system and service manager - GUI
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk2jeMgACgkQshl/216gEHjzfgCfQoiyvo4ZEP/fHCkQsEfWjF0G
nxAAn0TJTThsD5mgCJD+YrgqAj6RvFSC
=UHiq
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Tue, 2011-04-12 at 23:02 +0200, Tollef Fog Heen wrote:
> ]] Sam Morris
>
> | > $ tail /var/log/syslog
> | > Apr 11 22:47:40 wintermute systemd-cryptsetup[20574]: crypt_init()
> failed: Function not implemented
> | > Apr 11 22:47:40 wintermute systemd[1]: [email protected]: main
> process exited, code=exited, status=1
> | > Apr 11 22:47:40 wintermute systemd[1]: Unit [email protected]
> entered failed state.
> |
> | Looks like this happens because the dm_mod kernel module is not loaded.
>
> After a bit of debugging, it seems like you either need a newer kernel
> that has a modalias directive for /dev/mapper/control or manually load
> the dm_mod kernel module.
>
> Regards
You're right, once I upgraded to 2.6.39 this problem went away.
--
Sam Morris <https://robots.org.uk/>
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
--- End Message ---
