I was just installing cryptsetup and cryptsetup-bin to move to
encrypted swap and got this:

Preconfiguring packages ...
Selecting previously unselected package libcryptsetup12:amd64.
(Reading database ... 437931 files and directories currently installed.)
Preparing to unpack .../libcryptsetup12_2%3a2.3.5-1_amd64.deb ...
Unpacking libcryptsetup12:amd64 (2:2.3.5-1) ...
Selecting previously unselected package cryptsetup-bin.
Preparing to unpack .../cryptsetup-bin_2%3a2.3.5-1_amd64.deb ...
Unpacking cryptsetup-bin (2:2.3.5-1) ...
Selecting previously unselected package cryptsetup.
Preparing to unpack .../cryptsetup_2%3a2.3.5-1_amd64.deb ...
Unpacking cryptsetup (2:2.3.5-1) ...
Setting up libcryptsetup12:amd64 (2:2.3.5-1) ...
Setting up cryptsetup-bin (2:2.3.5-1) ...
Setting up cryptsetup (2:2.3.5-1) ...
insserv: FATAL: service cryptdisks-early has to be enabled to use service cryptdisks
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13) ...
[master 46cca18] committing changes in /etc made by "apt-get install cryptsetup cryptsetup-bin"


I’m guessing this isn’t fatal for me because I only use it for swap at
the moment but maybe failure to install the service may trouble others?

Dixi quod…

An interesting observation:

When I did 'sudo cleanenv / /etc/init.d/cryptdisks-early start' after
the installation, I needed to manually confirm that, yes, I want to
overwrite the existing signature (swap) from the block device. Maybe
this is what caused that error? I had changed /etc/crypttab before
installing the packages so maybe that…

… though, on the other hand, insserv is just for ordering init scripts,
right? Perhaps something else was the cause — I’m just noting my ob‐
servation.

bye,
//mirabilos