I found out my /etc/fstab has been empty so systemd-remount-fs falsely thought it had nothing to do.
This is still a bug, as Ubuntu crashes at bootup without any further notice. A) systemd-remount-fs MUST NOT sys OK if / and /usr aren't writeable after finishing it's job B) Ubuntu's starting MUST NOT believe in systemd-remount-fs and especially it is NOT allowed to fail silently if something it expects isn't the case One of those has to implement a fallback of simply issuing a "mount -o remount,rw" for /, /usr and /home -- or at least ask the user if it should do so and/or start the recovery menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652761 Title: [16.04 LTS] systemd systemd-remount-fs does NOT remount root writeable but says it did To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1652761/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
