If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot.
For partitions encrypted using dm-crypt you will be shown the following prompt during the boot:
Starting early crypto disks...
part_crypt(starting) Enter LUKS passphrase:
In the first line of the prompt,
part is the name of the underlying partition, e.g. sda2 or md0. You are now probably wondering for which volume you are actually entering the passphrase. Does it relate to your
/home? Or to
/var? Of course, if you have just one encrypted volume, this is easy and you can just enter the passphrase you used when setting up this volume. If you set up more than one encrypted volume during the installation, the notes you wrote down as the last step in Section 18.104.22.168, “Configuring Encrypted Volumes” come in handy. If you did not make a note of the mapping between
and the mount points before, you can still find it in
/etc/fstab of your new system.
The prompt may look somewhat different when an encrypted root file system is mounted. This depends on which initramfs generator was used to generate the initrd used to boot the system. The example below is for an initrd generated using
Begin: Mounting root file system... ... Begin: Running /scripts/local-top ... Enter LUKS passphrase:
No characters (even asterisks) will be shown while entering the passphrase. If you enter the wrong passphrase, you have two more tries to correct it. After the third try the boot process will skip this volume and continue to mount the next filesystem. Please see Section 7.2.1, “Troubleshooting” for further information.
After entering all passphrases the boot should continue as usual.
If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases.
The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again.
The easiest case is for encrypted volumes holding data like
/srv. You can simply mount them manually after the boot.
However for dm-crypt this is a bit tricky. First you need to register the volumes with device mapper by running:
This will scan all volumes mentioned in
/etc/crypttab and will create appropriate devices under the
/dev directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:
If any volume holding noncritical system files could not be mounted (
/var), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way is to just reboot the computer.