Comment 7 for bug 260807

well there's bad news - i had already tried to find something in the logfiles but to no avail - they do resume just after the kernel-induced reboot after the initial fsck. furthermore, i now recognized that after such crashy shutdown, fsck does not only find errors but also had "died with error code 3" each time. i must have read over that before.
another thing that already indicated that something is fishy with shutdown is, that after fsck and the reboot, my saved-upon-logoff ubuntu session including evolution, firefox etc. is always in a post-crash condition.

nevertheless i'll attach my kern.log, fyi, i initiated shutdown at 7:20, all entries at 7:22 are already from the reboot after (unsuccessful) fsck.