Your message dated Tue, 29 Jul 2014 00:05:44 +0200
with message-id <[email protected]>
and subject line Re: Bug#756340: [systemd] Boot stops with certain (valid)
tmpfs entries in /etc/fstab
has caused the Debian Bug report #756340,
regarding [systemd] Boot stops with certain (valid) tmpfs entries in /etc/fstab
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.)
--
756340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756340
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 208-6
Severity: important
--- Please enter the report below this line. ---
I had the following two lines in my /etc/fstab and these caused systemd to not
boot anymore.
tmpfs /var/run tmpfs defaults,relatime,mode=1777 0 0
tmpfs /var/lock tmpfs defaults,relatime,mode=1777 0 0
It complained about /run/systemd/private not being available and indeed the
system dbus was not started. With an older kernel (3.12) I got it to get kdm
started, but I could not enter my password, it simply did not accept any
keyboard input. Switching to the console only worked thanks to the menu option
in kdm that I could activate with the mouse.
I couldn't install or configure certain new packages, because their post-
install scripts again failed due to the missing dbus socket. So after trying
to install sysvinit-core and rebooting, booting failed even harder, apparently
because of missing /bin/init. I could only fix this in grub with init=/bin/bash
After searching for similar problems on a second computer, I found those boot-
bugs with encrypted and nfts filesystems in /etc/fstab which brought me into
commenting out the tmpfs lines.
So there's a few problems here:
- systemd does not know how to deal with certain entries in fstab (somewhat
OK)
- systemd does not report or log any error about that (NOT OK)
- systemd breaks the entire system instead of just skipping those entries (NOT
OK)
- systemd did not allow me to manually start dbus (NOT OK)
- (this might go to a different report): packages should be installable without
dbus being available
I fixed the problem by (re-)installing systemd-shim and systemd-sysv
Thanks
Carsten
PS: yes, I noticed that the tmpfs lines are superfluous by now, since they can
be managed through /etc/default/tmpfs. That was not possible when I had added
them.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.14-2-amd64
Debian Release: jessie/sid
500 unstable www.deb-multimedia.org
500 unstable ftp.de.debian.org
500 stable security.debian.org
1 experimental ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
================================================-+-=========================
libacl1 (>= 2.2.51-8) |
libaudit1 (>= 1:2.2.1) |
libblkid1 (>= 2.17.2) |
libc6 (>= 2.17) |
libcap2 (>= 2.10) |
libcryptsetup4 (>= 2:1.4.3) |
libdbus-1-3 (>= 1.1.1) |
libgcrypt11 (>= 1.5.1) |
libkmod2 (>= 5~) |
liblzma5 (>= 5.1.1alpha+20120614) |
libpam0g (>= 0.99.7.1) |
libselinux1 (>= 2.1.9) |
libsystemd-daemon0 (= 208-6) |
libsystemd-journal0 (= 208-6) |
libudev1 (>= 189) |
libwrap0 (>= 7.6-4~) |
libsystemd-login0 (= 208-6) |
util-linux (>= 2.19.1-2) |
initscripts (>= 2.88dsf-17) |
sysv-rc |
udev |
acl |
adduser |
libcap2-bin |
Recommends (Version) | Installed
=============================-+-===========
libpam-systemd | 208-6
Suggests (Version) | Installed
=========================-+-===========
systemd-ui |
--- End Message ---
--- Begin Message ---
Am 28.07.2014 23:52, schrieb [email protected]:
> Package: systemd
> Version: 208-6
> Severity: important
>
> --- Please enter the report below this line. ---
>
> I had the following two lines in my /etc/fstab and these caused systemd to
> not
> boot anymore.
>
> tmpfs /var/run tmpfs defaults,relatime,mode=1777 0 0
> tmpfs /var/lock tmpfs defaults,relatime,mode=1777 0 0
/var/run and /var/lock should be symlinks to
/run and /run/lock nowadays and your system needs has been updated by
the sysvinit package to support that.
Also, 1777 is very much broken for /var/run.
--
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
