I really don’t know what to suggest here. As you mentioned, this used to
work. If you are only using LUKS for swap, maybe you could just remove
it from crypttab and run the appropriate commands manually in rc.local
or a custom systemd unit.
--
You received this bug notification because you are a
Hey Richard,
OK I understand why this order has to be kept dunring boot amd I understand it
is a personal problem and this bug can be closed.
It would be nice if you could point me to a workaround for my
installation as I would love to only encrypt swap and home as we have no
native zfs
If the pool is on top of LUKS (a relatively common configuration when
ZFS and cryptsetup are both being used), then you'd need cryptsetup
first. My advice is that you should either stop encrypting swap or start
encrypting the whole pool. Hopefully in another (Ubuntu) release or two,
we'll have
Hi Richard,
thank you for your reply, but that didn't fix the problem.
It is more that at the moment when cryptsetup tries to configure the
cryptdevice on /dev/zvol/rpool/swap, the zpool is not imported. So
cryptsetup runs in timeout and drops me in a initramfs shell.
When I import the pool
Try adding initramfs as an option in /etc/crypttab. That's the approach
I use when putting the whole pool on a LUKS device, and is necessary due
to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1612906
--
You received this bug notification because you are a member of Kernel
** Package changed: cryptsetup (Ubuntu) => zfs-linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802481
Title:
cryptsetup waits for zvol /dev/zvol/rpool/swap with no
6 matches
Mail list logo
