Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #63783 > unrolled thread
| Started by | Lars Kruse <devel@sumpfralle.de> |
|---|---|
| First post | 2019-04-06 18:30 +0200 |
| Last post | 2019-09-01 22:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
Bug#926533: linux-image-armmp-lpae: Fail to mount cryptsetup device: missing aes-xts-plain64 cipher Lars Kruse <devel@sumpfralle.de> - 2019-04-06 18:30 +0200
Bug#926533: marked as done (linux-image-armmp-lpae: Fail to mount cryptsetup device: missing aes-xts-plain64 cipher) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-09-01 22:00 +0200
| From | Lars Kruse <devel@sumpfralle.de> |
|---|---|
| Date | 2019-04-06 18:30 +0200 |
| Subject | Bug#926533: linux-image-armmp-lpae: Fail to mount cryptsetup device: missing aes-xts-plain64 cipher |
| Message-ID | <xJWmB-6pC-1@gated-at.bofh.it> |
Package: linux-image-armmp-lpae Version: 4.19+104 Severity: normal Dear Maintainer, after upgrading from 4.9.144-3 to 4.19+104 I am not able to mount cryptsetup devices anymore. # cryptsetup luksOpen /dev/lvm-foo/crypto foo Enter passphrase for /dev/lvm-foo/crypto: device-mapper: reload ioctl on failed: No such file or directory Failed to setup dm-crypt key mapping for device /dev/lvm-foo/crypto. Check that kernel supports aes-xts-plain64 cipher (check syslog for more info). device-mapper: remove ioctl on temporary-cryptsetup-3150 failed: No such device or address device-mapper: table ioctl on failed: No such device or address The output of dmesg is: device-mapper: table: 253:8: crypt: Error allocating crypto tfm device-mapper: ioctl: error adding target to table The respective LUKS header of the cryptsetup device looks like this: # cryptsetup luksDump /dev/lvm-foo/crypto LUKS header information for /dev/lvm-foo/crypto Version: 1 Cipher name: aes Cipher mode: xts-plain64 Hash spec: sha1 Payload offset: 4096 MK bits: 256 ... Maybe the lack of the "aes-xts-plain64" cipher is related to the following? # dpkg -L linux-image-4.9.0-8-armmp-lpae | grep aes /lib/modules/4.9.0-8-armmp-lpae/kernel/drivers/crypto/omap-aes.ko # dpkg -L linux-image-4.19.0-4-armmp-lpae | grep aes [no output] I am using a BananaPi M1 board. Thank you for your time! Cheers, Lars
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2019-09-01 22:00 +0200 |
| Subject | Bug#926533: marked as done (linux-image-armmp-lpae: Fail to mount cryptsetup device: missing aes-xts-plain64 cipher) |
| Message-ID | <yBEaZ-3R0-3@gated-at.bofh.it> |
| In reply to | #63783 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Sun, 1 Sep 2019 21:47:58 +0200 with message-id <20190901214758.303e2f39@erker.lan> and subject line Re: linux-image-armmp-lpae: Fail to mount cryptsetup device: missing aes-xts-plain64 cipher has caused the Debian Bug report #926533, regarding linux-image-armmp-lpae: Fail to mount cryptsetup device: missing aes-xts-plain64 cipher to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 926533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926533 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web