| 2012-03-24 22:53:49 |
Nikolaus Rath |
bug |
|
|
added bug |
| 2012-03-24 22:53:49 |
Nikolaus Rath |
attachment added |
|
initctl list output for hanging system https://bugs.launchpad.net/bugs/964207/+attachment/2931396/+files/initctl-list |
|
| 2012-03-24 22:55:13 |
Nikolaus Rath |
attachment added |
|
Output of upstart started mountall https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+attachment/2931398/+files/mountall.log |
|
| 2012-03-24 22:56:43 |
Nikolaus Rath |
attachment added |
|
Output of second, manually started mountall https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+attachment/2931399/+files/mountall2.log |
|
| 2012-03-24 23:30:14 |
Nikolaus Rath |
attachment added |
|
strace -f output for upstarted started mountall https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+attachment/2931546/+files/strace.log |
|
| 2012-03-25 20:17:22 |
Launchpad Janitor |
mountall (Ubuntu): status |
New |
Confirmed |
|
| 2012-03-31 22:27:04 |
Nikolaus Rath |
description |
One of my Lucid systems stopped booting. If I interpret the "initctl list" output correctly (attached) the system is waiting for mountall to complete.
mountall, however, seems just stuck doing nothing. I added --verbose to /etc/init/mountall.conf and redirected the output into a file (attached as well).
If I execute another "mountall --verbose", this one seems to complete and the system continues booting. I have attached the output of this second run as well.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mountall 2.15.3
ProcVersionSignature: Ubuntu 3.0.0-17.30~lucid1-server 3.0.22
Uname: Linux 3.0.0-17-server x86_64
Architecture: amd64
Date: Sat Mar 24 18:45:46 2012
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: mountall |
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_DEVICE_FOR_DISPLAY=1
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.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mountall 2.15.3
ProcVersionSignature: Ubuntu 3.0.0-17.30~lucid1-server 3.0.22
Uname: Linux 3.0.0-17-server x86_64
Architecture: amd64
Date: Sat Mar 24 18:45:46 2012
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: mountall |
|
| 2012-03-31 22:27:37 |
Nikolaus Rath |
affects |
mountall (Ubuntu) |
upstart (Ubuntu) |
|
| 2012-03-31 22:28:08 |
Nikolaus Rath |
summary |
Hanging mountall stops boot process |
Waiting for mounted MOUNTPOINT=/home in gdm.conf breaks system boot |
|
| 2012-03-31 22:28:28 |
Nikolaus Rath |
summary |
Waiting for mounted MOUNTPOINT=/home in gdm.conf breaks system boot |
Waiting for "mounted MOUNTPOINT=/home in gdm.conf" breaks system boot |
|
| 2012-03-31 22:29:06 |
Nikolaus Rath |
summary |
Waiting for "mounted MOUNTPOINT=/home in gdm.conf" breaks system boot |
Waiting for "mounted MOUNTPOINT=/home" in gdm.conf breaks system boot |
|
| 2012-08-07 19:33:10 |
Nikolaus Rath |
summary |
Waiting for "mounted MOUNTPOINT=/home" in gdm.conf breaks system boot |
Dependency loops due to ANDed start conditions leave system unbootable |
|
| 2012-08-07 19:33:47 |
Nikolaus Rath |
bug task added |
|
mountall (Ubuntu) |
|
| 2012-08-07 19:34:04 |
Nikolaus Rath |
mountall (Ubuntu): status |
New |
Confirmed |
|
| 2012-08-07 20:22:02 |
Steve Langasek |
mountall (Ubuntu): status |
Confirmed |
Invalid |
|
| 2012-08-07 20:22:11 |
Steve Langasek |
upstart (Ubuntu): status |
Confirmed |
Invalid |
|
