From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Troubleshooting: Header Conversion to argon2id
Date: Thu, 13 Sep 2018 03:53:28 +0200 [thread overview]
Message-ID: <20180913015328.GA19430@tansi.org> (raw)
In-Reply-To: <8c5025a3-efdd-02a7-d6b8-4d14dcd0beb6@riseup.net>
On Thu, Sep 13, 2018 at 02:47:00 CEST, procmem wrote:
>
>
> Guilhem Moulin:
> > 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.
> >
>
> initramfs sounds like the most versatile option. Any pointers on how to
> to this? Searching SE turns up irrelevant results.
The FAQ has an example how to do an an initrd, including dropping to
shell, in Chapter 9:
https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions#9-the-initrd-question
Regards,
Arno
--
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
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2018-09-13 1:53 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
2018-09-13 0:47 ` procmem
2018-09-13 1:53 ` Arno Wagner [this message]
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=20180913015328.GA19430@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox