Comment 5 for bug 1726930

systemd-resolved.service and systemd.hostnamed.service show up pretty clearly on the startup console as having problems and their logs show repeated entries of the form:

-- Logs begin at Mon 2017-10-23 13:01:36 EDT, end at Mon 2017-10-23 13:05:52 EDT. --
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system
Oct 23 13:01:38 T450s systemd[1]: Failed to start Network Name Resolution.
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Unit entered failed state.
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Failed with result 'resources'.
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Oct 23 13:01:38 T450s systemd[1]: Stopped Network Name Resolution.
Oct 23 13:01:38 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system

-- Logs begin at Mon 2017-10-23 13:01:36 EDT, end at Mon 2017-10-23 13:06:20 EDT. --
Oct 23 13:01:38 T450s systemd[1]: systemd-hostnamed.service: Failed to run 'start' task: Read-only file system
Oct 23 13:01:38 T450s systemd[1]: Failed to start Hostname Service.
Oct 23 13:01:38 T450s systemd[1]: systemd-hostnamed.service: Unit entered failed state.
Oct 23 13:01:38 T450s systemd[1]: systemd-hostnamed.service: Failed with result 'resources'.