I will confess that I don't fully recall what I did when I set this all up, but I was given an option to encrypt my home directory, and I took it.

Lately, I've started seeing an occasional error on boot: my machine complains that it can't boot /dev/mapper/cryptswap1.

For a while it would just hang, but after a recent update I noticed it offering me the option to hit esc and drop into a shell to resolve the problem. Actually hitting esc, though, just lets me proceed to the login screen.

The whole thing is (not surprisingly) kind of nervewracking because I don't know what the problem is.

I'm on Karmic.

Here's my fstab:

[0 amanda@luna ~]$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda5 during installation
UUID=a937a8a8-6320-4f3e-9636-b2a92403065f / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
#UUID=73bc0726-ed56-43ca-9827-06ad56f4d98e none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/mapper/cryptswap1 none swap sw 0 0