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

user1685095
  • 372
  • 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 '15 at 06:20
  • @JdeBP what logs do you need? – user1685095 Jun 25 '15 at 07: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 '15 at 08: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? – user1685095 Jun 25 '15 at 08:22
  • Boot with systemd and view the journal since that boot. – JdeBP Jun 25 '15 at 17:40
  • @JdeBP I've updated my question – user1685095 Jun 27 '15 at 09:21
  • If it were me, I'd be looking at the systemd services that remount the root volume, to start with. Then I'd be looking for missing orderings relative to local-fs.target. But only you can do that until you show people what the logs say. – JdeBP Jun 27 '15 at 13:11
  • @JdeBP I've added the output of journalctl. Look at the last to photos, it's grep root volume and local-fs.target. Don't see any errors there. – user1685095 Jul 05 '15 at 20:38
  • Look at this link >> http://askubuntu.com/questions/640639/ubuntu-boots-to-read-only-filesystem-after-upgrading, I have the same problem after upgrading to 16.04 and currently trying to solve with given link above. – sugab Apr 25 '16 at 02:17

0 Answers0