> Also, when this hang occurs, please check whether you have multiple
> 'watershed' processes running.  If the boot-time cryptsetup has hung for
> whatever reason, 'cryptdisks restart' will also hang waiting, to avoid
> colliding with the one that's already running.
>
>    

ok. I stop /etc/init.d/cryptdisks restart (looping for ever) with crtl+c 
and then:
ps aux |grep watershed
root       886  0.0  0.0   1668   484 ?        S    14:57   0:00 
/lib/udev/watershed /lib/cryptsetup/askpass Enter passphrase to unlock 
the disk /dev/mmcblk0p1 (data):
root       988  0.0  0.0   1668   464 ?        S    14:57   0:00 
/lib/udev/watershed /lib/cryptsetup/askpass Enter passphrase to unlock 
the disk /dev/mmcblk0p1 (data):

but this message never appears during the boot process.

I kill both watershedprocesses and then the /etc/init.d/cryptdisks 
restart is working fine:
  Enter passphrase to unlock the disk /dev/mmcblk0p1 (data):
key slot 0 unlocked.
Command successful.
  * data 
(started)...                                                              [ 
OK ]

It looks like something starts during the boot but it is not a blocking 
call.
It may explain why I do not see "Enter passphrase to unlock the disk 
/dev/mmcblk0p1 (data):" during the boot. This question remains 
unresponded and watershed is still alive waiting for an input.

fstab:
# <file system> <mount point> <type> <options> <dump> <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda2 during installation
UUID=0fd38542-fff5-43ce-b78b-f11e0cea69a3 /               ext4    
errors=remount-ro 0       1
# swap was on /dev/sda1 during installation
UUID=30240ff1-54bd-412f-bab0-757b788bf87f none            swap    
sw              0       0

/dev/mapper/data        /home/gnata/data   ext4    defaults        0
1

crypttab:
# <target name> <source device> <key file> <options>
data      /dev/mmcblk0p1                none luks

All these tests are performed on a new fresh karmic + dist-upgrade after 
insertion of "proposed" in the sources.list.

-- 
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
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

Reply via email to