From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDosnEIFQy9g for ; Mon, 4 Mar 2013 14:07:34 +0100 (CET) Received: from mx.logtenberg.eu (mx.logtenberg.eu [IPv6:2a00:f60::1:229]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Mon, 4 Mar 2013 14:07:33 +0100 (CET) Received: by mx.logtenberg.eu (Postfix) with ESMTPSA id 503CB6E (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) for ; Mon, 4 Mar 2013 13:58:31 +0100 (CET) Message-ID: <51349A77.4070709@logtenberg.eu> Date: Mon, 04 Mar 2013 13:58:31 +0100 From: Erik Logtenberg MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [dm-crypt] Device $dev is not a valid LUKS device. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Hi all, I've been using dm-crypt for quite some years now, and every now and then I am very unpleasantly surprised by the message that my entire volume can no longer be read: Device /dev/disk/by-path/ip-foo.bar:mainstorage-lun-1 is not a valid LUKS device. In this case the iscsi server was rebooted while the volume was still mounted. The volume is used for making backups and no backups were currently made, so no actual writes got lost. Nevertheless after reboot it no longer recognizes my luks volume. I've had this kind of malice before and at that time was unable to fix it. So in the end I gave up, created a new luks volume and started from scratch. However I hope that is not how every future power failure is going to end up. Is there anything I can do to fix this volume or anything I can do to prevent such a simple event from causing such catastrophic results? Kind regards, Erik.