Comment 4 for bug 439604

I'm running into the same problem, however my case is not gdm related.

I've got a dev server system running karmic. On that server I'm mounting about 10 file systems on bootup. On average every 5 boots or so one will have to be checked. Now what happens for me is that the filesystem is simply not mounted and fsckd in the background, while the normal boot process continues.

That means a lot of services are started, even though filesystems that contain data for them are not mounted (yet).

Postfix / mysql et al should not be started until all filesystems have been mounted.

Is there any way to force the boot process to wait until everything has been mounted?

The current way of background fscking will horribly break a lot of server installs imho.

kind regards