I agree with ironstorm. This bug clearly needs to be reopened. I just upgraded my server and it became read only. I can confirm that the problem for me was that after upgrade the fstab had the wrong UUID in it. Bizarrely, it was changed from:
UUID=18254707-08e8-494e-b456-938592928a5e / ext4 errors=remount-ro 0 1 to: UUID=815063a9-c956-44a6-ab11-05e1d0bb3a58 / ext4 errors=remount-ro 0 1 The server was virtual and luckily I took a backup before upgrading. I therefore restored the backup, upgraded again and then dropped into the command prompt and corrected the fstab before rebooting the server. As Ironstorm suggests, this should be a post install check or perhaps the bug which is causing this issue can be resolved. I'm sure that this issue will affect lots of other people and it should be reopened as an issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431743 Title: fails to boot due to read-ony file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
