Comment 4 for bug 522341
Revision history for this message
| Steve Langasek (vorlon) wrote Re: crypttab entries not processed automatically at startup despite upstart files | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
What exactly was the option letting you select a custom initrd? This doesn't seem to be a question that comes from the initramfs-tools package.
After reinstall, did you use the same syntax in /etc/crypttab? I think the issue here is that the cryptdisks-udev job handles UUID=, LABEL=, or /dev/sd* as source devices, but is not configured to handle /dev/disk/by-id. So this device will only be brought up if it's caught by the cryptdisks-enable catch-all job, which is racy.