From: Guilhem Moulin <guilhem@fripost.org>
To: procmem <procmem@riseup.net>
Cc: dm-crypt@saout.de, whonix-devel@whonix.org
Subject: Re: [dm-crypt] Troubleshooting: Header Conversion to argon2id
Date: Wed, 12 Sep 2018 17:52:01 +0200 [thread overview]
Message-ID: <20180912155201.GA31331@localhost.localdomain> (raw)
In-Reply-To: <48f41120-27ae-cef3-8bb0-482eb164d468@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Hi,
On Wed, 12 Sep 2018 at 15:21:00 +0000, procmem wrote:
> cryptsetup convert /dev/vda5 --type luks2 --debug
> […]
> Cannot convert device /dev/vda5 which is still in use.
> […]
> Command failed with code -5 (device already exists or device is busy).
As the error message indicates, you need to remove (ie, close) the
mapped device first. If that device is required for your system to run
(for instance if it's holding the root file system) you won't be able to
run `cryptsetup luksClose $name` from the main system; however you
should be able to perform `cryptsetup convert` from a live CD, or from
the initramfs image.
Also, if as you hinted at you're using a detached header, you'll need to
pass --header=/path/to/header to `cryptsetup convert`.
Cheers,
--
Guilhem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-12 16:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 17:09 [dm-crypt] Troubleshooting: Header Conversion to argon2id procmem
2018-09-11 17:20 ` Ondrej Kozina
2018-09-11 17:53 ` procmem
2018-09-12 4:16 ` procmem
2018-09-12 4:44 ` Milan Broz
2018-09-12 15:21 ` procmem
2018-09-12 15:52 ` Guilhem Moulin [this message]
2018-09-13 0:47 ` procmem
2018-09-13 1:53 ` Arno Wagner
2018-09-13 1:58 ` Guilhem Moulin
2018-09-13 14:13 ` procmem
2018-09-13 15:00 ` Ondrej Kozina
2018-09-13 14:22 ` procmem
2018-09-13 16:02 ` Guilhem Moulin
2018-09-14 0:21 ` procmem
2018-09-14 7:10 ` Ondrej Kozina
2018-09-14 8:20 ` Ondrej Kozina
2018-09-15 1:33 ` procmem
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180912155201.GA31331@localhost.localdomain \
--to=guilhem@fripost.org \
--cc=dm-crypt@saout.de \
--cc=procmem@riseup.net \
--cc=whonix-devel@whonix.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.