Small update. After several tests, I found that if I duplicate the encrypted block device configuration line in /etc/crypttab, the upgrade is successful.
I.e., in my case:
nvme0n1p3_crypt UUID=c9ffc13a-cad1-49a2-83eb-fb9002b3ebff none luks
changes to
nvme0n1p3_crypt UUID=c9ffc13a-cad1-49a2-83eb-fb9002b3ebff none luks nvme0n1p3_crypt UUID=c9ffc13a-cad1-49a2-83eb-fb9002b3ebff none luks
I haven't tested if simply updating the timestamp on the file also does the trick.
Note: if doing this after the upgrade, it requires to re-generate initramfs.
Small update. After several tests, I found that if I duplicate the encrypted block device configuration line in /etc/crypttab, the upgrade is successful.
I.e., in my case:
nvme0n1p3_crypt UUID=c9ffc13a- cad1-49a2- 83eb-fb9002b3eb ff none luks
changes to
nvme0n1p3_crypt UUID=c9ffc13a- cad1-49a2- 83eb-fb9002b3eb ff none luks cad1-49a2- 83eb-fb9002b3eb ff none luks
nvme0n1p3_crypt UUID=c9ffc13a-
I haven't tested if simply updating the timestamp on the file also does the trick.
Note: if doing this after the upgrade, it requires to re-generate initramfs.