[SOLVED] Switch to systemd -> Now system won't boot

fettouhi · 2012-09-02 09:43:28

I saw that todays update upgrade included the installation of systemd. I looked the wiki and did the necessary changes (I already had made the /etc/hostname etc. files). So I added the

init=/bin/systemd

line to grub and now my system won't boot. I get an error saying something about syslog service not enabled and then a black screen. I can boot my machine fine without the "init=/bin/systemd" line but I want to run a pure systemd system since Arch is moving to it anyway. In the wiki it mentions to install systemd-sysvcompat but it conflicts with initscripts it says. What am I doing wrong or missing?

Last edited by fettouhi (2013-12-08 14:42:04)

rbbt · 2012-09-02 09:49:52

Remove initscripts manually. https://wiki.archlinux.org/index.php/Sy … stallation Check the Note in that link

Last edited by rbbt (2012-09-02 09:51:07)

progandy · 2012-09-02 09:52:08

Don't remove initscripts until you have at least a tty with systemd. If you cannot see one on tty1, try tty2. There was a time when I had no login on tty1, but some days later it started working again.

KimTjik · 2012-09-02 09:52:39

It should work without installing systemd-sysvcompat. It's probably smarter to figure what doesn't work at the moment, when you actually are able to boot the system.

If I remember correctly systemd will default to an equivalent runlevel to 5. Have you activated some login manager in systemd?

Last edited by KimTjik (2012-09-02 09:54:46)

fettouhi · 2012-09-02 10:00:05

KimTjik wrote:

It should work without installing systemd-sysvcompat. It's probably smarter to figure what doesn't work at the moment, when you actually are able to boot the system.
If I remember correctly systemd will default to an equivalent runlevel to 5. Have you activated some login manager in systemd?

I just turned off quiet in the kernel boot option to get a bit more info. The booting starts with syslog socket [FAILED]. How do I turn on login manager in systemd?

fettouhi · 2012-09-02 10:04:20

I'm using inittab to lauch my login manager KDM by the way.

progandy · 2012-09-02 10:07:21

fettouhi wrote:

I'm using inittab to lauch my login manager KDM by the way.

Systemd does not read inittab. You'll have to enable the kdm service.

rbbt · 2012-09-02 10:07:28

https://wiki.archlinux.org/index.php/Sy … stallation

as a root run

# systemctl enable kdm.service

fettouhi · 2012-09-02 10:22:53

rbbt wrote:

https://wiki.archlinux.org/index.php/Sy … stallation
as a root run
# systemctl enable kdm.service

YES, that did the trick. I still get this error saying syslog.service not enabled. Should I enable it? My only gripe at the moment is that for some reason my system goes into a black screen, so I can't see the boot output. I'm not using splash or anything. With sysvinit I only got to see it loading udev modules and then the black screen until KDM kicks in.

fettouhi · 2012-09-02 10:31:43

I tried to enable syslog.service but it can't find file

[root@andre ~]# systemctl enable syslog.service
Failed to issue method call: No such file or directory

rbbt · 2012-09-02 10:36:18

try this

 # systemctl enable syslog-ng.service

progandy · 2012-09-02 10:53:44

rbbt wrote:

try this

 # systemctl enable syslog-ng.service

If you use syslog-ng, then you'll have to follow the instructions in the wiki to get it to coexist with systemd's journal. If you think the journal is enough, then uninstall syslog-ng
https://wiki.archlinux.org/index.php/Sy … md_Journal

My only gripe at the moment is that for some reason my system goes into a black screen, so I can't see the boot output.

Systemd does not show any output. if you want output, remove quiet from the kernel command line.

fettouhi · 2012-09-02 20:48:51

There is one thing I'm confued about the systemd wiki. If you switched over to run a pure systemd system is then the initscripts package then needed at all? If not how do the daemons get loaded I have in my DAEMON LIST rc.conf?

Linkas · 2012-09-02 21:02:07

https://wiki.archlinux.org/index.php/Sy … ve_systemd

.:B:. · 2012-09-02 21:37:23

The daemons array contains all the services that you'll probably need to enable explicitly (and manually) with systemd. Look at it as configuring your system from scratch.

You'll get .pacsave files of all the old init config files, so you can still check them for reference. Then enable every one in systemd with the 'systemctl enable' command as described above for e.g. syslog-ng.

For me systemd's journal works just fine so far.

Last edited by .:B:. (2012-09-02 21:37:37)

Echo · 2012-09-02 22:01:01

I found the following helpful for handling the daemons when making the switch:

https://wiki.archlinux.org/index.php/Da … of_Daemons

Good to know we'll get pacsave files for reference of old config files.

fettouhi · 2012-09-03 07:17:15

Thanks for the clarification about the DAEMONS list. My DAEMONS list is:

DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond @alsa dbus networkmanager ufw cupsd avahi-daemon samba)

when I try to enable alsa and dbus I get this

[root@andre ~]# systemctl enable alsa-store.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable alsa-restore.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable dbus.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.

Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.

fettouhi · 2012-09-03 07:23:16

For some reason netfs refers to remote-fs.service in systemd but that file is nowhere to be found

[root@andre ~]# systemctl enable remote-fs.service
Failed to issue method call: No such file or directory

tomegun · 2012-09-03 08:01:26

fettouhi wrote:

There is one thing I'm confued about the systemd wiki. If you switched over to run a pure systemd system is then the initscripts package then needed at all? If not how do the daemons get loaded I have in my DAEMON LIST rc.conf?

If you want systemd to use your scripts in /etc/rc.d/* and to load what you have in DAEMONS in rc.conf, then you need initscripts installed. A better solution is to only use native unit files, and enable them using "systemctl enable foo.service". Then you can drop initscripts. We have not yet converted all the rc scripts to native service files, so maybe this is not possible for you yet though.

tomegun · 2012-09-03 08:02:45

fettouhi wrote:

For some reason netfs refers to remote-fs.service in systemd but that file is nowhere to be found
[root@andre ~]# systemctl enable remote-fs.service
Failed to issue method call: No such file or directory

Thanks, that's a bug. It should be remote-fs.target. Anyway, it is enabled by default so you can ignore it.

tomegun · 2012-09-03 08:04:40

fettouhi wrote:

when I try to enable alsa and dbus I get this
[root@andre ~]# systemctl enable alsa-store.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable alsa-restore.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable dbus.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.

Both alsa and dbus are enabled statically. That is, they are always started and there is no need for you to enable them.

Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.

You need to enable lvm.service (and maybe lvm-on-crypt.service if you use encrypted block devices).

tomegun · 2012-09-03 08:08:03

tomegun wrote:

fettouhi wrote:
For some reason netfs refers to remote-fs.service in systemd but that file is nowhere to be found
[root@andre ~]# systemctl enable remote-fs.service
Failed to issue method call: No such file or directory
Thanks, that's a bug. It should be remote-fs.target. Anyway, it is enabled by default so you can ignore it.

Actually, this is not a bug. Where do you see the reference from netfs to remote-fs.service? In the package netfs.service should just point to /dev/null (meaning it is not needed).

fettouhi · 2012-09-03 09:11:31

tomegun wrote:

tomegun wrote:
fettouhi wrote:
For some reason netfs refers to remote-fs.service in systemd but that file is nowhere to be found
[root@andre ~]# systemctl enable remote-fs.service
Failed to issue method call: No such file or directory
Thanks, that's a bug. It should be remote-fs.target. Anyway, it is enabled by default so you can ignore it.
Actually, this is not a bug. Where do you see the reference from netfs to remote-fs.service? In the package netfs.service should just point to /dev/null (meaning it is not needed).

In the DAEMONS wiki here:

https://wiki.archlinux.org/index.php/Da … of_Daemons

scroll down and look for netfs.

mcloaked · 2012-09-03 09:18:06

fettouhi wrote:

Thanks for the clarification about the DAEMONS list. My DAEMONS list is:
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond @alsa dbus networkmanager ufw cupsd avahi-daemon samba)
when I try to enable alsa and dbus I get this
[root@andre ~]# systemctl enable alsa-store.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable alsa-restore.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable dbus.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.

I made the permanent transition to systemd and did not start alsa at all - sound works fine - so I never bothered with the alsa-store/alsa-restore service files at all - it just works! Also dbus gets handled by default in systemd so you don't need any starting of dbus service at all... it just works.

Echo · 2012-09-03 14:43:06

@ fettouhi, I just ignored netfs as the chart said it was unused w/systemd. Remote-fs.service doesn't exist on my system so that part of the wiki is out of date i would assume.

Arch Linux

#1 2012-09-02 09:43:28

[SOLVED] Switch to systemd -> Now system won't boot

#2 2012-09-02 09:49:52

Re: [SOLVED] Switch to systemd -> Now system won't boot

#3 2012-09-02 09:52:08

Re: [SOLVED] Switch to systemd -> Now system won't boot

#4 2012-09-02 09:52:39

Re: [SOLVED] Switch to systemd -> Now system won't boot

#5 2012-09-02 10:00:05

Re: [SOLVED] Switch to systemd -> Now system won't boot

#6 2012-09-02 10:04:20

Re: [SOLVED] Switch to systemd -> Now system won't boot

#7 2012-09-02 10:07:21

Re: [SOLVED] Switch to systemd -> Now system won't boot

#8 2012-09-02 10:07:28

Re: [SOLVED] Switch to systemd -> Now system won't boot

#9 2012-09-02 10:22:53

Re: [SOLVED] Switch to systemd -> Now system won't boot

#10 2012-09-02 10:31:43

Re: [SOLVED] Switch to systemd -> Now system won't boot

#11 2012-09-02 10:36:18

Re: [SOLVED] Switch to systemd -> Now system won't boot

#12 2012-09-02 10:53:44

Re: [SOLVED] Switch to systemd -> Now system won't boot

#13 2012-09-02 20:48:51

Re: [SOLVED] Switch to systemd -> Now system won't boot

#14 2012-09-02 21:02:07

Re: [SOLVED] Switch to systemd -> Now system won't boot

#15 2012-09-02 21:37:23

Re: [SOLVED] Switch to systemd -> Now system won't boot

#16 2012-09-02 22:01:01

Re: [SOLVED] Switch to systemd -> Now system won't boot

#17 2012-09-03 07:17:15

Re: [SOLVED] Switch to systemd -> Now system won't boot

#18 2012-09-03 07:23:16

Re: [SOLVED] Switch to systemd -> Now system won't boot

#19 2012-09-03 08:01:26

Re: [SOLVED] Switch to systemd -> Now system won't boot

#20 2012-09-03 08:02:45

Re: [SOLVED] Switch to systemd -> Now system won't boot

#21 2012-09-03 08:04:40

Re: [SOLVED] Switch to systemd -> Now system won't boot

#22 2012-09-03 08:08:03

Re: [SOLVED] Switch to systemd -> Now system won't boot

#23 2012-09-03 09:11:31

Re: [SOLVED] Switch to systemd -> Now system won't boot

#24 2012-09-03 09:18:06

Re: [SOLVED] Switch to systemd -> Now system won't boot

#25 2012-09-03 14:43:06

Re: [SOLVED] Switch to systemd -> Now system won't boot

Board footer