Dependency loops due to ANDed start conditions leave system unbootable
If /home is mounted on a separate partition, and the gdm start condition in /etc/init/gdm.conf is modified to include "mounted MOUNTPOINT=/home" as follows:
start on (filesystem
and mounted MOUNTPOINT=/home
and started dbus
and (drm-device-added card0 PRIMARY_
or stopped udevtrigger))
then a lucid system will no longer boot. It seems that in this case the mountall process is waiting for input from upstart, but upstart is not sending anything. Thus, the required muntall events are not emitted and the system refuses to boot.
The problem can be worked around by manually starting another mountall instance while the first instance is hanging.
I have attached the --verbose output of the first and second mountall, as
well as an strace output.
DistroRelease: Ubuntu 10.04
Package: mountall 2.15.3
Uname: Linux 3.0.0-17-server x86_64
Date: Sat Mar 24 18:45:46 2012
|Nikolaus Rath (nikratio) wrote : Re: Waiting for "mounted MOUNTPOINT=/home" in gdm.conf breaks system boot||#7|
|Steve Langasek (vorlon) wrote : Re: [Bug 964207] Re: Dependency loops due to ANDed start conditions leave system unbootable||#12|