[lrusak]

Last build seems a bit confused about "network online". I do have a OS-level mount (but I wasn't experiencing any lockup on reboot).
Before the systemd bump months ago my network would be up in ~7 seconds and Kodi started a second after that (~8s). After bump, network would be online in ~15 seconds and Kodi started a second or two after that (~16-17s).
Today's build takes a while to bring up the interface, pinging the Pi while rebooting confirmed that network comes up after ~35 seconds.
"Network Online" service seems to timeout (after 30 seconds), mount service is started but fails and then Kodi is started (33 seconds):

Code:

10:50:43  33.529049 T:1963450368  NOTICE: Starting Kodi (17.0-ALPHA1 Git:e39724c). Platform: Linux ARM 32-bit

SSHing and starting the mount service manually works and Kodi is happy.
journalctl: http://sprunge.us/YcXZ

No idea what you have got going on there, here with build #203 I get the following without waiting for the network.

Code:

Startup finished in 3.277s (kernel) + 8.966s (userspace) = 12.244s

and the following with my NFS mount (waiting for network)

Code:

Startup finished in 3.314s (kernel) + 9.705s (userspace) = 13.020s

This is with a wireless network as well.

So check that you don't have any other services running.

Also could you please SSH into your RPi and get a boot chart for me

Code:

systemd-analyze plot > /storage/downloads/rpi-boot.svg

then upload the image somewhere so I can look at it.

also, the output of the following commands would be helpful

Code:

systemd-analyze blame

and

Code:

systemd-analyze critical-chain

also, my storage-videos.mount looks like this

Code:

[Unit]
Description=videos mount
Requires=network-online.service
After=network-online.service
Before=kodi.service

[Mount]
TimeoutSec=5s
What=192.168.1.108:/mnt/tank/movies
Where=/storage/videos
Options=nolock
Type=nfs

[Install]
WantedBy=multi-user.target

I have the "TimeoutSec=5s" value in there because I often take my RPi to the girlfriends (where there is not NFS server) and I don't want the failed mount to delay the boot process. This shouldn't be needed otherwise.