cryptdisk start too late at boot process - disks ignored by zfs mount
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi,
I have the following setup:
- System booting from encrypted SSD (luks, btrfs),
- two more hard-disks, both encrypted (luks) and with zfs (that's because the linux version of zfs does not have encrypted, I've therefore put it on two luks-encrypted disks
- encrypted zfs disks have no partition tables, i.e. luks is put directly into sda and sdb.
- luks-key for zfs disks is derived from boot partition using the key-script coming with cryptsetup
Problem:
the system starts these two encrypted disks too late, i.e. through /etc/init/
The problem is, that this runs after /etc/init/
I can easily start the zfs disks by simply running zfs import NAMEOFPOOL manually, but that's not the idea, it should be mounted automatically.
My first guess would be that /etc/init/
start on block-device-added ID_FS_USAGE=crypto
is not triggered.
/sbin/blkid -o udev -p /dev/sda
ID_FS_UUID=
ID_FS_UUID_
ID_FS_VERSION=1
ID_FS_TYPE=
ID_FS_USAGE=crypto
says ID_FS_USAGE is crypto, which seems correct, however, it does not work.
regards
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cryptsetup 2:1.6.1-1ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-45-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Feb 15 19:23:12 2015
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab:
sdc3_crypt UUID=cdb53b1b-
sdc2_crypt UUID=b800eec1-
sda_crypt UUID=af83410f-
sdb_crypt UUID=5824d863-
What is /etc/init/ zpool-import. conf ? This does not appear to be part of Ubuntu.
Without this file, we can't confirm that your analysis of the problem is correct.