On Monday 15. December 2014 07.34.07 Jonas Meurer wrote: > Thanks for your feedback. Can you provide me with some further > information?
Yes, I hope so! :-) > Which init system do you use? Is this systemd, sysvinit or something > completely different? I think it is systemd (no conscious decision from my side): kjetil@owl:~$ ls -l /sbin/init lrwxrwxrwx 1 root root 20 Nov 28 06:55 /sbin/init -> /lib/systemd/systemd > Did I get you right, that unlocking the encrypted root fs (sda5_crypt) > works as expected (i.e. you see a prompt asking for passphrase) while at > unlocking the encrypte home fs (owl-home_crypt) no prompt is displayed? Yes, that is correct. > The main difference is, that the root fs is unlocked in initramfs, while > the home fs is unlocked by a initscript. OK! > > In case that you use systemd: I know that systemd introduced some > internal magic to handle encrypted devices at startup and to my > knowledge this is tried before the initscript from my packages are > started. So could you try the following: press return a few times when > the system boot stops waiting for the passphrase of you encrypted home > partition (without prompt) and see, whether it continues afterwards - > optionally showing the expected prompt afterwards? Hmmmm. Not sure about it. After hitting return a couple of times, it scrolls on, and there is another prompt that looks identical. If I continue hitting return, I get to the the maintainance prompt, where I can type the root passwd ot Ctrl+D. Anyway, I don't know if this ends up in a log somewhere? I certainly can't find the phrase passphrase by grepping all logs in /var/log (expect some installer logs). I managed to snap some real screenshots with my mobile phone. Don't know if that could help? Anyway, there's something that I suppose could be related, since /usr is currently mounted just after /home: [ 20.600434] systemd[1]: /usr appears to be on its own filesytem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. [ 20.689337] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. So, my idea was that /usr didn't need to be encrypted, and since it can also be mounted ro, I figured it could be a good idea to make a separate partition for it. But that seems to have been a Bad Idea, perhaps cryptsetup needs something in /usr that isn't there when /home is mounted? > Sorry to bother you with extra debugging work, but unfortunately you > seem to be the only one suffering from this bug so far. No problem! One of the reasons why i run testing is of course to help bring out such issues to help you guys fixing it before it goes stable, so this is something I had expected to deal with. :-) I wish I could do more to help, but alas, ENOTIME. Cheers, Kjetil
