At the time when it appeared stuck, there was still heavy disk access. Looking at the sysrq trace and at the superblock on my third local filesystem, it seems like another fsck was running without displaying any output on the console.
-- Boot failed to complete after fsck https://launchpad.net/bugs/83831 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
