This should be reopened. This is a potentially serious regression that broke on my machine upgrading from 14.10 to 15.04. The way in which it broke left me looking at a shell that told me despite my FS being mounted "rw" according to "mount", all commands were failing because of "Read-only file system".
It is in no way intuitive why it happens, nor the solution that adding an entry to /etc/fstab for the root would fix it, given that that fstab entry was not required in 14.10 and prior. I'm fortunate enough to be experienced enough to find this report and execute follow the steps, many non-power/novice users will not be. This issue could have been avoided altogether by implementing a post- install check that examines the fstab and corrects the issue or at least notifies the user to correct the issue before rebooting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1431743 Title: fails to boot due to read-ony file system Status in systemd package in Ubuntu: Invalid Bug description: I have just recently done a sudo apt-get upgrade, noting something about an included 219 update -- after consequent reboot, the system now hangs at starting 219. No light on Caps Lock. I have since been using upstart. Kernel using - I am on: Linux kubuntu 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Same error when I try the 3.19.0.7-generic kernel. I have updated Grub, no change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
