Jaunty Update: system does not boot anymore (with my crypto devices)

[Michael Zoet]

Hi to all,

I just updated my notebook form intrepid to jaunty. The update went
smoothly but after I rebooted the system the system is stuck and went to
the BusyBox. On intrepid everything worked fine...

My encrypted root device (/dev/mapper/sda1_crypt) is recognised, the
system wants to get my passphrase, the root partitions is unencrypted
and then it tries to unencrypt my next partition. (On intrepid this was
/dev/mapper/sda3_crypt on /usr). But the system waits for about 2
minutes and drops to the BusyBox.

I get the following system messages:

Unlocking the disk
/dev/disk/by-uuid/d5f140f2-af8e-4c27-82e0-92e8a3e0febe (sda1_crypt)
Enter passphrase:
key slot 0 unlocked.
Commands successful.
cryptsetup: sda1_crypt setup successfully
Begin: Waiting for encrypted source device... ...
Done.
    Check cryptopts=source= bootarg cat /proc/cmdline
    or missing modules, devices cat /proc/modules ls /dev
-r ALERT! /dev/disk/by-uuid/2adba953-fe57-4800-ad75-4cdd97041f0e does
not exists. Dropping to a shell!

BusyBox v1.10.2 ...


What me annoys most: I have no disk with the UUID
2adba953-fe57-4800-ad75-4cdd97041f0e! Nothing in /dev/disk/by-uuid and
no partition with this UUID in my /etc/fstab.

Where does jaunty get this UUID from? Why does jaunty uses this number?

And most important: How do I get my system to boot again?

Another question: how can I mount my other encrypted partitions with the
BusyBox shell?

THX in advance for every help,

Michael