It seems systemd cannot mount /tmp, possibly because the kernel does not have CONFIG_TMPFS=y. I think this is required – while tmp.mount (in-memory /tmp) can be masked, but systemd will always try to mount a tmpfs on /run, for daemons' runtime data.
Not sure if that's why it hangs though. Would be nice to check the state from inside – e.g. enable debug-shell.service and check `systemctl list-jobs --full` when it hangs on the next boot... (It runs on tty9; edit the service file if you only have serial console.) Another possible method is to boot a minimal system in either rescue or emergency mode ("single" or "emergency" as kernel parameters) and try starting multi-user.target manually... -- Mantas Mikulėnas <graw...@gmail.com> // sent from phone On Jun 13, 2014 12:19 PM, "Jay D Bhatt" <jay.bh...@igate.com> wrote: > Sorry, Forgot to send log. > > I got the previous log by command use `journalctl --boot -1` > > Please find the log attached. This time the system stopped prior to > previous run. > > This time it stopped at : > > [ OK ] Started D-Bus System Message Bus. > Starting Authorization Manager... > > Thanks, > Jay > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Information contained and transmitted by this e-mail is confidential and > proprietary to IGATE and its affiliates and is intended for use only by the > recipient. If you are not the intended recipient, you are hereby notified > that any dissemination, distribution, copying or use of this e-mail is > strictly prohibited and you are requested to delete this e-mail immediately > and notify the originator or mailad...@igate.com <mailto: > mailad...@igate.com>. IGATE does not enter into any agreement with any > party by e-mail. Any views expressed by an individual do not necessarily > reflect the view of IGATE. IGATE is not responsible for the consequences of > any actions taken on the basis of information provided, through this email. > The contents of an attachment to this e-mail may contain software viruses, > which could damage your own computer system. While IGATE has taken every > reasonable precaution to minimise this risk, we cannot accept liability for > any damage which you sustain as a result of software viruses. You should > carry out your own virus checks before opening an attachment. To know more > about IGATE please visit www.igate.com <http://www.igate.com>. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel