Your message dated Tue, 08 Apr 2014 03:13:15 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-systemd-maintainers] Bug#743265: systemd: booting
with init=/bin/systemd drops into emergency mode
has caused the Debian Bug report #743265,
regarding systemd drops into emergency mode if devices from /etc/fstab are
missing
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.)
--
743265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743265
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 204-8
Severity: important
Hi,
I just tried to boot with init=/bin/systemd, and that didn't
work out well:
* first some error message
Failed to start Load Kernel Modules.
(I think!)
* after that it tried to fsck.vfat my Win8.1 partition
* after that dropped me into emergency shell
Hmm.. from the saved journal I see
Apr 01 15:49:04 wienerschnitzel systemd[1]: Starting File System Check on Root
Device...
Apr 01 15:49:04 wienerschnitzel systemd[1]: Expecting device dev-sda3.device...
Apr 01 15:49:04 wienerschnitzel systemd[1]: Expecting device dev-sda5.device...
Apr 01 15:49:04 wienerschnitzel systemd[1]: Expecting device
dev-disk-by\x2did-usb\x2dIntuix_U3_0BE1C9611230D925\x2d0:0\x2dpart1.device...
Apr 01 15:49:04 wienerschnitzel systemd[1]: Expecting device
dev-disk-by\x2did-usb\x2dSAMSUNG_HM250JI_0D0A52255FFF\x2d0:0\x2dpart1.device...
Apr 01 15:49:04 wienerschnitzel systemd[1]: Expecting device
dev-disk-by\x2did-usb\x2dBUFFALO_External_HDD_00000002022EAA7\x2d0:0\x2dpart1.device...
Apr 01 15:49:04 wienerschnitzel systemd[1]: Expecting device
dev-disk-by\x2did-usb\x2dWD_My_Passport_0748_575834314541314C5A453634\x2d0:0\x2dpart1.device...
Apr 01 15:49:04 wienerschnitzel systemd[1]: systemd-modules-load.service: main
process exited, code=exited, status=1/FAILURE
Apr 01 15:49:04 wienerschnitzel systemd[1]: Failed to start Load Kernel Modules.
Apr 01 15:49:04 wienerschnitzel systemd[1]: Unit systemd-modules-load.service
entered failed state.
Apr 01 15:49:04 wienerschnitzel systemd[1]: Started Apply Kernel Variables.
There is muuuuuuch more output in the sysctl -bx (or whatever)
output ...
Where should one start here?
For now I went back to sysv-init
Thanks
Norbert
-- Package-specific info:
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14.0+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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-51
ii libacl1 2.2.52-1
ii libaudit1 1:2.3.4-1
ii libc6 2.18-4
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.0-3
ii libgcrypt11 1.5.3-4
ii libkmod2 16-2
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.8-2
ii libselinux1 2.2.2-1
ii libsystemd-daemon0 204-8
ii libsystemd-journal0 204-8
ii libsystemd-login0 204-8
ii libudev1 204-8
ii libwrap0 7.6.q-25
ii sysv-rc 2.88dsf-51
ii udev 204-8
ii util-linux 2.20.1-5.7
Versions of packages systemd recommends:
ii libpam-systemd 204-8
Versions of packages systemd suggests:
pn systemd-ui <none>
-- no debconf information
0 overridden configuration files found.
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/pppd-dns.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lm-sensors.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/NetworkManager.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups-browsed.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <==
==> /var/lib/systemd/deb-systemd-helper-enabled/atd.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/atd.service
==> /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/anacron.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/bluetooth.target.wants/bluetooth.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/bluetooth.service.dsh-also <==
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/dbus-org.bluez.service
==> /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.bluez.service <==
==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <==
==>
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket <==
==> /var/lib/systemd/deb-systemd-helper-enabled/pppd-dns.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/pppd-dns.service
==> /var/lib/systemd/deb-systemd-helper-enabled/lm-sensors.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/lm-sensors.service
==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-dispatcher.service.dsh-also
<==
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.nm-dispatcher.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-wait-online.service.dsh-also
<==
/etc/systemd/system/multi-user.target.wants/NetworkManager-wait-online.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.NetworkManager.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager.service.dsh-also
<==
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/printer.target.wants/cups.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/cups-browsed.service.dsh-also
<==
/etc/systemd/system/multi-user.target.wants/cups-browsed.service
==> /var/lib/systemd/deb-systemd-helper-enabled/cups.service.dsh-also <==
/etc/systemd/system/sockets.target.wants/cups.socket
/etc/systemd/system/multi-user.target.wants/cups.path
/etc/systemd/system/printer.target.wants/cups.service
==> /var/lib/systemd/deb-systemd-helper-enabled/cups.path.dsh-also <==
/etc/systemd/system/multi-user.target.wants/cups.path
==> /var/lib/systemd/deb-systemd-helper-enabled/cups.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/cups.socket
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/ssh.service
/etc/systemd/system/sshd.service
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/ssh.socket
--- End Message ---
--- Begin Message ---
On 7. April 2014 00:46:32 MESZ, Norbert Preining <[email protected]> wrote:
>> I actually do think that systemd handles this correctly. How is it
>> supposed to know if the mount points listed in /etc/fstab aren't
>vital
>> for the system to function properly unless you tell it so?
>
>Thinking about it, I actually agree. Let us close this bug.
>If you want one you can add a line in the README, but I guess
>that is not even necessary.
>
>>From my side you can close this bug.
OK, doing so.
--- End Message ---
