[Bug 703947] New: systemd: boot.crypto no longer called / cryptohome not mounted
https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c0 Summary: systemd: boot.crypto no longer called / cryptohome not mounted Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: seife@novell.slipkontur.de QAContact: qa@suse.de CC: fcrozat@novell.com Found By: Third Party Developer/Partner Blocker: --- susi:~ # /etc/init.d/boot.crypto start Failed to issue method call: Unit boot.crypto.service failed to load: No such file or directory. See system logs and 'systemctl status' for details. susi:~ # systemctl start crypto.service Failed to issue method call: Unit crypto.service is masked. (no idea if that would have helped) This leaves me unable to login after boot. The issue is worsened by the fact that there is no way to use the old boot.crypto without editing /etc/rc.status to not call systemctl. Maybe a "--no-systemd" switch which is parsed by rc.status would be helpful? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c1 --- Comment #1 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-07-05 16:50:54 CEST --- susi:~ # cat /etc/crypttab /etc/crypttab susi:~ # cat /etc/crypttab cr_sda7 /dev/disk/by-id/ata-WDC_WD2500BEVS-08VAT2_WD-WX20AC9U2733-part7 none none susi:~ # grep cr_ /etc/fstab /dev/mapper/cr_sda7 /home ext3 noatime,acl,user_xattr,nofail 0 0 susi:~ # chkconfig boot.crypto boot.crypto on -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c Frederic Crozat <fcrozat@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |696902 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c2 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com --- Comment #2 from Andreas Jaeger <aj@novell.com> 2011-07-05 15:08:46 UTC --- boot.crypto is not called at all which is correct AFAIK. Instead systemd has its own crypt handling for mounting. Seife, please check cryptsetup.target, e.g.: systemctl status cryptsetup.target -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c3 --- Comment #3 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-07-05 17:13:28 CEST --- note: this worked until today's update to FACTORY susi:~ # rpm -qa --last|grep systemd systemd-29-4.1 Sat Jul 2 14:19:13 2011 systemd was not touched by this update! so it might be some side effect of another package. I did already play around with systemctl, so this might no longer be totally correct. I'll retry after next boot: susi:~ # systemctl status cryptsetup.target cryptsetup.target - Encrypted Volumes Loaded: loaded (/lib/systemd/system/cryptsetup.target) Active: inactive (dead) since Tue, 05 Jul 2011 16:47:53 +0200; 22min ago susi:~ # systemctl|grep crypt cryptset...r_sda7.service loaded active exited Cryptography Setup for cr_sda7 susi:~ # systemctl status cryptset...r_sda7.service cryptset...r_sda7.service Loaded: error Active: inactive (dead) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c4 --- Comment #4 from Frederic Crozat <fcrozat@novell.com> 2011-07-05 15:19:33 UTC --- check /var/log/messages for error in mount of crypto volume by systemd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c5 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|systemd: boot.crypto no |systemd: cryptsetup |longer called / cryptohome |passphrase prompt times out |not mounted |too quickly Severity|Critical |Normal --- Comment #5 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-07-05 21:03:00 CEST --- Ok, rebooted to test. crypto.service runs, but the passphrase input times out very fast (~5 seconds?), then the X server starts, the boot console gets cleared and you never see that passphrase prompt again. Starting it afterwards is not easy: susi:~ # systemctl status crypto.service crypto.service Loaded: masked (/dev/null) Active: inactive (dead) Warning: Unit file changed on disk, 'systemctl --system daemon-reload' recommended. susi:~ # systemctl start crypto.service Failed to issue method call: Unit crypto.service is masked. susi:~ # systemctl start crypto.service Failed to issue method call: Unit crypto.service is masked. So I finally did systemctl restart cryptsetup.target # not sure if that was necessary systemctl --system daemon-reload systemctl restart crypto.service And finally got my passphrase prompt. Maybe a allowing "/etc/init.d/boot.crypto start" to also work would be helpful for users in panic mode (as I was ;-) And the timeout is too short. I mean - continuing to boot makes absolutely no sense without $HOME mounted, so the "speed" argument is not valid ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c Marcus Meissner <meissner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@novell.com AssignedTo|bnc-team-screening@forge.pr |fcrozat@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c6 Frederic Crozat <fcrozat@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Frederic Crozat <fcrozat@novell.com> 2011-08-12 12:08:44 UTC --- closing as fixed in systemd in Base:System and Factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com