Auto-mount encrypted partitions at boot

Mounting encrypted partitions manually can be annoying. This post will show you how to mount encrypted partitions at boot automatically.

This post is connected to the previous post, where you learned how to encrypt your hard drive in Linux with LUKS. In this post, you will learn how to mount encrypted partitions at boot automatically.

You can watch the video tutorial or continue reading below.

Set up auto-mount at boot

First, check the name of your encrypted partition.

Checking the partition
Checking the partition

In this example, my encrypted partition is sdb1, depending on the configuration of your system, this name may be different

Next, obtain the UUID of the encrypted device.

sudo cryptsetup luksUUID /dev/sdb1
Showing the partition's UUID
Showing the partition's UUID

Now, edit /etc/crypttab:

sudo nano /etc/crypttab

By adding this line:

sdb1 /dev/disk/by-uuid/<UUID of block device> none luks

The format of the entry in /etc/crypttab is as follows.

  • sdb1 is the name of the encrypted device.
  • fd3c01ad-0e59-4bc1-9bda-7c61e00b36cf is the UUID we have just got.
  • none means we do not use any key file and the system will ask your encryption password to decrypt the partition. So, you can also use a key file here, if your system partition is encrypted already. I personally do not encrypt my system partition and I assume most users also do not encrypt it. So, just use none here.
  • luks is the disk encryption specification.

Ctrl+O to save the changes. And Ctrl+X to exit from nano editor.

Finally, create a folder where you want to mount your encrypted partition.

sudo mkdir /mnt/encrypted_sdb1

Then, edit /etc/fstab file.

sudo nano /etc/fstab

Next, add the following to add this mount point:

/dev/mapper/sdb1 /mnt/encrypted_sdb1 ext4
Adding the mount point to fstab file
Adding the mount point to the fstab file

Let’s explain the entry:

  • sdb1 is the encrypted device. If your device name different, replace sdb1.
  • encrypted_sdb1 is the mounting point we have just created.

Ctrl+O to save the changes. And Ctrl+X to exit from nano editor.

Then, reboot your system.

Test the mounting during boot

Next, you will have to type a decryption password during the system boot.

Entering the passphrase on the boot system
Entering the passphrase on the boot system

After you enter it, the encrypted partition should be auto-mounted.

If I open the file manager and navigate to the place where I specified the mounting point, you will see the encrypted partition has been mounted automatically.

Showing the encrypted partition mounted
Showing the encrypted partition mounted

There are the two files we created during the encryption described in the previous post.

Now, you know how to mount encrypted partitions at boot.


This way to mount encrypted partitions at boot works only for LUKS encryption. If you use any other encryption method, auto-mounting settings may differ. So, I recommend using LUKS encryption that I showed in this previous post. Read it if you missed it.

You can also read 10 things to do after installing KDE Neon.

Average Linux User
Average Linux User I am the founder of the Average Linux User project, which is a hobby I work on at night. During the day I am a scientist who uses computers to analyze genetic data.



Works great on Manjaro (Kernel 5.10, all updates as of 06/03/2021). Thank you so so much for taking the time to write this tutorial, and for its clarity. Worked like a charm and to be honest I prefer not having a key and instead having to enter the pswd myself; that’s kind of the point of encryption! Thanks again :-)


Beautiful and much easier than the other methods with key files.

I can confirm this works on Ubuntu Desktop 20.04.1 LTS. My setup is a fully encrypted system disk (encrypted at Ubuntu install) + another data disk with the same encryption password. I wanted both the disk to be mounted at boot. Because the password is the same for the 2 disks, I enter the password once at boot and it makes everything available as intended. Thanks!


Curious how/whether this can work on a headless server instance without I/O during boot. Is this not recommended for that use-case?

I'm using this for a backup drive attached to my home server.

Learn how to write in Markdown with this Quick Reference.
Notify me of new comments on this post.
* E-mail is used to display Gravatar.