http://bugzilla.suse.com/show_bug.cgi?id=1134802
http://bugzilla.suse.com/show_bug.cgi?id=1134802#c9
Thomas Blume
Created attachment 811043 [details] rdsosreport.txt
I extracted the rdsosreport.txt from the failing boot which I attach here.
It looks like the root cause of the problem is a failing fsck. The rdsosrepot shows: --> [ 7.032060] linux-suse systemd-fsck[445]: /dev/sda2: Inodes that were part of a corrupted orphan linked list found. [ 7.032060] linux-suse systemd-fsck[445]: /dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. [ 7.032060] linux-suse systemd-fsck[445]: (i.e., without -a or -p options) [ 7.079060] linux-suse systemd-fsck[445]: fsck failed with exit status 4. [ 7.079141] linux-suse systemd-fsck[445]: Running request emergency.target/start/replace [ 7.081560] linux-suse systemd[1]: systemd-fsck-root.service: Main process exited, code=exited, status=1/FAILURE [ 7.081917] linux-suse systemd[1]: systemd-fsck-root.service: Failed with result 'exit-code'. --< The failing systemd-fsck-root.service makes other services fail. Please boot until the machine stops in emergency mode, and then run: fsck /dev/sda2 manually. When it succeeds, please reboot and check whether the machine comes up now. -- You are receiving this mail because: You are on the CC list for the bug.