System doesn't boot up because of Systemd-timesyncd.service

ArchDoctor_needed · 2018-07-18 12:55:01

Since my last system update the System won't boot successfully.

I get stuck at:

[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details. 
[ OK ] Stopped Network Time Synchronization.
       Starting Network Time  Synchronization...
[...]
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details. 
[ OK ] Stopped Network Time Synchronization.
       Starting Network Time  Synchronization...
[...]

What I tried so far:

* I can't access the systemctl status since I'm stuck right at the boot sequence
* Went into the system using arch-root and looked into journalctl since today

<code>
systemd-timesyncd.service: Start operation timed out. Terminating.
systemd-timesyncd.service: Failed with result `timeout`.
Failed to start Network Time Synchronization.
systemd-timesyncd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
</code>

* Looked into /var/log/pacman.log
<code>
There was a warning that the permissions of /var/lib/samba/private are 755 on the filesystem and 700 on the package.
Also i noticed that libnss_nis got upgraded
</code>
* I googled the initial error and found a thread that states that this could be related to libnss_nis so i reinstalled it
* For the permission warning I recursively changed the permission of /var/lib/samba/private to 700

* Furthermore, I found a thread that stated it might be related to the ProtectKernelModules=true within /usr/lib/systemd/system/systemd-timesyncd.service. I put that to "no" as well as tried to put all protect flags to "no"

So far nothing worked and I hope someone can help me out.

Best regards

Edit:

pacman.log : https://pastebin.com/f8X3Tqnq
dmesg : https://pastebin.com/wSTUgAUj
journal : https://pastebin.com/MG4XfuSa

Last edited by ArchDoctor_needed (2018-07-18 13:23:08)

WorMzy · 2018-07-18 13:05:43

When the boot process gets stuck, can you switch to another TTY?

Please post the full journal from a failed boot session.

ArchDoctor_needed · 2018-07-18 13:23:32

Added logs.

edit: Tried to switch tty using ctrl+alt F(x) but doesn't work

Last edited by ArchDoctor_needed (2018-07-18 13:32:40)

seth · 2018-07-18 14:14:58

Random observations:
* no trace of a network connection (no idea whether that knocks out timesyncd)
* cryptsetup issues (invalid password)

Maybe the timesyncd is just a r ed herring. What happens if you disable the service?

ua4000 · 2018-07-18 16:40:14

seth wrote:

What happens if you disable the service?

e.g. with

systemd.mask=systemd-timesyncd.service

as kernel parameter at boot, https://wiki.archlinux.org/index.php/Kernel_parameters
or you delete the timesyncd start link somewhere in /etc/systemd/system with an arch-chroot.

Last edited by ua4000 (2018-07-18 17:16:39)

ArchDoctor_needed · 2018-07-20 06:29:20

I noticed the cryptsetup issue too. But I had this for years. I believe it is related to my swap partition being within my crypt/lvm setup. But I don't know, maybe now it is interfering with something.

For disabling, I went with

systemd.mask=systemd-timesyncd.service

as boot parameter.

The booting process continued further but everything took ages (probably because more timeouts occurred).

journal: https://pastebin.com/DbJsjVNw

I was able to switch tty's (or at least screens) but didn't get a prompt to login.

After that i looked into the systemd services that I'm starting (especially the ones that failed). I also removed the link so they won't start during the next boot phase.
But before I'm doing that, maybe someone got still an idea how to fix this.

journal: https://pastebin.com/pVYVSVvb

I got further and even saw a mouse cursor. But i couldn't get a tty. Everything froze.
From the journal I get, that gnome stopped with internal errors. Probably because of whatever is causing the initial issues.

I think, that I will go with the approach of wiping the root volume and reinstalling arch. Hopefully this will resolve my issues.

Last edited by ArchDoctor_needed (2018-07-20 06:42:12)

seth · 2018-07-20 07:32:45

The "crystemd-cryptsetup[391]: Invalid passphrase." messages are however gone.

You're running two competing network managing services (NM and dhcpcd), pick one.
Also I'd try w/o the vbox modules…

ua4000 · 2018-07-20 14:24:06

ArchDoctor_needed wrote:

I got further and even saw a mouse cursor. But i couldn't get a tty. Everything froze.

mouse cursor sounds like you reached X.

Try booting without GUI, e.g. with kernel boot line systemd.unit=multi-user.target

ArchDoctor_needed · 2018-08-24 16:18:40

I think i found the problem.
It's related to the upgrade of systemd 238 to 239. After downgrading everything and partly re-upgrading them, I could narrow it down to

* libsystemd
* systemd
* systemd-sysvcompat

Also found a open bug ticket that hopefully will lead to a solution. https://bugs.archlinux.org/task/59262

Last edited by ArchDoctor_needed (2018-08-24 16:19:33)

loqs · 2018-08-24 16:24:54

If you update to 239 but disable gdm does that still work? (which would indicate it is that issue)

Arch Linux

#1 2018-07-18 12:55:01

System doesn't boot up because of Systemd-timesyncd.service

#2 2018-07-18 13:05:43

Re: System doesn't boot up because of Systemd-timesyncd.service

#3 2018-07-18 13:23:32

Re: System doesn't boot up because of Systemd-timesyncd.service

#4 2018-07-18 14:14:58

Re: System doesn't boot up because of Systemd-timesyncd.service

#5 2018-07-18 16:40:14

Re: System doesn't boot up because of Systemd-timesyncd.service

#6 2018-07-20 06:29:20

Re: System doesn't boot up because of Systemd-timesyncd.service

#7 2018-07-20 07:32:45

Re: System doesn't boot up because of Systemd-timesyncd.service

#8 2018-07-20 14:24:06

Re: System doesn't boot up because of Systemd-timesyncd.service

#9 2018-08-24 16:18:40

Re: System doesn't boot up because of Systemd-timesyncd.service

#10 2018-08-24 16:24:54

Re: System doesn't boot up because of Systemd-timesyncd.service

Board footer