I’ve updated the Kernel via Tumbleweed. Since the last two Kernel Versions 3.9.1 and 3.9.2 the booting fails with my Cryptodevice settings:
Installed Kernels:
/boot/vmlinuz-3.9.0-6-desktop: Linux/x86 Kernel, Setup Version 0x20c, bzImage, Version 3.9.0, Version 3.9.0-6, RO-rootFS, swap_dev 0x4, Normal VGA
works fine
/boot/vmlinuz-3.9.1-7.gb6484b6-desktop: Linux/x86 Kernel, Setup Version 0x20c, bzImage, Version 3.9.1, RO-rootFS, swap_dev 0x4, Normal VGA
hangs at
systemd[1]: Breaking ordering cycle by deleting job systemd-cryptsetup@cr_temp.crypt.service/start
as endless loop.
/boot/vmlinuz-3.9.2-8.g04040b9-desktop: Linux/x86 Kernel, Setup Version 0x20c, bzImage, Version 3.9.2, RO-rootFS, swap_dev 0x4, Normal VGA
the same as Kernel 3.9.1
cat /etc/fstab
/dev/disk/by-id/ata-xxx-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-yyy-part1 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-xxx-part3 /tmp ext4 defaults 1 1
/dev/disk/by-id/ata-xxx-part2 /mnt/boot ext4 defaults 1 2
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
/dev/mapper/cr_temp.crypt /home/usr/temp ext4 loop,noauto,acl,user_xattr,nofail 0 2
192.168.1.1:/home /home nfs4 defaults 0 0
192.168.1.1:/sik /mnt/sik nfs4 defaults 0 0
#....
cat /etc/crypttab
#cr_temp.crypt /mnt/sik/temp/temp.crypt none timeout=0 #original entry but same result as next line
cr_temp.crypt /mnt/sik/temp/temp.crypt none nofail,timeout=0
With this entries (both) the new Kernels have the effect. (I uses “nofail” instead of “noauto” like described in the “man” pages.
cat /etc/crypttab
cr_temp.crypt /mnt/sik/temp/temp.crypt none noauto,timeout=0
This is working but I can’t mount the crypto device. I found in the net, that I should start the service “systemctl start secret.mount” or “systemctl restart secret.mount”
Normally I mount after booting via “systemd-tty-ask-password-agent” command, the crypto file system, if it is working.
Have anyone an idea, what can be my mistake or is this relay a bug?
Ulf