Ok, I purged cryptsetup to see if it caused the problems. It doesn't. I find it *very strange* that you cannot reproduce the error, as it seems quite simple to reproduce on this side.
With 'quiet splash' on the grub kernel commandline, and 1 ext4 partition to check at startup I get this problem. Without 'quiet splash' startup is quick. In both cases 'mountall --deamon' is still active after boot, it *should* finish after starting up, shouldn't it? As I said earlier, when I kill 'mountall' manually, the terminal I/O is weird. So, it doesnt wait indefinitely, but it takes *much* longer to start up, and I also have the feeling that my mounted filesystems aren't really stable (scp and rsync disconnect errors). A few days back this was OK, now it is not. -- 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
