Re: [dm-crypt] Device $dev is not a valid LUKS device.

[Arno Wagner <arno@wagner.name>]

Hi Erik,

first, you can make a header-backup, see the FAQ. Second, you can 
investigate what destroys the header. The same thing could
well destroy a filesystem, RAID-superblock, etc.
Or put differently: Something is very, very wrong in
your set-up. Loss of the LUKS header can only happen if
einther the user does it (directly or indirectly) or
somethign is broken. 

Arno

On Mon, Mar 04, 2013 at 01:58:31PM +0100, Erik Logtenberg wrote:
> 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.
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell