From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <arno@wagner.name>
Received: from v1.tansi.org (mail.tansi.org [84.19.178.47])
 by mail.server123.net (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu, 13 Sep 2018 03:53:29 +0200 (CEST)
Received: from gatewagner.dyndns.org (unknown [212.51.156.222])
 by v1.tansi.org (Postfix) with ESMTPA id 0848314001D
 for <dm-crypt@saout.de>; Thu, 13 Sep 2018 03:52:58 +0200 (CEST)
Date: Thu, 13 Sep 2018 03:53:28 +0200
From: Arno Wagner <arno@wagner.name>
Message-ID: <20180913015328.GA19430@tansi.org>
References: <3981e376-6bc1-eafa-661f-800527d1edd8@riseup.net>
 <0a634f10-a4fe-54e3-b6ad-edd3f7682ec3@redhat.com>
 <05d42a4b-7439-0f5a-21b0-d79d1195b07f@riseup.net>
 <cdad2fc3-5013-0412-2634-3a11fe04a3bc@gmail.com>
 <48f41120-27ae-cef3-8bb0-482eb164d468@riseup.net>
 <20180912155201.GA31331@localhost.localdomain>
 <8c5025a3-efdd-02a7-d6b8-4d14dcd0beb6@riseup.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8c5025a3-efdd-02a7-d6b8-4d14dcd0beb6@riseup.net>
Subject: Re: [dm-crypt] Troubleshooting: Header Conversion to argon2id
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <https://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <https://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <https://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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