Arch Linux

xesth

Member

Registered: 2024-08-07

Posts: 2

Failed to open encryption mapping: the device is not a LUKS volume

When i start my laptop, i get this error while booting:

'ERROR: Failed to open encryption mapping: The device UUID=... is not a LUKS volume and the crypto= parameter was not specified. /dev/nvme0n1p2: clean, number/number files, number/number blocks'

here is my lsblk:

NAME               MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
zram0              253:0    0     4G  0 disk  [SWAP]
nvme0n1            259:0    0 953.9G  0 disk  
├─nvme0n1p1        259:1    0     1G  0 part  /boot
├─nvme0n1p2        259:2    0    50G  0 part  /
└─nvme0n1p3        259:3    0 902.9G  0 part  
  └─ainstnvme0n1p3 254:0    0 902.9G  0 crypt /home

I installed arch directly from iso file and i also used Archinstall. I remember that i used disk encryption setting while installing it.

Even though my system works with no problem, i want to get rid of that error. What should i do?

cryptearth

Member

Registered: 2024-02-03

Posts: 1,110

Re: Failed to open encryption mapping: the device is not a LUKS volume

don't use archinstall unless you're familiar with the manual guide and know what you do - the script is not meant as an easy installer for newcomers but to aid experienced users in rapid deployment
I eould recommend start over follow the guide

xesth

Member

Registered: 2024-08-07

Posts: 2

Re: Failed to open encryption mapping: the device is not a LUKS volume

don't use archinstall unless you're familiar with the manual guide and know what you do - the script is not meant as an easy installer for newcomers but to aid experienced users in rapid deployment
I eould recommend start over follow the guide

Is it there any other way to fix it rather than reinstalling arch?

frostschutz

Member

Registered: 2013-11-15

Posts: 1,475

Re: Failed to open encryption mapping: the device is not a LUKS volume

I can only guess you specified a wrong UUID somewhere. If the UUID is specified in the error message, you could `grep -r UUIDHERE /etc /boot` and see what (if anything) pops up. Also check your boot parameters `cat /proc/cmdline` if it's as expected or not.

faw

Member

Registered: 2007-06-09

Posts: 19

Re: Failed to open encryption mapping: the device is not a LUKS volume

Hey,

lsblk is showing that p2 / root is not a crypt block device (only home is), so it seems the system is asking "why you telling me to decrypt this block when it isn't one?"

Maybe your bootloader is telling the system to decrypt this UUID? Remove any commands / kernel options there if they exist.