[pkg-cryptsetup-devel] Bug#1037973: Patch to fix cryptsetup: option 'tcrypt-system' in crypttab is unknown

Paul Richards paulrichards321 at gmail.com
Sun Jan 25 01:24:27 GMT 2026


Hello,

I have the same problem, with a Windows 11 C:\ drive encrypted as a
veracrypt system drive and trixie gives me the same error and cannot
successfully mount the partition automatically on boot.

Attached is a patch to fix the bug reported in #1037979.

The file that has the problem is:
/usr/lib/cryptsetup/functions
(in the cryptsetup package.)

After applying this patch, running update-initramfs, then rebooting I
am able to automatically mount the veracrypt system drive. It is still
able to mount other normal non-system veracrypt partitions as long as
you don't use the 'tcrypt-system' flag on those partitions in
/etc/crypttab. The 'tcrypt-system' flag for veracrypt system
partitions will need to come on the same line after the tcrypt flag to
work properly.

In my /etc/crypttab file the line is similar to:

unencrypted_c_drive
/dev/disk/by-partuuid/<c-drive-veracrypt-partition-uuid>
tcrypt,tcrypt-veracrypt,tcrypt-system

That same crypttab line entry also works fine for me on RHEL 10.

Hope that helps!

Paul Franklin Richards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: functions.patch
Type: text/x-patch
Size: 1813 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20260124/15f3f577/attachment.bin>


More information about the pkg-cryptsetup-devel mailing list