@TRHH
The systemd.automount related issue in the banner has not been fixed yet. The problem is another contradicting issue, where hitting a network share mount point with systemd.automount active can cause a 90 seconds hang if that network share is offline.
So it does now show all matching mounts in the banner (thanks to findmnt --fstab flag), but it does not actively trigger them to mount, hence the disk usage will the one from the rootfs, until the mount has been actually triggered. We need to find a way to trigger the automounts with a short timeout, or asynchronously, a way that it does not hang everything.