upstart hangs while starting cryptdisks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Karmic |
Fix Released
|
Medium
|
Steve Langasek | ||
Lucid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: upstart
Hi,
I am not sure if this bug is more cryptdisk releated, maybe you can decide when you read the provided solution.
My startup process needs both stages of the cryptdisk scripts. In the first step (stage early) a /dev/mapper/ entry is created for an USB Stick asking for a password. On this stick resides all keys for the second step.
The two step mechanism is not processed by the new upstart script in /etc/init/
Please change /etc/init/
...
esac
INITSTATE=
do_start
end script
to
...
esac
INITSTATE=
do_start
INITSTATE=
do_start
end script
The second problem is a timing problem. If the Stick is not mounted fast enough the system fails to read some keys. When this happens the system hangs completly. I think this might be, because this partitions are marked as auto in /etc/fstab. If tey don't come up the upstart process waits endless.
To overcome this I changed /lib/cryptsetup
Please change /lib/cryptsetup
do_start () {
local dst src key opts result
modprobe -qb dm-mod || true
modprobe -qb dm-crypt || true
dmsetup mknodes > /dev/null 2>&1 || true
mount_fs
...
to
do_start () {
local dst src key opts result
modprobe -qb dm-mod || true
modprobe -qb dm-crypt || true
dmsetup mknodes > /dev/null 2>&1 || true
mount_fs
sleep 1
...
Finally I deleted both symlinks /etc/rcS.
Hope this helps cheers,
Christoph
ProblemType: Bug
Architecture: i386
Date: Mon Oct 5 21:51:47 2009
DistroRelease: Ubuntu 9.10
Package: upstart 0.6.3-7
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=de_DE.UTF-8
ProcVersionSign
SourcePackage: upstart
Uname: Linux 2.6.31-11-generic i686
XsessionErrors:
(nautilus:5989): Eel-CRITICAL **: eel_preferences
(polkit-
affects: | upstart (Ubuntu) → cryptsetup (Ubuntu) |
Changed in cryptsetup (Ubuntu): | |
status: | Fix Committed → Invalid |
Changed in cryptsetup (Ubuntu): | |
status: | Invalid → Fix Committed |
Changed in cryptsetup (Ubuntu): | |
status: | Fix Committed → Triaged |
importance: | Undecided → Medium |
Changed in cryptsetup (Ubuntu Karmic): | |
assignee: | nobody → Steve Langasek (vorlon) |
importance: | Undecided → Medium |
milestone: | none → karmic-updates |
status: | New → Triaged |
Changed in cryptsetup (Ubuntu Karmic): | |
status: | Triaged → In Progress |
Hi, early.conf) . The second part (timing problem) seems more related to mountall.
since the startup scripts for mountall and cryptsetup are under heavy development, the proposed solution does not work anymore. A better solution for the first part is to create an additional init script (eg. cryptdisks-
Thanks,
Christoph