1

The problem is occurring when loading ubuntu with systemd. If I'm manually starting with upstart (from boot menu) then everything works fine.

I've checked the disk with badsector and I have no badsectors in disk. The disk is pretty new also, so I don't think that that's a problem with disk.

I've tried to look at the output of journalctl command and I don't see anything wierd. Seems that all hardware is working properly. But then when systemd starts to launching programs if they want lock they couldn't get it because of read-only file system. Aside from that I can't say anything.

I can post like 10 photos with outputs of journalctl if it will help

That's the output of journalctl -b

9
  • So edit your question and tell people what the logs say. The world is not clairvoyant, nor can people access your computer to read the logs themselves.
    – JdeBP
    Jun 25, 2015 at 6:20
  • @JdeBP what logs do you need? Jun 25, 2015 at 7:33
  • If it were my system, I'd be reading the output of journalctl -b -x to start with, which would lead me on to other stuff. But don't use the -x option for stuff that you pass to other people for diagnosis.
    – JdeBP
    Jun 25, 2015 at 8:15
  • @JdeBP No journal files were found. Should I do it when booting with systemd and read only file system or I can do that with upstart when everything is working fine? Jun 25, 2015 at 8:22
  • Boot with systemd and view the journal since that boot.
    – JdeBP
    Jun 25, 2015 at 17:40

0

You must log in to answer this question.

Browse other questions tagged .