Seems you already figured out the broken fstab yourself. Indeed
upstart/mountall didn't complain about this, and you silently wouldn't
have a swap partition. systemd is more explicit about this, and in
rescue mode or if you boot without "splash", or wait long enough you'd
see the error. This is a behaviour which we want to keep, we don't just
want to sweep such errors under the carpet.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
** Summary changed:
- System doesn't boot with systemd, upstart mode is ok
+ does not boot with broken UUIDs in fstab
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1448865
Title:
does not boot with broken UUIDs in fstab
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448865/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
