You are not logged in.

#1 2013-11-08 16:18:41

gcala
Member
Registered: 2010-06-03
Posts: 9

Unknown filesystem type crypto_LUKS

Hi, I have spare space on my HD so I decided to experiment with encryption following this wiki:

https://wiki.archlinux.org/index.php/dm-crypt_with_LUKS

In summary:

  • created boot (sda6) and root (sda7) partitions

  • formatted boot as ext2 and root with passphrase and then with ext4

  • installed the base system

  • generated a new initramfs as explained in the wiki:

    MODULES="dm_mod ext4"
    HOOKS="base udev autodetect modconf block keymap encrypt filesystems keyboard fsck"
  • added cryptdevice=<device>:<dmname> to kernel boot options:

    linux   /vmlinuz-linux cryptdevice=/dev/sda7:cryptroot root=UUID=d3505fe1-4a29-4841-8e80-e953442d8d30 ro  quiet
  • restarted pc

On boot it asks for passphrase, but after that it stops with an error regarding crypto_LUKS; here the complete message:

A password is required to access the cryptroot volume:
Enter passphrase for /dev/sda7
fsck: fsck.crypto_LUKS: not founf
fsck: error 2 while executing fsck.crypto_LUKS for /dev/sda7
ERROR: fsck failed on '/dev/sda7'
********************* WARNING ***********************
*                                                   *
*  The root device is not configured to be mounted  *
*  read-write! It may be fsck'd again later.        *
*                                                   *
*****************************************************
mount: unknown filesystem type 'crypto_LUKS'
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs /]#

Here it is my fstab: http://pastebin.archlinux.fr/474004
and lsblk output: http://pastebin.archlinux.fr/474005

Any idea about the problem?

Thanks for your time.

Offline

#2 2013-11-08 18:04:39

ANOKNUSA
Member
Registered: 2010-10-22
Posts: 2,141

Re: Unknown filesystem type crypto_LUKS

There are two discrepencies between your kernel parameters and fstab:

1) The kernel parameter UUID for real root differs from the UUID given for /dev/mapper/cryptroot in your fstab; if cryptroot is your real root partition, the UUIDs should be the same.
2) Your fstab instructs the system to mount the root partition as read-write, while the kernel parameters specify read-only. (the kernel parameter should be read-write, which is what the warning in the output above is about).

Change those and see if it helps.

Offline

Board footer

Powered by FluxBB