On 27 October 2016 at 15:32, Michael MacIsaac <mike99...@gmail.com> wrote: > I heard about this new cool command and tried it, but it did not work: > > # systemd-analyze time > Bootup is not yet finished. Please try again later. > > How would I analyze systemd to know why 'bootup is not yet finished'? This > is SLES 12 SP1. >
Generic / architecture independent systemd commands to try: $ systemctl list-units --failed Should show some culprits. Also look at full output of $ systemctl list-units and grep/look for things that are activating or waiting. Hopefully this should give you enough hints to figure out what components are not ready yet, to class system as started. Ideally, at the end of the boot you should be able to see that system is in running state: $ systemctl is-system-running running It is for me on machines that I maintain. Loads of things can make systemd believe things are degraded - e.g. when optional services are required or wanted by accident and similar. -- Regards, Dimitri. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
