Re: How to resume decryption on LUKS1 in-place

Ondrej Kozina <[email protected]> Mon, 4 Mar 2024 11:59:28 +0100
Newsgroups dev.linux.lists.cryptsetup
Message-ID <[email protected]>
On 01/03/2024 14:12, xndr wrote:
> Thank you for the assist.
> 
> We've taken the advice to migrate the data to a backup and after
> reattempted using the command:-
> 
> cryptsetup reencrypt --decrypt
> --uuid=LUKS-aaecbfc4-459a-4cf9-9a34-fd4af43b8be0  /dev/sdd
> 
> This returns:-
> 
> Device /dev/sdd is not a valid LUKS device.

Ok, this is a bug (regression in fact) in cryptsetup v2.5.0 which is not 
yet fixed.

The most straightforward workaround would be to install cryptsetup 
v2.4.3 and run following command using legacy cryptsetup-reencrypt utility:

"cryptsetup-reencrypt --decrypt --uuid 
aaecbfc4-459a-4cf9-9a34-fd4af43b8be0  /dev/sdd"

(no need to add 'LUKS-' prefix in --uuid parameter).

I'll figure out a fix for it (feel free to open issue on 
https://gitlab.com/cryptsetup/cryptsetup if interested).

Thank you for the feedback!
Ondrej