From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com
 [IPv6:2a00:1450:400c:c03::233])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Fri,  1 Aug 2014 08:20:24 +0200 (CEST)
Received: by mail-we0-f179.google.com with SMTP id u57so3755611wes.38
 for <dm-crypt@saout.de>; Thu, 31 Jul 2014 23:20:23 -0700 (PDT)
Received: from [192.168.2.28] (56.157.broadband5.iol.cz. [88.100.157.56])
 by mx.google.com with ESMTPSA id u7sm5409154wif.3.2014.07.31.23.20.22
 for <dm-crypt@saout.de>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 31 Jul 2014 23:20:22 -0700 (PDT)
Message-ID: <53DB31A5.6010508@gmail.com>
Date: Fri, 01 Aug 2014 08:20:21 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <20140801035717.GA28952@tansi.org>
In-Reply-To: <20140801035717.GA28952@tansi.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Kernel update: "Failed to access temporary keystore
 device."
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt <dm-crypt@saout.de>

On 08/01/2014 05:57 AM, Arno Wagner wrote:
> I just tried to upgrade my kernel from 3.10.48 to 3.14.15
> (kernel.org). This is Debian wheezy. After the update, I
> get "Failed to access temporary keystore device." when 
> trying to unlock my LUKS partitions. As far as I can tell
> I have not changed anything relevant in the kernel config,
> I just did a "make oldconfig" with the old kernel .config.

Hi,

for some strange reason I am tempting to ask if you read
the FAQ but... ;-)

Well, seriously: this happens when temporary mapped keyslot device
cannot be read (but kernel mapping was created successfully).
Not common problem, I do not even remember someone reported this... 

It seems like some udev/kernel compatibility problem (Debian
has non-standard dm/lvm udev rules btw).
Either bad access rights to device node or device node is missing
(the second is probably the issue).
It is possible you will need to use new udev or something.

Can you paste the command with added --debug?

Can you try to boot Debian provided kernel - does it work?
(Anyway, I am using custom kernel in Debian for years without problem
but I am using unstable repo.)

Milan