Comment 8 for bug 522341
Revision history for this message
| Kiri (kiri) wrote Re: crypttab entries not processed automatically at startup despite upstart files | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
I re-installed and took a screen shot of the choice about which initrd to make. (generic or custom) I hope to be able to locate it and upload it in the next few days.
The configuration file is identical. I backed it up and restored it after re-install.
My last attempt to retest this in the advanced install was hindered by grub2 bug(s).
From the description of what devices are available at boot, it sounds unfortunately inadequate for the majority of use cases for potential users:
LABEL and UUID are unavailable since they come from the FileSystem, which is still, encrypted.
The /dev/sd* devices can vary in ordering. What is sdb in one boot can be sdc the next.
So even if this bug is invalid due to being about unsupported by-id devices, it sounds like setting status to 'WishList' for support of by-id devices is ... a wish.
As far as I can recall, this always works with the non-advanced install.
I suppose that if I find out how, I can reconfigure my existing system to use a custom initrd and see whether the problem appears.