And this worked fine with cryptdisks_start however the option "offset" is not understood by systemd 215. I did change init system from sysvinit to systemd, and now, after 2 reboots, I don't have any swap and my device that had UUID c836dd13-1b4e-4bfb-9be5-6e5d972aa75a has seen its start erased, and thus its UUID itself, as if I had not mentioned an offset=>>0 in crypttab.
The use case for "offset=2048" is to be able to use a UUID to identify the partition I want to have encrypted swap on. Not using an offset=>>0 parameter would unconditionally erase the whole partition, including the portion where its UUID is stored. Using any other way to identify a partition can thus cause data loss if I reparttion my disk and forget to update /etc/crypttab.
Please make systemd understand the "offset=" paramater of /etc/crypttab.
Has this problem been addressed in a subsequent systemd version?
Dear Developpers,
My /etc/crypttab contains:
cryptswap1 UUID=c836dd13- 1b4e-4bfb- 9be5-6e5d972aa7 5a /dev/urandom swap,offset= 2048,cipher= aes-cbc- essiv:sha256
And my /etc/fstab contains:
/dev/mapper/ cryptswap1 none swap sw 0 0
And this worked fine with cryptdisks_start however the option "offset" is not understood by systemd 215. I did change init system from sysvinit to systemd, and now, after 2 reboots, I don't have any swap and my device that had UUID c836dd13- 1b4e-4bfb- 9be5-6e5d972aa7 5a has seen its start erased, and thus its UUID itself, as if I had not mentioned an offset=>>0 in crypttab.
The use case for "offset=2048" is to be able to use a UUID to identify the partition I want to have encrypted swap on. Not using an offset=>>0 parameter would unconditionally erase the whole partition, including the portion where its UUID is stored. Using any other way to identify a partition can thus cause data loss if I reparttion my disk and forget to update /etc/crypttab.
Please make systemd understand the "offset=" paramater of /etc/crypttab.
Has this problem been addressed in a subsequent systemd version?
Note: related to debian bug #751707 /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 751707 )
( https:/
Thanks,
Vecu Bosseur