https://bugzilla.novell.com/show_bug.cgi?id=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c1 Andreas Otto changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aotto1968@t-online.de --- Comment #1 from Andreas Otto 2014-04-03 19:48:56 UTC --- (In reply to comment #0)

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.152 Safari/537.36

Hello,

1. I was upgrading from 12.3 to 13.1 using "zypper dup" (the first time) 2. the upgrade went well. 3. I have the boot device on a SSD and 2 additional HD's for mass storage

systemd[1]: Expecting device~ ~dev-disk-by\x2did-ata\x2dSamsung_SSD_840_PRO_Series_S12SNEAD207940W\x2dpart1.device... ~dev-disk-by\x2duuid-b499aac0\x2d0d98\x2d4b35\x2dadef\x2d91711c637e2b.device... ~dev-disk-by\x2duuid-7a8d375e\x2d4be0\x2d4f83\x2d978d\x2d450b6eccfd20.device...

4. the SSD has the root partition -> NO problem 5. the both other have the backup partition based on LVM

...

...

...

PROBLEM-1 <<<

6. the system hangs after every ~second boot waiting for mount of one of the LVM volume's 7. it waits it waits ... and after a while it changes into the emergency mode

...

...

...

PROBLEM-2 <<<

8. BUT i don't get a login-prompt in emergency mode 9. I have to reset the hardware 10. The only solution is to add "noauto" to the both devices (from the end)

====================================================================== # less /etc/fstab /dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S12SNEAD207940W-part1 swap swap defaults 0 0 /dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S12SNEAD207940W-part2 / ext4 acl,user_xattr 1 1 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 UUID=b499aac0-0d98-4b35-adef-91711c637e2b /backup/linux02-1 btrfs noauto,defaults 0 0 UUID=7a8d375e-4be0-4f83-978d-450b6eccfd20 /backup/linux02-2 btrfs noauto,defaults 0 0 /dev/backup-2/windows01 /backup/windows01-2 ext4 noauto,acl,user_xattr 1 2 /dev/backup-1/windows01 /backup/windows01-1 ext4 noauto,acl,user_xattr 1 2 /dev/lxc/lxc_nhi2 /mount/lxc/lxc_nhi2 ext4 noauto,ro,acl,user_xattr 1 2 /dev/lxc/lxc_portal /mount/lxc/lxc_portal ext4 noauto,ro,acl,user_xattr 1 2

=======================================================================

Reproducible: Sometimes

Steps to Reproduce: 1. see details 2. 3. Actual Results: hanging system

Expected Results: booting system

the problem is during setup of "local_fs" this mean I don't have any logfiles to submit

Now I have done additional tests: linux02:~ # systemctl status /backup/linux02-1 backup-linux02\x2d1.mount - /backup/linux02-1 Loaded: loaded (/etc/fstab) Active: failed (Result: exit-code) since Thu 2014-04-03 21:38:48 CEST; 6min ago Where: /backup/linux02-1 What: /dev/backup-1/linux02 Process: 1069 ExecMount=/bin/mount /dev/backup-1/linux02 /backup/linux02-1 -t btrfs -o nofail,defaults,noatime,noexec,acl (code=exited, status=32) Apr 03 21:38:48 linux02 systemd[1]: Mounting /backup/linux02-1... Apr 03 21:38:48 linux02 systemd[1]: backup-linux02\x2d1.mount mount process exited, code=exited status=32 Apr 03 21:38:48 linux02 systemd[1]: Failed to mount /backup/linux02-1. Apr 03 21:38:48 linux02 systemd[1]: Unit backup-linux02\x2d1.mount entered failed state. =============================================================== linux02:~ # systemctl status /backup/linux02-2 backup-linux02\x2d2.mount - /backup/linux02-2 Loaded: loaded (/etc/fstab) Active: failed (Result: exit-code) since Thu 2014-04-03 21:38:48 CEST; 9min ago Where: /backup/linux02-2 What: /dev/backup-2/linux02 Process: 1060 ExecMount=/bin/mount /dev/backup-2/linux02 /backup/linux02-2 -t btrfs -o nofail,defaults,noatime,noexec,acl (code=exited, status=32) Apr 03 21:38:48 linux02 systemd[1]: backup-linux02\x2d2.mount mount process exited, code=exited status=32 Apr 03 21:38:48 linux02 systemd[1]: Failed to mount /backup/linux02-2. Apr 03 21:38:48 linux02 systemd[1]: Unit backup-linux02\x2d2.mount entered failed state. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c6 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com --- Comment #6 from Thomas Blume 2014-04-04 09:47:16 UTC --- This is most probably a duplicate of bug 862076. Until the update is published, please used the workaround noted in comment #0 of this bug. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c7 --- Comment #7 from Thomas Blume 2014-04-04 09:50:07 UTC --- Sorry, I've overlooked that the update was already released. Can you check that your system is at the latest patchlevel? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c9 --- Comment #9 from Thomas Blume 2014-04-04 11:09:07 UTC --- -> BUT: still no answer why I don't get a root login if NON-ROOT local mount fails? This is because without nofail the mount unit has a dependencies to local.fs.target. If the dependency fails, local.fs.target will also fail stopping the further boot process. You can find details in: man 5 systemd.mount -->-- If nofail is given, this mount will be only wanted, not required, by the local-fs.target. This means that the boot will continue even if this mount point is not mounted successfully. Option fail has the opposite meaning and is the default. --<-- -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c11 --- Comment #11 from Andreas Otto 2014-04-04 11:22:24 UTC --- my value: # If lvmetad has been running while use_lvmetad was 0, it MUST be stopped # before changing use_lvmetad to 1 and started again afterwards. use_lvmetad = 1 i read the lvm bug as well: # systemctl is-enabled lvm2-lvmetad.socket disabled -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c13 --- Comment #13 from Andreas Otto 2014-04-04 11:43:54 UTC --- I send you my journalctl from a failed boot: interesting "lvm" error BEFOR the mount fail... Apr 04 13:26:22 linux02 systemd[1]: Started Hostname Service. Apr 04 13:26:23 linux02 hp-systray[4582]: hp-systray[4582]: error: option -s not recognized Apr 04 13:26:24 linux02 systemd-udevd[734]: timeout: killing '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 16' [843] Apr 04 13:26:24 linux02 systemd-udevd[734]: '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 16' [843] terminated by signal 9 (Killed) Apr 04 13:26:24 linux02 systemd-udevd[737]: timeout: killing '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 32' [832] Apr 04 13:26:24 linux02 systemd-udevd[737]: '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 32' [832] terminated by signal 9 (Killed) Apr 04 13:26:24 linux02 systemd-udevd[740]: timeout: killing '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 4' [898] Apr 04 13:26:24 linux02 systemd-udevd[740]: '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 4' [898] terminated by signal 9 (Killed) Apr 04 13:26:24 linux02 systemd-udevd[738]: timeout: killing '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 3' [899] Apr 04 13:26:24 linux02 systemd-udevd[738]: '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 3' [899] terminated by signal 9 (Killed) -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c15 --- Comment #15 from Andreas Otto 2014-04-04 11:47:55 UTC --- next funny stuff: start the SUSE partition tool to see whats going on ... it hangs start my service linux02:~ # rclxc-watchdog status Checking for service lxc-watchdog... it hangs ... seems to be that the systemd blocking at all ... I have to reboot .-( -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c17 --- Comment #17 from Andreas Otto 2014-04-04 11:59:15 UTC --- linux02:~ # systemctl status | grep lvm2-lvmetad.socket └─6551 grep --color=auto lvm2-lvmetad.socket -> nothing and... linux02:~ # systemctl status | grep lvm2 └─6566 grep --color=auto lvm2 lvm2-lvmetad.service -> '/org/freedesktop/systemd1/unit/lvm2_2dlvmetad_2eservice' lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.service; disabled) CGroup: /system.slice/lvm2-lvmetad.service I have done now: linux02:~ # systemctl enable lvm2-lvmetad.service ln -s '/usr/lib/systemd/system/lvm2-lvmetad.service' '/etc/systemd/system/sysinit.target.wants/lvm2-lvmetad.service' linux02:~ # ls -al /etc/systemd/system/sysinit.target.wants/lvm2-lvmetad.service lrwxrwxrwx 1 root root 44 Apr 4 13:55 /etc/systemd/system/sysinit.target.wants/lvm2-lvmetad.service -> /usr/lib/systemd/system/lvm2-lvmetad.service linux02:~ # ls -al /etc/systemd/system/sysinit.target.wants/ total 8 drwxr-xr-x 2 root root 4096 Apr 4 13:55 . drwxr-xr-x 13 root root 4096 Apr 4 13:55 .. lrwxrwxrwx 1 root root 44 Apr 4 13:55 lvm2-lvmetad.service -> /usr/lib/systemd/system/lvm2-lvmetad.service linux02:~ # => is this ok? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c19 --- Comment #19 from Thomas Blume 2014-04-04 12:20:07 UTC --- Normally only lvm2-lvmetad.socket needs to be enabled. When the socket is present, it will enable the service at socket access. You might want to run mkinitrd to sync your changes into the initrd. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c21 --- Comment #21 from Andrey Borzenkov 2014-04-04 13:42:31 UTC --- (In reply to comment #13)

Apr 04 13:26:24 linux02 systemd-udevd[734]: timeout: killing '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 16' [843] [...] skipped

That explains why LVs are not started. Could you add "--debug" to invocation of pvscan in /usr/lib/udev/rules.d/69-dm-lvm-metad.rules and attach journalctl output next time you get a problem? Also check BIOS settings - if you have floppy controller, try to completely deactivate it. (In reply to comment #17)

linux02:~ # systemctl status | grep lvm2-lvmetad.socket └─6551 grep --color=auto lvm2-lvmetad.socket

Wrong. Please read manual page for systemctl. It is either systemctl (without any options) or "systemctl status lvm2-lvmetad.socket". -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c23 --- Comment #23 from Andreas Otto 2014-04-06 20:30:15 UTC --- Created an attachment (id=585255) --> (http://bugzilla.novell.com/attachment.cgi?id=585255) the new journalctl with bug AND --debug option seems the same stuff a last event: Apr 06 20:10:20 linux02 rtkit-daemon[4471]: Successfully made thread 4528 of process 4528 (/usr/bin/pulseaudio) owned by 'dev1usr' high priority at nice level -11. Apr 06 20:10:20 linux02 rtkit-daemon[4471]: Supervising 5 threads of 2 processes of 1 users. Apr 06 20:10:20 linux02 pulseaudio[4528]: [pulseaudio] pid.c: Daemon already running. Apr 06 20:10:20 linux02 polkitd[1081]: Registered Authentication Agent for unix-session:1 (system bus name :1.31 [/usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/Authe nticationAgent, locale de_DE.UTF-8) Apr 06 20:10:21 linux02 systemd-udevd[747]: timeout: killing '/sbin/lvm pvscan --debug --cache --activate ay --major 8 --minor 32' [880] Apr 06 20:10:21 linux02 systemd-udevd[747]: '/sbin/lvm pvscan --debug --cache --activate ay --major 8 --minor 32' [880] terminated by signal 9 (Killed) Apr 06 20:10:21 linux02 systemd-udevd[744]: timeout: killing '/sbin/lvm pvscan --debug --cache --activate ay --major 8 --minor 16' [887] Apr 06 20:10:21 linux02 systemd-udevd[744]: '/sbin/lvm pvscan --debug --cache --activate ay --major 8 --minor 16' [887] terminated by signal 9 (Killed) Apr 06 20:10:21 linux02 systemd-udevd[740]: timeout: killing '/sbin/lvm pvscan --debug --cache --activate ay --major 8 --minor 3' [905] Apr 06 20:10:21 linux02 systemd-udevd[740]: '/sbin/lvm pvscan --debug --cache --activate ay --major 8 --minor 3' [905] terminated by signal 9 (Killed) Apr 06 20:10:21 linux02 systemd-udevd[743]: timeout: killing '/sbin/lvm pvscan --debug --cache --activate ay --major 8 --minor 4' [904] Apr 06 20:10:21 linux02 systemd-udevd[743]: '/sbin/lvm pvscan --debug --cache --activate ay --major 8 --minor 4' [904] terminated by signal 9 (Killed) Apr 06 20:10:24 linux02 systemd-readahead[668]: open(/home/dev1usr/.kde4/socket-linux02/klauncherMT4237.slave-socket) failed: No such device or address Apr 06 20:10:26 linux02 nfsserver[3798]: Starting kernel based NFS server:exportfs: Failed to resolve HP-HP but the modification is there # Only process devices already marked as a PV - this requires blkid to be called before. ENV{ID_FS_TYPE}=="LVM2_member|LVM1_member", RUN+="/sbin/lvm pvscan --debug --cache --activate ay --major $major --minor $minor" -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c25 --- Comment #25 from Andreas Otto 2014-04-07 05:50:46 UTC --- done. I did some additional reserach: 1) linux02:~ # /sbin/lvm pvscan --debug --cache --activate ay --major 8 --minor 32 ^C -> hanhing. 2) linux02:~ # /sbin/lvm pvscan -dddddd --cache --activate ay --major 8 --minor 32 ^C -> hanging 3) strace /sbin/lvm pvscan -dddddd --cache --activate ay --major 8 --minor 32 1>/tmp/strace.txt 2>&1 -> see attachment => the debug itself does bring anything ... the process stopps bevor anything interesting happen -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c27 --- Comment #27 from Andrey Borzenkov 2014-04-07 09:04:40 UTC --- (In reply to comment #25)

=> the debug itself does bring anything ... the process stopps bevor anything interesting happen

debug output goes to syslog. According to strace, there should be quite a lot of it. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c29 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |aotto1968@t-online.de --- Comment #29 from Thomas Blume 2014-04-07 13:12:11 UTC --- Did you also see that the lvm commands (for example pvscan) hang in the running system? I could see the issue once with the above symptoms. The reason was that lvmetad was hung. Killing the pid of lvmetad and then restarting it solved the problem for me. Unfortunately, I couldn't reproduce it after the lvmetad restart. So, if you see the hanging lvm commands, we would also need a n strace of lvmetad. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c31 --- Comment #31 from Thomas Blume 2014-04-07 14:13:45 UTC --- If you add the option: "nofail" to all your non-systemroot mounts in /etc/fstab, the machine should come up and you should be able to log in as root. Afterwards, please try wheter a pvscan, vgscan, lvscan works. If not, please check the PID of lvmetad and attach an strace via: strace -f -t -p $PID > strace.out where pid is the process id of lvmetad. Let it running for a few minutes and then attach strace.out. Afterwards, please kill the lvmetad pid: kill $PID and restart it via: systemctl restart lvm2-lvmetad.service then please check via: systemctl status lvm2-lvmetad.service wheter it is running. If it is, retry the above lvm commands. Do they work then? IMHO, you don't need to keep the -ddddd to pvscan if it doesn't give an output. Andrey, any objections? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c33 --- Comment #33 from Andrey Borzenkov 2014-04-07 17:14:54 UTC --- @Andreas: please test updated package: zypper ar obs://home:arvidjaar:bnc:871704/standard bnc871704 zypper refresh bnc871704 zypper dup -r bnc871704 Try to reproduce the problem. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c35 --- Comment #35 from Michael Bednowicz 2014-04-08 04:35:29 UTC --- I had this problem too. The updated packages seem to have fixed it. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c37 --- Comment #37 from Andrey Borzenkov 2014-04-08 05:41:23 UTC --- (In reply to comment #36)

some mount show up as ... "/dev/mapper..." other as "/dev/dm..."

That does not matter. They all are aliases for the same device. I do not know whether this is systemd, mount or df who resolves them, but would ignore it at this point. Some more reboots to verify would be good :) -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c39 --- Comment #39 from Andreas Otto 2014-04-10 20:20:52 UTC --- so, last boot crashed terrible... KDE start but I don't even get a "konsole" I add some logs. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c41 --- Comment #41 from Andreas Otto 2014-04-10 20:24:00 UTC --- Created an attachment (id=585916) --> (http://bugzilla.novell.com/attachment.cgi?id=585916) df -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c43 --- Comment #43 from Andreas Otto 2014-04-10 20:30:00 UTC --- Created an attachment (id=585918) --> (http://bugzilla.novell.com/attachment.cgi?id=585918) mount -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c45 --- Comment #45 from Thomas Blume 2014-04-11 07:45:19 UTC --- Seems your lvm devices are inactive. What does: systemctl status lvm2-lvmetad.service and lvscan -v tell? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c47 --- Comment #47 from Andreas Otto 2014-04-16 05:48:28 UTC --- Also, ich glaube das Problem hängt mit meinen lxc's zusammen !! + lvscan -v WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. connect() failed on local socket: No such file or directory Internal cluster locking initialisation failed. WARNING: Falling back to local file-based locking. Volume Groups with the clustered attribute will be inaccessible. Finding all logical volumes ACTIVE '/dev/backup-2/linux02' [400.00 GiB] inherit ACTIVE '/dev/backup-2/windows01' [400.00 GiB] inherit ACTIVE '/dev/backup-1/linux02' [400.00 GiB] inherit ACTIVE '/dev/backup-1/windows01' [400.00 GiB] inherit ACTIVE '/dev/backup-1/nhi2' [200.00 GiB] inherit ACTIVE '/dev/backup-1/portal' [200.00 GiB] inherit ACTIVE '/dev/lxc/lxc_nhi2' [20.00 GiB] inherit ACTIVE '/dev/lxc/lxc_portal' [20.00 GiB] inherit systemctl status lvm2-lvmetad.service + systemctl status lvm2-lvmetad.service Failed to get D-Bus connection: No connection to service manager. + systemctl start lvm2-lvmetad.service Failed to get D-Bus connection: No connection to service manager. + sudo ps aux + grep dbus message+ 1110 0.0 0.0 32824 1820 ? Ss 07:17 0:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation usbmux 4813 0.0 0.0 32560 1652 ? Ss 07:17 0:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation dev1usr 5540 0.0 0.0 22416 836 ? S 07:17 0:00 dbus-launch --sh-syntax --exit-with-session --close-stderr dev1usr 5541 0.0 0.0 33636 2124 ? Ss 07:17 0:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session dev1usr 5617 0.0 0.0 32560 1580 ? S 07:17 0:00 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3 root 7486 0.0 0.0 9268 924 tty1 S+ 07:38 0:00 grep dbus + netstat antp + grep dbus unix 3 [ ] STREAM CONNECTED 181763 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 34577 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 16578 /run/dbus/system_bus_socket unix 3 [ ] STREAM CONNECTED 16579 /run/dbus/system_bus_socket unix 3 [ ] STREAM CONNECTED 36371 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 180324 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 26296 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 37574 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32515 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 36935 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32531 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 31623 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 37577 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 176970 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 37575 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 31499 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 19007 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 45716 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 36937 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32509 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 26339 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 170236 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 44531 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 40034 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 177260 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 34582 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 26376 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 26313 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 26311 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32545 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 45824 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 186940 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 37579 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 30954 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 30953 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 40113 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32512 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 16580 /run/dbus/system_bus_socket unix 3 [ ] STREAM CONNECTED 32532 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 187947 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 40108 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32530 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 180318 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 189649 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 34371 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 26326 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32501 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 29904 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 8087 /run/dbus/system_bus_socket unix 3 [ ] STREAM CONNECTED 49762 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 176969 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 170235 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 34457 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 30979 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 52915 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32511 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32502 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 16577 /run/dbus/system_bus_socket unix 3 [ ] STREAM CONNECTED 26352 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 28863 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 16584 /run/dbus/system_bus_socket unix 3 [ ] STREAM CONNECTED 44510 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 26303 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 177242 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 18973 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 31018 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 38232 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32549 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 32513 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 18985 @/tmp/dbus-1PbEIF4Ud6 unix 3 [ ] STREAM CONNECTED 177379 @/tmp/dbus-rhGJ95Rr unix 3 [ ] STREAM CONNECTED 44503 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 37582 @/tmp/dbus-TPbj2PtpgH unix 3 [ ] STREAM CONNECTED 40102 @/tmp/dbus-TPbj2PtpgH + df -k df: ‘/usr/lib64/lxc/rootfs/root’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/dev’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/sys/fs/cgroup’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/usr/lib64/lxc/rootfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/usr/lib64/lxc/rootfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/usr/lib64/lxc/rootfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/dev’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/sys/fs/cgroup’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/usr/lib64/lxc/rootfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/usr/lib64/lxc/rootfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/usr/lib64/lxc/rootfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/dev’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/sys/fs/cgroup’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/usr/lib64/lxc/rootfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/usr/lib64/lxc/rootfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/usr/lib64/lxc/rootfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/home/dev1usr/.gvfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/home/dev1usr/.gvfs’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/home/dev1usr/.gvfs’: No such file or directory Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda2 103080224 69926788 27894224 72% / devtmpfs 16340556 1108 16339448 1% /dev tmpfs 16358804 40 16358764 1% /sys/fs/cgroup none 103080224 69926788 27894224 72% /usr/lib64/lxc/rootfs none 103080224 69926788 27894224 72% /usr/lib64/lxc/rootfs none 103080224 69926788 27894224 72% /usr/lib64/lxc/rootfs /var/log/boot Trying manual resume from /dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S12SNEAD207940W-part1 Invoking userspace resume from /dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S12SNEAD207940W-part1 resume: libgcrypt version: 1.5.3 Trying manual resume from /dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S12SNEAD207940W-part1 Invoking in-kernel resume from /dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S12SNEAD207940W-part1 Waiting for device /dev/root to appear: ok fsck from util-linux 2.23.2 [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/sda2 /dev/sda2: clean, 949041/6553600 files, 17883863/26214144 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/root mount -o rw,discard,defaults,noatime,acl,user_xattr -t ext4 /dev/root /root Welcome to openSUSE 13.1 (Bottle) (x86_64)! Starting Replay Read-Ahead Data... Starting Collect Read-Ahead Data... [ OK ] Listening on Syslog Socket. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Listening on LVM2 metadata daemon socket. [ OK ] Set up automount Arbitrary Executable File Formats File System Automount Point. [ OK ] Reached target Encrypted Volumes. [ OK ] Listening on udev Kernel Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on Journal Socket. Starting LSB: Set default boot entry if called... Mounting POSIX Message Queue File System... Mounting Huge Pages File System... Starting Create dynamic rule for /dev/root link... Starting Create list of required static device nodes for the current kernel... Starting Journal Service... [ OK ] Started Journal Service. Expecting device dev-disk-by\x2did-ata\x2dSamsung_SSD_840_PRO_Series_S12SNEAD207940W\x2dpart1.device... Expecting device dev-backup\x2d1-linux02.device... Expecting device dev-backup\x2d1-nhi2.device... Expecting device dev-backup\x2d1-portal.device... Expecting device dev-backup\x2d1-windows01.device... Expecting device dev-backup\x2d2-linux02.device... Expecting device dev-backup\x2d2-windows01.device... [ OK ] Created slice Root Slice. [ OK ] Created slice User and Session Slice. [ OK ] Created slice System Slice. [ OK ] Created slice system-getty.slice. [ OK ] Reached target Slices. [ OK ] Started Collect Read-Ahead Data. [ OK ] Started Replay Read-Ahead Data. [ OK ] Started LSB: Set default boot entry if called. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Huge Pages File System. [ OK ] Started Create dynamic rule for /dev/root link. Starting Load Kernel Modules... Starting Setup Virtual Console... Starting Remount Root and Kernel File Systems... %G[ OK ] Started Create list of required static device nodes for the current kernel. [ OK ] Started Load Kernel Modules. (K Starting Apply Kernel Variables... Starting Create static device nodes in /dev... [ OK ] Started Apply Kernel Variables. [ OK ] Started Remount Root and Kernel File Systems. Starting Load/Save Random Seed... [ OK ] Started Create static device nodes in /dev. [ OK ] Started Load/Save Random Seed. Starting udev Kernel Device Manager... [ OK ] Reached target Local File Systems (Pre). Mounting Lock Directory... Mounting /sys/kernel/debug... Mounting Runtime Directory... [ OK ] Mounted Lock Directory. [ OK ] Mounted /sys/kernel/debug. [ OK ] Started udev Kernel Device Manager. [ OK ] Started Setup Virtual Console. [ OK ] Mounted Runtime Directory. [ OK ] Reached target Local File Systems. Starting Trigger Flushing of Journal to Persistent Storage... Starting Recreate Volatile Files and Directories... Starting Tell Plymouth To Write Out Runtime Data... Starting udev Coldplug all Devices... [ OK ] Started Trigger Flushing of Journal to Persistent Storage. [ OK ] Started Recreate Volatile Files and Directories. Starting LSB: AppArmor initialization... Starting Update UTMP about System Reboot/Shutdown... [ OK ] Started Update UTMP about System Reboot/Shutdown. [ OK ] Started Tell Plymouth To Write Out Runtime Data. [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot Screen... Starting LVM2 metadata daemon... [ OK ] Started LVM2 metadata daemon. [ OK ] Reached target Sound Card. [ OK ] Found device Samsung_SSD_840_PRO_Series. Activating swap /dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S12SNEAD207940W-part1... [ OK ] Activated swap /dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S12SNEAD207940W-part1. [ OK ] Reached target Swap. [ OK ] Started LSB: AppArmor initialization. [ OK ] Reached target System Initialization. [ OK ] Listening on CUPS Printing Service Sockets. [ OK ] Listening on RPCbind Server Activation Socket. [ OK ] Reached target RPC Port Mapper. [ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket. [ OK ] Listening on PC/SC Smart Card Daemon Activation Socket. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Timers. Starting Restore Sound Card State... [ OK ] Started Restore Sound Card State. [ OK ] Found device /dev/backup-1/windows01. Starting File System Check on /dev/backup-1/windows01... systemd-fsck[1040]: /dev/mapper/backup--1-windows01: clean, 11/26214400 files, 1696024/104857600 blocks [ OK ] Started File System Check on /dev/backup-1/windows01. Mounting /backup/windows01-1... [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Paths. [ OK ] Reached target Basic System. Starting LSB: VirtualBox Linux module... Starting D-Bus System Message Bus... [ OK ] Started D-Bus System Message Bus. Starting Avahi mDNS/DNS-SD Stack... Starting WPA Supplicant daemon... Starting Modem Manager... Starting Network Manager Script Dispatcher Service... Starting System Logging Service... Starting Name Service Cache Daemon... [ OK ] Started Name Service Cache Daemon. Starting Haveged Entropy Gathering Daemon... [ OK ] Started Haveged Entropy Gathering Daemon. Starting SuSEfirewall2 phase 1... Starting RPC Bind... Starting Login Service... Starting Permit User Sessions... [ OK ] Started Permit User Sessions. [ OK ] Started Avahi mDNS/DNS-SD Stack. [ OK ] Started WPA Supplicant daemon. [ OK ] Started Network Manager Script Dispatcher Service. [ OK ] Started Login Service. Starting Authorization Manager... [ OK ] Started System Logging Service. [ OK ] Started Authorization Manager. [ OK ] Started Modem Manager. [ OK ] Started RPC Bind. [ OK ] Found device /dev/backup-2/windows01. Starting File System Check on /dev/backup-2/windows01... [ OK ] Started SuSEfirewall2 phase 1. Starting LSB: Configure network interfaces and set up routing... [ OK ] Found device /dev/backup-2/linux02. Mounting /backup/linux02-2... [ OK ] Found device /dev/backup-1/portal. Mounting /backup/portal-1... [ OK ] Mounted /backup/linux02-2. systemd-fsck[1186]: /dev/mapper/backup--2-windows01: clean, 11/26214400 files, 1696024/104857600 blocks [ OK ] Mounted /backup/windows01-1. [ OK ] Started File System Check on /dev/backup-2/windows01. Mounting /backup/windows01-2... [ OK ] Mounted /backup/windows01-2. [ OK ] Found device /dev/backup-1/linux02. Mounting /backup/linux02-1... [ OK ] Started LSB: VirtualBox Linux module. [ OK ] Created slice system-network.slice. Expecting device sys-subsystem-net-devices-br0.device... Starting ifup managed network interface br0... [ OK ] Found device /sys/subsystem/net/devices/br0. [ OK ] Mounted /backup/portal-1. [ OK ] Found device /dev/backup-1/nhi2. Mounting /backup/nhi2-1... [ OK ] Mounted /backup/nhi2-1. [ OK ] Mounted /backup/linux02-1. [ OK ] Started ifup managed network interface br0. [ OK ] Started LSB: Configure network interfaces and set up routing. [ OK ] Reached target Network. Starting LSB: Start the lxc-watchdog deamon... Starting Samba SMB Daemon... Starting OpenSSH Daemon... [ OK ] Reached target Host and Network Name Lookups. Starting LSB: Network time protocol daemon (ntpd)... Starting LSB: Start the kernel based NFS daemon... Starting /etc/init.d/boot.local Compatibility... [ OK ] Started /etc/init.d/boot.local Compatibility. Starting Getty on tty1... [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. Starting /etc/init.d/after.local Compatibility... [ OK ] Started /etc/init.d/after.local Compatibility. [ OK ] Started OpenSSH Daemon. [ OK ] Started Samba SMB Daemon. [ OK ] Started LSB: Network time protocol daemon (ntpd). [ OK ] Reached target System Time Synchronized. Starting Postfix Mail Transport Agent... Starting LSB: X Display Manager... Starting CUPS Printing Service... [ OK ] Started CUPS Printing Service. [ OK ] Started LSB: X Display Manager. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c49 --- Comment #49 from Thomas Blume 2014-04-16 07:24:58 UTC --- Seems to be an issue with the cgroups: df: ‘/usr/lib64/lxc/rootfs/root/sys/fs/cgroup’: No such file or directory According to the manpage, systemd needs this: -->-- Processes systemd spawns are placed in individual Linux control groups named after the unit which they belong to in the private systemd hierarchy. (see cgroups.txt[1] for more information about control groups, or short "cgroups"). systemd uses this to effectively keep track of processes. Control group information is maintained in the kernel, and is accessible via the file system hierarchy (beneath /sys/fs/cgroup/systemd/), or in tools such as ps(1) (ps xawf -eo pid,user,cgroup,args is particularly useful to list all processes and the systemd units they belong to.). --<-- Can you check wheter: /sys/fs/cgroup/systemd/system.slice/lvm2-lvmetad.service is accessible from within the linux container? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c51 Andreas Otto changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|aotto1968@t-online.de | --- Comment #51 from Andreas Otto 2014-04-17 06:22:10 UTC --- Hi, this is the "original" system - my one and yes the lxc was always on this system and if @Thomas say that the "cgroup" is damaged than the lxc where just victim of the problem ... on normal operation the lxc stuff worked quite well... I come to the lxc suggestion only with the hint of "df" command showing lxc shares. + df -k df: ‘/usr/lib64/lxc/rootfs/root’: No such file or directory df: ‘/usr/lib64/lxc/rootfs/root/dev’: No such file or directory .. => a NORMAL output of "df" is. linux02:~ # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda2 103080224 69949712 27871300 72% / devtmpfs 16340556 152 16340404 1% /dev tmpfs 16358804 1180 16357624 1% /dev/shm tmpfs 16358804 15704 16343100 1% /run tmpfs 16358804 0 16358804 0% /sys/fs/cgroup tmpfs 16358804 15704 16343100 1% /var/run tmpfs 16358804 15704 16343100 1% /var/lock /dev/mapper/backup--2-linux02 419430400 312 417304320 1% /backup/linux02-2 /dev/mapper/backup--2-windows01 412718256 71952 391658400 1% /backup/windows01-2 /dev/mapper/backup--1-portal 209715200 9828208 197928568 5% /backup/portal-1 /dev/mapper/backup--1-windows01 412718256 71952 391658400 1% /backup/windows01-1 /dev/mapper/backup--1-nhi2 209715200 775784 207084040 1% /backup/nhi2-1 /dev/mapper/backup--1-linux02 419430400 56513108 360846500 14% /backup/linux02-1 => Attention be aware that NOW the /dev/mapper/... devices are shown. => In earlier attempts it has shown: ... /dev/dm-* /dev/mapper/backup--1-windows01 412718256 71952 391658400 1% /backup/windows01-1 /dev/dm-6 419430400 312 417304320 1% /backup/linux02-2 /dev/mapper/backup--2-windows01 412718256 71952 391658400 1% /backup/windows01-2 /dev/dm-2 209715200 775392 207084296 1% /backup/nhi2-1 /dev/dm-3 209715200 9624856 198067168 5% /backup/portal-1 /dev/dm-0 419430400 48503684 369306340 12% /backup/linux02-1 -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c53 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |aotto1968@t-online.de --- Comment #53 from Thomas Blume 2014-04-17 09:03:25 UTC --- Ok, I was probably distraced by the fact that you are using lxc.

+ halt Failed to open /dev/initctl: No such device or address Failed to talk to init daemon.

what is the output of: systemctl status systemd-initctl.socket ? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c55 --- Comment #55 from Andreas Otto 2014-04-18 17:16:55 UTC --- today the mounts are missing ... the old bug is back ... this seems the problem systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Fri 2014-04-18 18:02:27 CEST; 58min ago Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 720 (systemd-udevd) CGroup: /system.slice/systemd-udevd.service └─720 /usr/lib/systemd/systemd-udevd Apr 18 18:02:27 linux02 systemd-udevd[720]: invalid rule '/etc/udev/rules.d/99-lexmarklegacy-util.rules:11' Apr 18 18:02:27 linux02 mtp-probe[791]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1" Apr 18 18:02:27 linux02 mtp-probe[791]: bus: 1, device: 3 was not an MTP device Apr 18 18:02:27 linux02 mtp-probe[989]: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.1" Apr 18 18:02:28 linux02 mtp-probe[1111]: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2" Apr 18 18:02:28 linux02 mtp-probe[1583]: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.4" Apr 18 18:02:58 linux02 systemd-udevd[756]: timeout: killing '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 16' [841] Apr 18 18:02:58 linux02 systemd-udevd[756]: '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 16' [841] terminated by signal 9 (Killed) Apr 18 18:02:58 linux02 systemd-udevd[751]: timeout: killing '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 32' [840] Apr 18 18:02:58 linux02 systemd-udevd[751]: '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 32' [840] terminated by signal 9 (Killed) systemd-update-utmp.service -> '/org/freedesktop/systemd1/unit/systemd_2dupdate_2dutmp_2eservice' the old "--debug" flag was missing... add "--debug" to /usr/lib/udev/rules.d/69-dm-lvm-metad.rules # rpm -qf /sbin/lvmetad lvm2-2.02.98-0.28.17.2.x86_64 -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c57 --- Comment #57 from Andrey Borzenkov 2014-04-19 05:35:49 UTC --- I can reproduce it now (not with exact symptoms) in QEMU VM: openSUSE 32 bit, minimal install on a single physical disk (non LVM!), all current patches, added three more drives after initial installation and created PV on them. During reboot I get: Apr 19 09:27:24 linux-qqqf LVM: Logical Volume autoactivation enabled. Apr 19 09:27:24 linux-qqqf LVM: Activation generator successfully completed. Apr 19 09:27:24 linux-qqqf systemd[1]: Starting LVM2 metadata daemon socket. Apr 19 09:27:24 linux-qqqf systemd[1]: Listening on LVM2 metadata daemon socket. Apr 19 09:27:29 linux-qqqf systemd[1]: Starting LVM2 metadata daemon... Apr 19 09:27:29 linux-qqqf systemd[1]: Started LVM2 metadata daemon. Apr 19 09:27:29 linux-qqqf systemd-udevd[247]: '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 33' [870] terminated by signal 6 (Aborted) Apr 19 09:27:29 linux-qqqf systemd-udevd[249]: '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 17' [874] terminated by signal 6 (Aborted) Apr 19 09:27:29 linux-qqqf systemd-udevd[248]: '/sbin/lvm pvscan --cache --activate ay --major 8 --minor 49' [871] terminated by signal 6 (Aborted) And no device is present. Running "pvs" after reboot apparently triggers rescan from lvmetad and devices appear. So yes, there it definitely an issue with multiple PVs. This may be hidden if root itself is on LVM so initrd does initial scan and configures them; but pure lvmetad fails far too easily. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c Andrey Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #585298|application/octet-stream |text/plain mime type| | -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c60 Joachim Banzhaf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joachim.banzhaf@googlemail. | |com --- Comment #60 from Joachim Banzhaf 2014-05-26 13:23:43 UTC --- I have the same problems on 2 fully updated 13.1 systems: Some of the bigger volumes very often fail to mount and I don't get an emergency shell to fix or investigate. I understand the nofail workaround, but is there a fix on its way? Nofail is wrong, because I do not want the systems to boot to normal mode when these mounts fail. But of course I still want an emergency shell. Test your packages means executing the 3 zypper commands from comment #33 right? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c62 --- Comment #62 from Joachim Banzhaf 2014-05-26 22:08:21 UTC --- I did this: $ sudo zypper ar http://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/ factory-systemd $ sudo LANG=C zypper up systemd gives this response: There is an update candidate for 'systemd', but it is from a different vendor. Use 'zypper install systemd-210-685.4.x86_64' to install this candidate. ok then, I tried this: $ sudo LANG=C zypper install systemd-210-685.4.x86_64 but now getting this Problem: nothing provides libgcrypt.so.20()(64bit) needed by systemd-210-685.4.x86_64 Solution 1: do not install systemd-210-685.4.x86_64 Solution 2: break systemd-210-685.4.x86_64 by ignoring some of its dependencies Could have tried to find the right libgcrypt, but cowardly bailed out here. Options? And what would be my returnpath to the standard systemd (other than restoring from a backup)? Just removing the factory repo and install systemd again? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c64 --- Comment #64 from Dr. Werner Fink 2014-05-27 06:41:04 UTC --- Args .. cut&paste error as I meant http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/ mumble ... herein I've tried to hold the systemd-210 usable for openSUSE 13.1 -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c66 --- Comment #66 from Joachim Banzhaf 2014-05-27 09:59:04 UTC --- Emergency prompt works now, too. Thanks. If I find the time, I'll try providing a backtrace for the lvmetad deadlock -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c68 --- Comment #68 from Thomas Blume 2014-05-28 09:16:46 UTC --- We really should go for a final fix for this issue. Therefore, we'd need the backtrace as noted in comment #59 Who ever can provide it would help much to find the root cause, so that we can provide the fix. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c70 --- Comment #70 from Joachim Banzhaf 2014-05-28 20:28:01 UTC --- Tested comment #33. Hangs again. Basically the same backtrace: Thread 1 (Thread 0x7f8d90b86800 (LWP 1009)): #0 0x00007f8d8fe7e8f3 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:81 #1 0x0000000000406332 in daemon_start (s=...) at daemon-server.c:516 #2 0x0000000000403112 in main (argc=1, argv=0x7fffdfd91888) at lvmetad-core.c:1202 -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c72 --- Comment #72 from Joachim Banzhaf 2014-07-02 07:43:46 UTC --- I'm afraid I could use some tips from the test repo experts here. With the above repo changes (for lvm and systemd) my system often did not shutdown. So I removed the repos and did another zypper dup. Unfortunately the system now only boots in a basic shell (after millions of "/dev/mapper/conrol not found" messages). Reinstall needed? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c74 --- Comment #74 from Joachim Banzhaf 2014-07-06 23:08:24 UTC --- Thanks, but that did not help (or I did it wrong). Opened a forum thread for this because it is no longer directly bug related: https://forums.opensuse.org/showthread.php/499418-opensuse-13-1-boots-into-i... Any help appreciated. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c76 --- Comment #76 from Joachim Banzhaf 2014-07-07 12:41:50 UTC --- (In reply to comment #75)

Are you sure that the initrd matches the kernel you are booting?

Yes, pretty sure. I trust the opensuse installation does the right thing there. As I wrote in the forum, I installed another opensuse 13.1 instance, even with current network updates. I used the same /boot (/dev/sda1, ext3, 500 MB, not formatting) and a new lv for root in the same vg as the original system. This method has worked on earlier occations on other servers (but not tried before with v13.1). /boot/grub2/grub.conf menuentry kernel and initrd are both 3.11.10-17-desktop They have the timestamp from the install.

Before you build a new initrd, please double check that /boot is mounted. Otherwise you will boot the new kernel with an old initrd. This will cause a load failure of most modules due to kernel version mismatch.

I do not know how to run mkinitrd on that defect system myself. I tried from the 13.1 dvd rescue system, but it says "getopts: usage: getopts optstring name [arg]" no matter what parameters I call it with. I did run mkinitrd for integrating new boot filesystem modules before on other systems. But only from the "native", more or less healthy os.

If this doesn't help, could you attach a serial console log from the boot? In addition, please attach the initrd you were using.

Difficult. I have an usb to serial adapter but nowhere to attach it to. But I'll try to get the initrd off of the server. -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c78 --- Comment #78 from Joachim Banzhaf 2014-07-07 14:20:14 UTC --- Connected the usb2serial converters to 2 working servers to experiment. Both started minicom -D /dev/ttyUSBx -b 9600 -8 I also tried minicom -D /dev/ttyUSBx -b 9600 -8 -o Doesn't matter. Both say they use 9600,8n1 and if I type "abc" into one side, it displays as "O'N" on the other side. So, the connection works, only the parameters are wrong. But how? -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c80 --- Comment #80 from Joachim Banzhaf 2014-07-07 17:30:59 UTC --- The link only describes how to make lvm work in a rescue system. That already works with 13.1. I finally made some progress: Found out how to activate network and ssh. Made a backup of the /boot partition and reinstalled the mini 13.1 system again. This time with format of /boot. Now I can boot into the new mini system! One thing still missing: grub2 auto detection finds all old systems, but creates the entries wrong (with the new kernel, root fs and initrd). I assume this is because it cannot find the correct kernels and other support files in /boot now that I formatted it. I'll see if I can copy the needed files back, without sending me back to square one. Should work, so case closed for now. Thanks for your support, much appreciated! -- 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=871704 https://bugzilla.novell.com/show_bug.cgi?id=871704#c82 --- Comment #82 from Thomas Blume 2014-07-08 13:16:29 UTC --- Hm, I'm a bit confused. Your older systems should have their own initrds that load the appropriate file system modules and mount the system root device accordingly. Seems the root= parameter doesn't match the original settings in your older systems. I would suggest that you disable the grub OS prober by setting: GRUB_DISABLE_OS_PROBER=true in /etc/default/grub and use /etc/grub.d/40_custom to generate custom entries for your older systems. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=871704 --- Comment #109 from Liuhua Wang --- (In reply to Andrei Borzenkov from comment #107)

(In reply to Liuhua Wang from comment #105)

...

Can we close this and open a new bug duplicated to bsc#905690?

You are not authorized to access bug #905690.

Sorry, I just realized that you cannot access the L3 bugs from customers, which is for respect the privacy of our customers, sorry for the inconvenience. Would you please open a new bug for your issues? -- You are receiving this mail because: You are on the CC list for the bug.