From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 112631] Cannot open encrypted Luks root filesystem
Date: Fri, 19 Feb 2016 18:52:19 +0000 [thread overview]
Message-ID: <bug-112631-13602-i0ZGddtzGy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-112631-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=112631
Karl Sponser <karl.sponser@web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |karl.sponser@web.de
--- Comment #2 from Karl Sponser <karl.sponser@web.de> ---
I can confirm the problem on Fedora ARM with the RPI Kernel 4.1.18 (previous
kernels worked). It's not possible to open a luks container nor format a new
device:
# cryptsetup luksOpen /dev/vg1/test1 luks-test1
Enter passphrase for /dev/vg1/test1:
Failed to setup dm-crypt key mapping for device /dev/vg1/test1.
Check that kernel supports aes-xts-plain64 cipher (check syslog for more info).
# cryptsetup luksFormat /dev/vg1/test2
WARNING!
========
This will overwrite data on /dev/vg1/test2 irrevocably.
Are you sure? (Type uppercase yes): YES
Enter passphrase:
Verify passphrase:
Failed to setup dm-crypt key mapping for device /dev/vg1/test2.
Check that kernel supports aes-xts-plain64 cipher (check syslog for more info).
Even if the message tells to check syslog for more information, there's no
entry in /var/log/messages nor in dmesg output.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-02-19 18:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 20:08 [Bug 112631] New: Cannot open encrypted Luks root filesystem bugzilla-daemon
2016-02-17 20:10 ` [Bug 112631] " bugzilla-daemon
2016-02-17 20:22 ` bugzilla-daemon
2016-02-17 20:30 ` bugzilla-daemon
2016-02-19 18:52 ` bugzilla-daemon [this message]
2016-02-20 2:28 ` bugzilla-daemon
2016-02-20 10:15 ` bugzilla-daemon
2016-02-20 18:46 ` bugzilla-daemon
2016-02-21 12:00 ` bugzilla-daemon
2016-02-21 12:02 ` bugzilla-daemon
2016-02-21 12:55 ` bugzilla-daemon
2016-02-21 14:23 ` bugzilla-daemon
2016-02-21 16:12 ` bugzilla-daemon
2016-02-21 16:18 ` [Bug 112631] Cannot open encrypted Luks filesystem. Cruptsetup error bugzilla-daemon
2016-02-21 16:19 ` bugzilla-daemon
2016-02-21 16:20 ` bugzilla-daemon
2016-02-21 16:22 ` bugzilla-daemon
2016-02-21 16:35 ` bugzilla-daemon
2016-02-21 20:14 ` bugzilla-daemon
2016-02-21 21:27 ` bugzilla-daemon
2016-02-23 8:34 ` bugzilla-daemon
2016-02-23 9:37 ` bugzilla-daemon
2016-02-23 19:41 ` bugzilla-daemon
2016-02-23 20:30 ` bugzilla-daemon
2016-02-23 20:52 ` bugzilla-daemon
2016-02-24 21:01 ` bugzilla-daemon
2016-03-07 17:57 ` bugzilla-daemon
2016-03-07 18:03 ` bugzilla-daemon
2016-03-11 17:38 ` bugzilla-daemon
2016-03-11 17:43 ` bugzilla-daemon
2016-03-11 17:43 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-112631-13602-i0ZGddtzGy@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.