[dm-crypt] backup of luks header example in the FAQ has a wrong path

.. ink .. mhogomchungu at gmail.com
Sat Jan 14 23:32:27 CET 2012


using cryptsetup 1.4.1

At the section on how to backup a luks header, the example given is below:

cryptsetup luksHeaderBackup --header-backup-file h /dev/mapper/c1


The usage of "/dev/mapper" path implies running the command on the mapper,
when i do that i get the following output:

[root at mtz build]# cryptsetup luksOpen /dev/sdc1 abc
Enter passphrase for /dev/sdc1:
[root at mtz build]# cryptsetup luksHeaderBackup --header-backup-file
backup.img  /dev/mapper/abc ; echo $?
Device /dev/mapper/abc is not a valid LUKS device.
1

The command errors out when using the mapper address as FAQ suggests.

When i use the device directly, it works as shown below:
[root at mtz build]# cryptsetup luksHeaderBackup --header-backup-file
backup.img  /dev/sdc1 ; echo $?
0

It looks like the command to backup the header is supposed to be run on the
device its self and not on the mapper as the FAQ suggests.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.saout.de/pipermail/dm-crypt/attachments/20120114/957c143a/attachment.html>


More information about the dm-crypt mailing list