systemd, what are you even doing

gistfile1.txt

Oct 28 00:12:05 t520 journal: Permanent journal (/var/log/journal/) is currently using 4.0G.#012Maximum allowed usage is set to 4.0G.#012Leaving at least 4.0G free (of currently available 7.6G of space).#012Enforced usage limit is thus 4.0G.
Oct 28 00:12:05 t520 journal: Journal started
Oct 28 00:12:05 t520 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x50000 action 0x6 frozen
Oct 28 00:12:05 t520 kernel: ata1: SError: { PHYRdyChg CommWake }
Oct 28 00:12:05 t520 kernel: ata1.00: failed command: FLUSH CACHE EXT
Oct 28 00:12:05 t520 kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 28#012         res 40/00:01:00:00:00/00:00:00:00:00/e0 Emask 0x4 (timeout)
Oct 28 00:12:05 t520 kernel: ata1.00: status: { DRDY }
Oct 28 00:12:05 t520 kernel: ata1: hard resetting link
Oct 28 00:12:05 t520 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 28 00:12:05 t520 kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Oct 28 00:12:05 t520 kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Oct 28 00:12:05 t520 kernel: ata1.00: configured for UDMA/133
Oct 28 00:12:05 t520 kernel: ata1.00: retrying FLUSH 0xea Emask 0x4
Oct 28 00:12:05 t520 kernel: ata1.00: device reported invalid CHS sector 0
Oct 28 00:12:05 t520 kernel: ata1: EH complete
Oct 28 00:12:05 t520 systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
Oct 28 00:12:05 t520 systemd[1]: Unit systemd-journald.service entered failed state.
Oct 28 00:12:05 t520 systemd[1]: systemd-journald.service failed.
Oct 28 00:12:05 t520 systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
Oct 28 00:12:05 t520 systemd[1]: Stopping Flush Journal to Persistent Storage...
Oct 28 00:12:05 t520 systemd[1]: Starting Journal Service...
Oct 28 00:12:05 t520 systemd[1]: Started Journal Service.