Comment 2 for bug 421876

Content of /var/log/fsck/checkfs file indicating root cause of the problem:

Log of fsck -C3 -R -A -a
Mon Aug 31 12:32:12 2009

fsck from util-linux-ng 2.16
boot: recovering journal
boot: clean, 188/62248 files, 89730/248976 blocks (check in 2 mounts)
fsck.ext4: Unable to resolve 'UUID=47bcbd50-5ae6-47c5-88b9-463e577f7ade'
/dev/mapper/plain-misc: recovering journal
/dev/mapper/plain-misc: clean, 5658/2621440 files, 9378933/10485760 blocks
fsck died with exit status 8

Mon Aug 31 12:32:13 2009
----------------

Note: I suspect this is some timing issue in the boot sequence (udev or upstart related), as the fsck seems to be run before LVM is properly set-up on top of dm-crypt device.