From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Wed, 24 Apr 2019 21:36:00 +0200 (CEST) Received: from localhost ([88.90.129.220]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MLA6k-1h2OnV1eB0-00ICcb for ; Wed, 24 Apr 2019 21:35:59 +0200 Date: Wed, 24 Apr 2019 21:35:58 +0200 From: Heinz Diehl Message-ID: <20190424193558.GA2126@fritha.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dm-crypt] Is my LUKS header corrupted? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 24.04.2019, Greg Laun wrote: > I have a LUKS-encrypted hard drive partition that is showing the following > behavior on Kubuntu 19.04: [.....] I would suggest trying to open the device after booting from an external system, e.g. a Fedora or Arch linux boot disk. Just to rule out it isn't Kubuntu doing something weird.