https://bugzilla.redhat.com/show_bug.cgi?id=967521
--- Comment #49 from Zbigniew Jędrzejewski-Szmek zbyszek@in.waw.pl --- (In reply to Tom London from comment #43)
Not sure if it is helpful, but I noticed that I can successfully boot with "systemd.log_level=info".
[snip]
This indeed doesn't say much. It is possible that systemd-journald is running fine long before the "Started Trigger Flushing" message appears. Can you boot with the following file:
# /etc/systemd/system/systemd-journald.service.d/debug.conf [Service] Environment=SYSTEMD_LOG_LEVEL=debug SYSTEMD_LOG_TARGET=kmsg
This will make systemd-journald log what it is doing. The output will be in dmesg. Might help us to understand what is going on.