Checked again: fsck is definitely not finished: file /forcefsck is not erased!
So it is not just killing plymouth, start-up procedure is faulty. See also this bug report: https://bugs.launchpad.net/bugs/538810 and https://bugs.launchpad.net/bugs/554079 -- ply_boot_client_flush() does not read replies (plymouth stuck during/after filesystem check or error) https://bugs.launchpad.net/bugs/554737 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
