Forking off from issue #3368 as the scope is different

unfortunately, the information needed to diagnosis and confirm the issue is conflated into the other ticket - TLDR: the solution is to install 'openssl-1.1'

symptoms apparent in log:

systemd-cryptsetup[170]: Requested LUKS hash whirlpool is not supported.
systemd-cryptsetup[170]: Failed to load LUKS superblock on device /dev/disk/by-uuid/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx: Invalid argument

whirlpool support in openssl can be checked with:

## openssl v1.1:
$ openssl     dgst -list | grep -o whirlpool
whirlpool

## openssl-1.1 v1.1:
$ openssl-1.1 dgst -list | grep -o whirlpool
whirlpool

## openssl v3:
$ openssl     dgst -list | grep -o whirlpool

The hash algorithm in use by LUKS can be checked with:

# cryptsetup luksDump /dev/sdAN | grep whirlpool

Long-term what is the solution though?
Re-encrypting the device and avoiding whirlpool or should Parabola move to using gnutls?
On the one-hand the first option will avoid the problem for sure, and the second solution is more overhead for the maintainers.
Yet, judging with the number of CVEs that keep popping up in OpenSSL, gnutls might be giving another advantage here.
Specifically since OpenSSL seems to be deprecating code solely because they don't want to deal with maintaining it - not because of some cryptographic security reasoning.

I found the bug report from Arch:
https://bugs.archlinux.org/task/76440

I just attempted to change the hash from whirlpool to sha512, ended up with an unbootable system.
Long term, if OpenSSL will drop whirlpool this leaves only two options:
1) Wipe and install again, with a different hash algorithm (hopefully they don't deprecate sha512).
2) Maybe compile cryptsetup with gnutls instead of openssl?

Long term, if OpenSSL will drop whirlpool this leaves only two options:

its not dropped, but moved into a legacy.so library, which actually
suggests that it will be retained for the foreseeable future

the initial cryptsetup+openssl3 rebuild did not include the 'legacy' library,
and was broken the same way for many arch users - the latest one does;
so this may be solved already for the long-term