Bug 1039821 - No matter what the password is, cryptsetup during boot fails horribly
Summary: No matter what the password is, cryptsetup during boot fails horribly
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cryptsetup
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Broz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-10 05:25 UTC by Rudd-O DragonFear
Modified: 2015-06-29 13:27 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:27:10 UTC
Type: Bug


Attachments (Terms of Use)
screenie 1 (1.19 MB, image/jpeg)
2013-12-10 05:26 UTC, Rudd-O DragonFear
no flags Details
screenie 2 (1.77 MB, image/jpeg)
2013-12-10 05:26 UTC, Rudd-O DragonFear
no flags Details
screenie 3 (1.61 MB, image/jpeg)
2013-12-10 05:27 UTC, Rudd-O DragonFear
no flags Details

Description Rudd-O DragonFear 2013-12-10 05:25:28 UTC
rpm -q kernel cryptsetup
kernel-3.10.7-200.fc19.x86_64
kernel-3.11.3-201.fc19.x86_64
kernel-3.11.10-300.fc20.x86_64
cryptsetup-1.6.2-1.fc20.x86_64

The latest initrd fails with the error screenshots that I will attach to this bug report.

Essentially no password will satisfy cryptsetup luksOpen.  That is the bug.

Comment 1 Rudd-O DragonFear 2013-12-10 05:26:19 UTC
Created attachment 834640 [details]
screenie 1

Comment 2 Rudd-O DragonFear 2013-12-10 05:26:44 UTC
Created attachment 834641 [details]
screenie 2

Comment 3 Rudd-O DragonFear 2013-12-10 05:27:15 UTC
Created attachment 834642 [details]
screenie 3

Comment 4 Ondrej Kozina 2013-12-10 16:17:17 UTC
Seems to me like there are some missing kernel modules in initrd. At least dm-crypt module. See file 3.jpg:

The line with "crypt: unknown target type"

Perhaps dracut bug or FedUp bug? Did you actually make an distro upgrade from F19 to F20?

Comment 5 Ondrej Kozina 2013-12-10 16:33:28 UTC
Could you please reboot to the working kernel and paste here output from following command?

lsinitrd /boot/initramfs-3.11.10-300.fc20.x86_64.img | grep crypt

(provided this is the affected initramfs image)

Comment 6 Rudd-O DragonFear 2014-04-15 11:43:32 UTC
Working kernel:
lsinitrd /boot/initramfs-3.12.5-200.fc19.x86_64.img | grep crypt                                                                                                                                                                              
crypt
-rw-r--r--   1 root     root          117 Apr 15 03:54 etc/crypttab
-rwxr-xr-x   1 root     root       157872 Apr 15 03:54 usr/lib64/libcryptsetup.so.4.5.0
lrwxrwxrwx   1 root     root           22 Apr 15 03:54 usr/lib64/libcryptsetup.so.4 -> libcryptsetup.so.4.5.0
-rwxr-xr-x   1 root     root       531696 Apr 15 03:54 usr/lib64/libgcrypt.so.11.8.2
lrwxrwxrwx   1 root     root           19 Apr 15 03:54 usr/lib64/libgcrypt.so.11 -> libgcrypt.so.11.8.2
-rwxr-xr-x   1 root     root         6898 Mar 19 09:16 usr/lib/dracut-crypt-lib.sh
-rwxr-xr-x   1 root     root         3276 Mar 19 09:16 usr/lib/dracut/hooks/cmdline/30-parse-crypt.sh
drwxr-xr-x   2 root     root            0 Apr 15 03:54 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto
-rw-r--r--   1 root     root        20615 Dec 17 14:44 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto/crc32c-intel.ko
-rw-r--r--   1 root     root         8343 Dec 17 14:45 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto/crc32-pclmul.ko
-rw-r--r--   1 root     root        11111 Dec 17 14:44 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto/crct10dif-pclmul.ko
-rw-r--r--   1 root     root        11591 Dec 17 14:45 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto/ghash-clmulni-intel.ko
drwxr-xr-x   2 root     root            0 Apr 15 03:54 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/crypto
-rw-r--r--   1 root     root         5959 Dec 17 14:45 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/crypto/arc4.ko
-rw-r--r--   1 root     root        31439 Dec 17 14:46 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/drivers/md/dm-crypt.ko
-rw-r--r--   1 root     root          366 Apr  7 19:10 usr/lib/systemd/system/cryptsetup.target
-rwxr-xr-x   1 root     root        61400 Apr 15 03:54 usr/lib/systemd/systemd-cryptsetup
-rwxr-xr-x   1 root     root        53552 Apr 15 03:54 usr/lib/systemd/system-generators/systemd-cryptsetup-generator
lrwxrwxrwx   1 root     root           20 Apr 15 03:54 usr/lib/systemd/system/sysinit.target.wants/cryptsetup.target -> ../cryptsetup.target
-rwxr-xr-x   1 root     root         4336 Mar 19 09:16 usr/sbin/cryptroot-ask
-rwxr-xr-x   1 root     root          887 Mar 19 09:16 usr/sbin/crypt-run-generator
-rwxr-xr-x   1 root     root        61080 Apr 15 03:54 usr/sbin/cryptsetup

Malfunctioning kernel:
lsinitrd /boot/initramfs-3.13.9-200.fc20.x86_64.img | grep crypt
crypt
-rw-r--r--   1 root     root          117 Apr 15 04:33 etc/crypttab
-rwxr-xr-x   1 root     root       157872 Apr 15 04:33 usr/lib64/libcryptsetup.so.4.5.0
lrwxrwxrwx   1 root     root           22 Apr 15 04:33 usr/lib64/libcryptsetup.so.4 -> libcryptsetup.so.4.5.0
-rwxr-xr-x   1 root     root       531696 Apr 15 04:33 usr/lib64/libgcrypt.so.11.8.2
lrwxrwxrwx   1 root     root           19 Apr 15 04:33 usr/lib64/libgcrypt.so.11 -> libgcrypt.so.11.8.2
-rwxr-xr-x   1 root     root         6898 Mar 19 09:16 usr/lib/dracut-crypt-lib.sh
-rwxr-xr-x   1 root     root         3276 Mar 19 09:16 usr/lib/dracut/hooks/cmdline/30-parse-crypt.sh
drwxr-xr-x   2 root     root            0 Apr 15 04:33 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto
-rw-r--r--   1 root     root        20615 Dec 17 14:44 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto/crc32c-intel.ko
-rw-r--r--   1 root     root         8343 Dec 17 14:45 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto/crc32-pclmul.ko
-rw-r--r--   1 root     root        11111 Dec 17 14:44 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto/crct10dif-pclmul.ko
-rw-r--r--   1 root     root        11591 Dec 17 14:45 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/arch/x86/crypto/ghash-clmulni-intel.ko
drwxr-xr-x   2 root     root            0 Apr 15 04:33 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/crypto
-rw-r--r--   1 root     root         5959 Dec 17 14:45 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/crypto/arc4.ko
-rw-r--r--   1 root     root        31439 Dec 17 14:46 usr/lib/modules/3.12.5-200.fc19.x86_64/kernel/drivers/md/dm-crypt.ko
-rw-r--r--   1 root     root          366 Apr  7 19:10 usr/lib/systemd/system/cryptsetup.target
-rwxr-xr-x   1 root     root        61400 Apr 15 04:33 usr/lib/systemd/systemd-cryptsetup
-rwxr-xr-x   1 root     root        53552 Apr 15 04:33 usr/lib/systemd/system-generators/systemd-cryptsetup-generator
lrwxrwxrwx   1 root     root           20 Apr 15 04:33 usr/lib/systemd/system/sysinit.target.wants/cryptsetup.target -> ../cryptsetup.target
-rwxr-xr-x   1 root     root         4336 Mar 19 09:16 usr/sbin/cryptroot-ask
-rwxr-xr-x   1 root     root          887 Mar 19 09:16 usr/sbin/crypt-run-generator
-rwxr-xr-x   1 root     root        61080 Apr 15 04:33 usr/sbin/cryptsetup

Comment 7 Rudd-O DragonFear 2014-04-15 11:44:39 UTC
luks-xxxxxx-xxxxxxxxxxxxxxxxxxx: 0 xxxxxxxxx crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 8:0 4096 1 allow_discards

This is the device encryption type.

Comment 8 Fedora End Of Life 2015-05-29 09:57:12 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2015-06-29 13:27:10 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.