hello forum,
I’m new to linux and ran directly in a strange behaviour for a VM on ESX 5.5 vmx-10.
The installed sles12sp1 is partitioned as follows and I can shutdown or “coldboot” the system, but on “init 6” or “reboot” in x11 the system is going to a black screen - than nothing (I was waiting for 20 minutes).
the partion|mountpoint layout was choosen for easier future disk extention
the choice of the file systems is completely by pure chance.
my questions:
where can I find any helpful log - on the screen I’m not getting any message.
What can be the reason for this issue?
False combination of partitioning / file system?
Thank You,
Stefan
[SIZE=2]PS: sorry for any language errors - I’m native German speaker[/SIZE]
hello ab,
the last messages before forced shutdown down:
2017-01-22T16:59:42.048186+01:00 vslidm3 polkitd[1235]: Operator of unix-session:1 successfully authenticated as unix-user:root to gain TEMPORARY authorization for action org.freedesktop.login1.reboot for system-bus-name::1.30 [/usr/bin/gnome-session --session sle-classic] (owned by unix-user:specuser)
2017-01-22T16:59:42.055886+01:00 vslidm3 org.gnome.Nautilus.SearchProvider[6632]: (nautilus:6816): GLib-GObject-WARNING **: gsignal.c:2593: instance '0x18e88e0' has no handler with id '233'
2017-01-22T16:59:42.101044+01:00 vslidm3 ca.desrt.dconf[6632]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
2017-01-22T16:59:42.120339+01:00 vslidm3 rsyslogd: [origin software="rsyslogd" swVersion="8.4.0" x-pid="1084" x-info="http://www.rsyslog.com"] exiting on signal 15.
I’ve tried other partition/filesystem layouts - the error ist always reproducable, so I believe I’m running perhaps in a VMware special issue related to the graphic emulation?!
The answers to your other questions:
the system is freshly installed, SP1 x64, other SLES 12 SP1+2 are up and running.
switching to “init 1” also crashes the system. strange …
switching to “init 3” and then rebooting works fine.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
the system is actually unpatched - it will be registered and updated by an inernal smt server.
the layout is on customer demand (ldap/idm collegues)
the system specification seems fully esx compatible.
the drivers are “out of the box” from the sles install media and and open vm tools are installed.
I really appreciate your interest and suggestions. I will continue my investigations next week due to more important work this week.
rsyslogd: [origin software=“rsyslogd” swVersion=“8.4.0” x-pid=“1084” x-info=“http://www.rsyslog.com”] exiting on signal 15.
that last line from syslog seems to indicate that the shutdown was actually initiated (and further messages are no longer logged, since syslog went down).
Are you able to connect via text console (via VMware console)? Then I’d advise to both run "journalctl -f & " (to receive any journal messages produced by systemd during shutdown processing, even after rsyslogd exited) and to initiate the shutdown from tty0, to visually catch any message that might additionally appear from old-style scripts.
