Comment 4 for bug 447817

As I realized mountall 1.0 had been released I decided to try this again, but it still fails. This time, however, I'm getting an error message, rather than the system just freezing:

========================================
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
swap: waiting for LABEL=faolain-swap
/home: waiting for LABEL=faolain-home
/var/tmp: waithing for tmpfs
Press ESC to enter a recovery shell
========================================

After pressing ESC I'm getting the following message:
========================================
key slot 0 unlocked.
Command successful.
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and re-try.
root@faolain:~#
========================================

I used the maintenance shell to look around, and found that /dev/mapper/faolain-root exists and is mounted read-write as /, neither /dev/mapper/faolain-home nor /dev/mapper/faolain-swap exists, and that one of my tmpfs (/tmp) is mounted, but the other (/var/tmp) is not.

I also tried to start the cryptdisks-enable upstart script manually (by running "start cryptdisks-enable" in the shell) and this will create /dev/mapper/faolain-home and /dev/mapper/faolain-swap properly without asking for any password. Pressing Ctrl-D will however just restart usplash and gives me the same error massages again (see above). This time, however, pressing ESC will not give me another maintenance shell.

If I in addition to starting the cryptdisks-enable upstart script manually also mount all filesystems manually (by running "mount -a" in the shell) before pressing Ctr-D, then the system will resume the boot sequence and I'll get to my desktop eventually.

As cryptdisks-enable *does* do the right thing if started manually, I really do not believe the problem lies there, but rather with mountall.

This testing was done using mountall 1.0 and cryptsetup 1.0.6+20090405.svn49-1ubuntu7. Downgrading to mountall 0.1.8 while keeping cryptsetup 1.0.6+20090405.svn49-1ubuntu7 still solves the problem.