https://bugzilla.novell.com/show_bug.cgi?id=804575 https://bugzilla.novell.com/show_bug.cgi?id=804575#c0 Summary: systemd problem with rbind (and crypto setup?) Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: koenig@linux.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- trying to setup dual-boot and chroot for both 12.2 and 12.3-RC1 on my notebook I slipped over a strange systemd problem: the following line in my /etc/fstab /dev /12.2/dev none rbind caused systemd to stop booting with this failure # systemctl | grep fail systemd-cryptsetup@cr_ata\x2dHGST_HTS541010A9E680_J810007600B1RA\x2dpart5.service loaded failed failed Cryptography Setup for cr_ata-HGST_HTS541010A9E680_J810007600B1RA-part5 # systemctl status systemd-cryptsetup@cr_ata\x2dHGST_HTS541010A9E680_J810007600B1RA\x2dpart5.service systemd-cryptsetup@cr_ata\x2dHGST_HTS541010A9E680_J810007600B1RA\x2dpart5.service - Cryptography Setup for cr_ata-HGST_HTS541010A9E680_J810007600B1RA-part5 Loaded: loaded (/etc/crypttab) Active: failed (Result: exit-code) since Tue, 2013-02-19 08:42:31 CET; 6min ago Docs: man:systemd-cryptsetup@.service(8) man:crypttab(5) Process: 965 ExecStop=/usr/lib/systemd/systemd-cryptsetup detach cr_ata-HGST_HTS541010A9E680_J810007600B1RA-part5 (code=exited, status=1/FAILURE) Process: 856 ExecStart=/usr/lib/systemd/systemd-cryptsetup attach cr_ata-HGST_HTS541010A9E680_J810007600B1RA-part5 /dev/disk/by-id/ata-HGST_HTS541010A9E680_J810007600B1RA-part5 none none (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/systemd-cryptsetup@.service/cr_ata\x2dHGST_HTS541010A9E680_J810007600B1RA\x2dpart5 Feb 19 08:41:10 hl.turtle.de systemd[1]: Started Cryptography Setup for cr_ata-HGST_HTS541010A9E680_J810007600B1RA-part5. Feb 19 08:42:31 hl.turtle.de systemd[1]: Stopped Cryptography Setup for cr_ata-HGST_HTS541010A9E680_J810007600B1RA-part5. Feb 19 08:42:31 hl.turtle.de systemd[1]: Unit systemd-cryptsetup@cr_ata\x2dHGST_HTS541010A9E680_J810007600B1RA\x2dpart5.service entered failed state although the cryptsetup stuff worked fine as I could check in the "emergency" shell. this happened both in my 12.2 system and in the 12.3-RC1 !! after removing/changing that rbind line for /dev startup with systemd worked again! running mount --rbind /dev /12.2/dev worked without a problem. more details to my (somewhat non-standard;) setup: basis is a plain 12.2 installation with encrypted LVM in sda5 containing everything but the boot partition: # fdisk -l /dev/sda Device Boot Start End Blocks Id System /dev/sda3 * 312578048 314697727 1059840 83 Linux /dev/sda4 314697728 1953523711 819412992 f W95 Ext'd (LBA) /dev/sda5 314699776 1363275775 524288000 8e Linux LVM there are LVMs root-12.2 and root-12.3 (later was a copy of root-12.2 which I then updated to 12.3-RC1). /boot is used for both distro roots together. in such "dual boot" systems I typically mount the "other" root partiton into /12.2 or /12.3 with proc sys dev etc. in place to be able to chroot into the old/new system for tests. for the 12.3 system I tried to setup the 12.2 chroot in fstab with /dev/system/root-12.2 /12.2 ext4 acl,user_xattr 1 1 /boot /12.2/boot none rbind /proc /12.2/proc none rbind /sys /12.2/sys none rbind /dev /12.2/dev none rbind thouse rbinds work fine on the command line, and at least they worked before in fstab without systemd. but now the last line for /dev caused that strange boot trouble:-( now I'm using this slightly more complex fstab entries to avoid rbind and similar trouble: /dev/system/root-12.2 /12.2 ext4 acl,user_xattr 1 1 /boot /12.2/boot none rbind proc /12.2/proc proc defaults 0 0 sysfs /12.2/sys sysfs noauto 0 0 debugfs /12.2/sys/kernel/debug debugfs noauto 0 0 usbfs /12.2/proc/bus/usb usbfs noauto 0 0 /dev /12.2/dev none bind devpts /12.2/dev/pts devpts mode=0620,gid=5 0 0 any clue what happens in systemd for my rbind /dev/ entry ? how can I provide more debug data ? -- 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.