[AshamedCaptain]

Sadly no. The problem is that the entire local-fs.target is stopped 'cleanly' but with no clear reason. i.e.

    $ systemctl status local-fs.target
    Active: inactive (dead) since [...]
    21:12:56 ... systemd[1]: Reached target Local File Systems.
    21:12:57 ... systemd[1]: Stopped target Local File Systems.

Yes, the log just shows it stopping one second after being started, nothing happening inbetween, and no reason given for it being stopped.

Incredibly enough, local-fs.target is a dependency for graphical.target, so the system should not have continued booting. But not only it has continued booting, systemd even thinks that it finished booting all-OK. State is "running" (not "degraded" as it would be if any service/mount failed), with 0 failed services. Even though both graphical.target and local-fs.target are 'dead'.