* Andrey Borzenkov <arvidjaar@gmail.com> [02-16-14 00:50]:
В Sat, 15 Feb 2014 17:14:51 -0500 Patrick Shanahan <paka@opensuse.org> пишет: [...] mkdir /etc/systemd/system/emergency.service.d cat << EOF
/etc/systemd/system/emergency.service.d/stop_syslog_socket.conf [Unit] Conflicts=syslog.socket EOF
done
read, tks
Almost pulled my remaining hairs out before realizing that drive was the problem rather than my lvm ssd system drive. The new speedy boot makes err msgs fly by quite quickly.
I can boot with a "live" cd/dvd and the lvm is "Active" and I can mount it w/o any action other than creating a mount point and: mount -t ext4 /dev/mapper/<lvm-name> mount-point
I realize that this undoubtedly deserves a bug report. What should be reported against what and what logs provide relative info?
With above workaround, boot with systemd.log_level=debug on kernel command line, enter emergency shell and provide output of "journalctl -l -b"
As I seem to have a workable cludge and affected system is mail/web server, will reboot and test next available opportunity and provide log results re gpt/lvm disk problem.
kernel-desktop-3.11.10-7.1.x86_64
thanks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org