If you had set 'bootwait=true', that's a syntax error; the correct option is simply 'bootwait'.
It's also entirely redundant on the / and /home filesystems. I've heard other reports that setting 'bootwait' on a filesystem where it's already implicit does cause hangs. This is a bug that should be fixed, certainly, but it doesn't mean that bootwait is unusable - there's no reason you should have set bootwait on these fstab entries in the first place. I guess the original problem you were trying to solve was the issue described at <https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/439604/comments/25>. I think that was indeed an fsck holding up X. And I agree that there should be documentation somewhere of the set of filesystems that mountall implicitly waits for. -- boot process isn't paused while fsck runs on partition: boot process is completed with fsck running in the background preventing partition from mounting https://bugs.launchpad.net/bugs/439604 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
