From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.saout.de (Postfix) with ESMTP for ; Sun, 30 Aug 2009 09:39:24 +0200 (CEST) Received: from liesel.fancy-poultry.org (localhost [127.0.0.1]) by liesel.fancy-poultry.org (Postfix) with ESMTP id 2B5EF18CB85AA for ; Sun, 30 Aug 2009 09:44:11 +0200 (CEST) Date: Sun, 30 Aug 2009 09:44:10 +0200 Message-ID: <87k50lrbjp.wl%htd@fancy-poultry.org> From: Heinz Diehl In-Reply-To: References: <4A97DF3D.6010504@redhat.com> <87zl9ibmcz.wl%htd@fancy-poultry.org> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: Re: [dm-crypt] Command failed: Can not access device on luksOpen List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de At Sun, 30 Aug 2009 00:25:57 +0100, Paul Bradley wrote: > Incidentally, there are also some files in /dev/mapper which I've never seen before called temporary-cryptsetup-xxxx > (xxxx being a 4 digit number), there are 4 of these files. Perhaps these are a symptom of the problem, as I have never > seen them before. I would suggest to delete them, reboot and try again. Alternatively, you could try to close them via the "cryptsetup luksClose" command.