http://bugzilla.suse.com/show_bug.cgi?id=1134802
http://bugzilla.suse.com/show_bug.cgi?id=1134802#c15
Franck Bui
- Systemd reports four different ordering cycle problems which have nothing to do with fsck, it's possibly just a configuration issue that a failure in systemd-fsck-root.service is not handled in Systemd unit files dependencies. - Usually, one error leads to another i.e. it is wise to solve them chronologically. Here, the real culprit is in the middle and the preceding and succeeding messages are just consequences. - The system indeed should stop booting but - not because of a failed configuration which caused ordering issues - and also not because systemd-fsck-root.service failed but because fsck has to be run manually.
Comment #5 was suggesting some actions you want to try to figure out where this ordering cycle is coming from. But that looks related to the dracut units. Thomas could you have a look ? -- You are receiving this mail because: You are on the CC list for the bug.