[Bug 775342] New: rccrypto does not work in systemd mode
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342 https://bugzilla.novell.com/show_bug.cgi?id=775342#c0 Summary: rccrypto does not work in systemd mode Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: carlos.e.r@opensuse.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Freshly installed test system, in a computer with several openSUSE versions installed, including encrypted partitions. The installer sees the partitions, ask for the passwords, open them. But the installed system does not even ask for the password. The appropriate entries exist in fstab and crypttab files. If I attempt to manually activate them, I get: bombadillo:~ # rccrypto status redirecting to systemctl crypto.service Loaded: masked (/dev/null) Active: inactive (dead) bombadillo:~ # rccrypto start redirecting to systemctl Failed to issue method call: Unit crypto.service is masked. After several trials, I use the yast partitioner to acivate the partitions. After that, I get a behaviour change: bombadillo:/lib/systemd/system # rccrypto stop redirecting to systemctl bombadillo:/lib/systemd/system # rccrypto start redirecting to systemctl Job failed. See system logs and 'systemctl status' for details. bombadillo:/lib/systemd/system # The log has many useless details:
Aug 9 22:03:16 bombadillo boot.crypto[17746]: stty: standard input: Inappropriate ioctl for device Aug 9 22:03:16 bombadillo boot.crypto[17746]: Activating crypto devices using /etc/crypttab ... Aug 9 22:03:16 bombadillo boot.crypto[17746]: Unlocking cr_sdc9 (/dev/disk/by-id/ata-ST3500418AS_9VM7ZCQQ-part9) Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** ADDING /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** ADDED /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** EMITTING ADDED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** REMOVING /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** EMITTING REMOVED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** IGNORING REMOVE /sys/devices/virtual/block/dm-0 Aug 9 22:03:17 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:17 bombadillo boot.crypto[17746]: Unlocking cr_sdc9 (/dev/disk/by-id/ata-ST3500418AS_9VM7ZCQQ-part9)
here it waits for a minute...
Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** ADDING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** ADDED /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING ADDED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** REMOVING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING REMOVED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** IGNORING REMOVE /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo boot.crypto[17746]: Unlocking cr_sdc9 (/dev/disk/by-id/ata-ST3500418AS_9VM7ZCQQ-part9) Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** ADDING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** ADDED /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING ADDED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** CHANGED /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** REMOVING /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING REMOVED for /sys/devices/virtual/block/dm-0 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/host5/target5:0:0/5:0:0:0/block/sdc/sdc9 Aug 9 22:03:27 bombadillo dbus-daemon[1119]: **** IGNORING REMOVE /sys/devices/virtual/block/dm-0 Aug 9 22:03:28 bombadillo boot.crypto[17746]: cr_sdc9... ..failed Aug 9 22:03:28 bombadillo boot.crypto[17746]: cr_sdc10..skipped Aug 9 22:03:28 bombadillo systemd[1]: crypto.service: control process exited, code=exited status=1 Aug 9 22:03:28 bombadillo systemd[1]: Unit crypto.service entered failed state.
I tried a reboot. It asked for the password, maybe it failed (it does not say clearly), then it tried to mount the devices, and failed, dumping me into emergency mode. There was an error in fstab, after so many trials. Has to be noauto and nofail mandatory, or if you fail the password you can not boot ever. I had to press the hard reset button to exit and boot again after the edit to fstab in emergency mode, a ctrl-D asked for the encrypted device password again and failed. On the second reboot it asked for the password, continued the boot, but the device was not mounted. In manual mode it does not work. In system V mode it works fine (with other unrelated bug I'll report later). After getting it working with systemV, I tried systemD again - failed. -- 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://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c
kk zhang
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c1
Frederic Crozat
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c2
Carlos Robinson
are you running with 12.1 with all 12.1 maintenance updates installed ?
Yep.
please provide /etc/crypttab,
+++···························· bombadillo:~ # cat /etc/crypttab #cr_sdc9 /dev/disk/by-id/ata-ST3500418AS_9VM7ZCQQ-part9 none noauto cr_sdc9 /dev/disk/by-id/ata-ST3500418AS_9VM7ZCQQ-part9 none none cr_sdc10 /dev/disk/by-id/ata-ST3500418AS_9VM7ZCQQ-part10 none noauto ····························++- Notice that the intention is to activate cr_sdc9 at boot and not cr_sdc10. This works with system V but not with systemd D: it ask for the password of both devices. Do I report that as a different bug?
/etc/fstab,
Beware of line wrap, line width in Bugzilla is exceedingly short. +++···························· bombadillo:~ # cat /etc/fstab LABEL=a_one / reiserfs acl,user_xattr 1 1 LABEL=a_boot_1 /boot ext2 acl,user_xattr 1 2 LABEL=a_swap swap swap pri=-1 0 0 LABEL=b_swap swap swap pri=-1 0 0 LABEL=a_main /other/main ext3 acl,user_xattr 1 2 #/dev/mapper/cr_sdc9 /other/main/data/cripta xfs noauto,nofail 0 0 #/dev/mapper/cr_sdc10 /other/main/data/other xfs noauto,nofail 0 0 /dev/mapper/cr_sdc9 /data/cripta xfs nofail 0 2 /dev/mapper/cr_sdc10 /data/other xfs nofail 0 2 LABEL=a_storage /data/storage_a xfs defaults 1 2 LABEL=b_storage /data/storage_b reiserfs noatime,acl,user_xattr 1 2 LABEL=c_storage /data/storage_c xfs defaults 1 2 LABEL=d_storage /data/storage_d xfs defaults 1 2 LABEL=e_storage /data/storage_e xfs noauto,nofail 1 2 LABEL=a_vmware /data/vmware xfs defaults 1 2 LABEL=b_boot_1 /other/boot_b1 ext2 noauto,acl,user_xattr 0 0 LABEL=b_boot_2 /other/boot_b2 ext2 noauto,acl,user_xattr 0 0 LABEL=b_boot_3 /other/boot_b3 ext2 noauto,acl,user_xattr 0 0 LABEL=c_boot_1 /other/boot_c1 ext2 noauto,acl,user_xattr 0 0 LABEL=c_boot_2 /other/boot_c2 ext2 noauto,acl,user_xattr 0 0 LABEL=c_boot_3 /other/boot_c3 ext2 noauto,acl,user_xattr 0 0 LABEL=a_boot_2 /other/main/boot ext2 acl,user_xattr 1 3 LABEL=c_home /other/main/home xfs defaults 1 3 LABEL=c_home_mail /other/main/home1 reiserfs defaults 1 3 LABEL=b_main_opt /other/main/opt reiserfs acl,user_xattr 1 3 #LABEL=b_main_usr /other/main/usr xfs defaults 1 2 LABEL=b_main_usr /other/main/usr reiserfs acl,user_xattr 1 3 LABEL=c_usr_local /other/main/usr/local reiserfs acl,user_xattr 1 3 LABEL=c_usr_src /other/main/usr/src reiserfs acl,user_xattr 1 3 LABEL=a_test2 /other/test_a2 reiserfs noauto,acl,user_xattr 1 2 LABEL=a_boot_3 /other/test_a2/boot ext2 noauto,acl,user_xattr 1 2 LABEL=a_test3 /other/test_a3 reiserfs noauto,acl,user_xattr 1 2 LABEL=b_test1 /other/test_b1 reiserfs noauto,acl,user_xattr 1 2 LABEL=b_test2 /other/test_b2 reiserfs noauto,acl,user_xattr 1 2 LABEL=c_test1 /other/test_c1 reiserfs noauto,acl,user_xattr 1 2 LABEL=c_test2 /other/test_c2 reiserfs noauto,acl,user_xattr 1 2 LABEL=Erebor /data/Erebor xfs noauto,user,noatime,nodiratime,exec,nofail 1 10 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 ····························++-
/proc/cmdline
+++···························· bombadillo:~ # cat /proc/cmdline root=/dev/disk/by-label/a_one resume=/dev/disk/by-label/b_swap systemd.log_level=debug systemd.log_target=kmsg splash=verbose quiet vga=0x31a ····························++-
and output from dmesg when booting with systemd.log_level=debug systemd.log_target=kmsg
+++···························· bombadillo:~ # rccrypto stop redirecting to systemctl bombadillo:~ # rccrypto start redirecting to systemctl Failed to issue method call: Unit crypto.service is masked. bombadillo:~ # ····························++- No password is requested. Service is not stopped. However, I get a WALL that the system wants the password - for the device that I do not want mounted!: This may be a consequence, perhaps, of not having "noauto" in fstab. I'll try that on next reboot. +++···························· bombadillo:~ # Broadcast message from root@bombadillo (Thu, 16 Aug 2012 11:19:24 +0200): Password entry required for 'Please enter passphrase for disk ST3500418AS (cr_sdc10) on /data/other!' (PID 5374). Please enter password with the systemd-tty-ask-password-agent tool! ····························++- But I don't know where to enter that password. Notice the scenario: I have one partition that I want mounted on boot, and another that I want to mount at MY will. For that I need: - that the system keeps silent, no WALLs. - that the system ask for passwords when I want and dutifully enables the requested partition (rccrypto syntax admits mounting only one requested partition). All this works in system V mode. dmesg output will be attached next. -- 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://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c3
--- Comment #3 from Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c
Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c4
--- Comment #4 from Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c5
--- Comment #5 from Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c6
--- Comment #6 from Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c7
--- Comment #7 from Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c
Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c
Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c8
--- Comment #8 from Frederic Crozat
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c9
--- Comment #9 from Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c10
--- Comment #10 from Carlos Robinson
/etc/init.d/boot.crypto / /etc/init.d/boot.crypto-early / rccrypto are disabled under systemd, there is no point in trying to run them, they are clearly not supported under systemd.
What alternative do you have for that lost functionality? How do you manually activate and mount a partition that was not mounted at boot? Do we have to recreate those scripts from scratch?
for wall, this is a duplicate for bnc#747783 (no fix for now)
It is so nasty as to make System D totally unusable for me.
for noauto, fstab is taking precedence over /etc/crypttab, which is why the prompt was asked.
Ok, understood. I thought as much. -- 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://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c11
--- Comment #11 from Frederic Crozat
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c
Frederic Crozat
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c12
Stefan Fent
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c13
Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c14
Thomas Blume
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c15
Thomas Blume
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c16
Carlos Robinson
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=775342
https://bugzilla.novell.com/show_bug.cgi?id=775342#c17
Thomas Blume
participants (1)
-
bugzilla_noreply@novell.com