initrdscripts: Make cryptsetup fail hard in unexpected conditions

[mtoman]

This patch adds a set of checks that make sure that the partition layout is as expected on a system with encrypted disks.

---

Contributor checklist

• Changes have been tested
  • Covered in automated test suite
  • Manual test case recorded
• Change-type present on at least one commit
• Signed-off-by is present
• The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

• When submitting a review, please pick:
  • 'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
  • 'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
  • 'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

[github-actions]

Website deployed to CF Pages, 👀 preview link https://9b90b1a3.balena-os.pages.dev

[jakogut]

We'll probably need to change this from always running, to always running when the device is in user mode. Otherwise, systems without secure boot may not boot.

[rettier]

@mtoman we have seen issues with this change because lsblk sometimes seems to output an extra whitespace. here for example:

$ LUKS_PARTITIONS=$(lsblk -nlo "kname,uuid,fstype,partlabel" "/dev/${BOOT_DEVICE}" | grep "crypto_LUKS")
$ echo $LUKS_PARTITIONS
sda
sda1  3845-FC2                                                           vfat                balena-efi
sda2  0b587cd9-60bd-47dd-909e-f23e8f7b6e36 crypto_LUKS resin-boot
...

there are 2 spaces between sda2 and 0b...
when cutting the UUID later via cut -d " " -f2 a whitespace is actually extracted.

Other uses of lblk always cut the first column (-f1) thus were never affected by this.

I suggest adding tr -s " " in order to strip any duplicate whitespaces and make the behaviour consistent.

[mtoman]

Thanks for the comment @rettier is this still the case with the latest master? We have observed this as well, shortly after merging the PR and c9544aa was supposed to fix it.

[rettier]

@mtoman thanks for the info, i was looking through the latest merges but must have missed this one. It does indeed fix our issue.

Sorry for the unnecessary comment.