No sshd as of the latest update

[Ralf Mardorf]

I would start troubleshooting by checking those points:

1. tmpfs is in the RAM not on your hard disk drive, so any directory
you'll create in tmpfs, gets lost if you shutdown -r now. [1]
2. Perhaps sshd needs write access, while the file system still is
mounted read only. [2]
3. Care about the order the units are started by systemd. [3]
4. Log files?

[1]
"Modern Linux distributions include a /run directory as a temporary
filesystem (tmpfs) which stores volatile runtime data, and which is
being considered for the next version of the FHS.[14] According to the
FHS version 2.3, this data should be stored in /var/run but this was a
problem in some cases because this directory isn't always available at
early boot." -
http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

[2]
"For the root filesystem, it also has to be mounted read-only initially
with the kernel parameter ro and only then remounted read-write from
fstab" - https://wiki.archlinux.org/index.php/Fsck

[3]
"Handling dependencies

With systemd, dependencies can be resolved by designing the unit files
correctly. The most typical case is that the unit A requires the unit B
to be running before A is started. In that case add Requires=B and
After=B to the [Unit] section of A. If the dependency is optional, add
Wants=B and After=B instead. Note that Wants= and Requires= do not
imply After=, meaning that if After= is not specified, the two units
will be started in parallel.

Dependencies are typically placed on services and not on targets. For
example, network.target is pulled in by whatever service configures
your network interfaces, therefore ordering your custom unit after it
is sufficient since network.target is started anyway." -
https://wiki.archlinux.org/index.php/Systemd