systemctl --failed : console-setup about log2ram HOT 8 CLOSED

# systemctl --failed
  UNIT                  LOAD   ACTIVE SUB    DESCRIPTION                
● console-setup.service loaded failed failed Set console font and keymap

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @18.409s
└─multi-user.target @18.409s
  └─docker.service @14.605s +3.801s
    └─network-online.target @14.593s
      └─network.target @14.587s
        └─dhcpcd.service @3.888s +10.696s
          └─basic.target @3.858s
            └─sockets.target @3.857s
              └─docker.socket @3.840s +16ms
                └─sysinit.target @3.839s
                  └─systemd-timesyncd.service @3.483s +350ms
                    └─systemd-tmpfiles-setup.service @3.396s +78ms
                      └─systemd-journal-flush.service @3.322s +64ms
                        └─systemd-journald.service @3.146s +155ms
                          └─log2ram.service @3.002s +138ms
                            └─var-hdd.log.mount @3.074s
                              └─local-fs-pre.target @2.718s
                                └─lvm2-monitor.service @1.067s +1.650s
                                  └─lvm2-lvmetad.service @1.304s
                                    └─systemd-journald.socket @1.015s
                                      └─-.mount @808ms
                                        └─system.slice @927ms
                                          └─-.slice @808ms

# stat /var/hdd.log/log2ram.log
  File: /var/hdd.log/log2ram.log
  Size: 0         	Blocks: 0          IO Block: 4096   regular empty file
[...]

# lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 9.1 (stretch)
Release:	9.1
Codename:	stretch

# cat /etc/systemd/system/log2ram.service 
[Unit]
Description=Log2Ram
DefaultDependencies=no
Before=basic.target rsyslog.service syslog.target systemd-journald.service sysinit.target shutdown.target console-setup.service apache2.service
After=local-fs.target
Conflicts=shutdown.target reboot.target halt.target
RequiresMountsFor=/var/log /var/hdd.log
IgnoreOnIsolate=yes

[Service]
Type=oneshot
ExecStart= /usr/local/bin/log2ram start
ExecStop= /usr/local/bin/log2ram stop
ExecReload= /usr/local/bin/log2ram write
RemainAfterExit=yes

[Install]
WantedBy=sysinit.target
root@pifour:/home/yves# systemctl -failed
systemctl: invalid option -- 'e'

# systemctl --failed
  UNIT                  LOAD   ACTIVE SUB    DESCRIPTION                
● console-setup.service loaded failed failed Set console font and keymap

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

# systemctl restart console-setup.service

# systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

# systemd-analyze critical-chain |cat
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @19.923s
└─multi-user.target @19.923s
  └─docker.service @16.084s +3.838s
    └─network-online.target @16.077s
      └─network.target @16.046s
        └─dhcpcd.service @3.963s +12.081s
          └─basic.target @3.781s
            └─sockets.target @3.779s
              └─docker.socket @3.748s +28ms
                └─sysinit.target @3.746s
                  └─systemd-timesyncd.service @3.407s +338ms
                    └─systemd-tmpfiles-setup.service @3.295s +91ms
                      └─systemd-journal-flush.service @3.229s +59ms
                        └─systemd-journald.service @3.085s +138ms
                          └─log2ram.service @2.944s +135ms
                            └─var-hdd.log.mount @2.992s
                              └─local-fs-pre.target @2.677s
                                └─lvm2-monitor.service @1.052s +1.624s
                                  └─lvm2-lvmetad.service @1.275s
                                    └─systemd-journald.socket @992ms
                                      └─-.mount @808ms
                                        └─system.slice @906ms
                                          └─-.slice @808ms