As far as I know, the mounting is handled by systemd. To avoid other errors and problems, systemd aborts the booting process when a partition is missing.
In my opinion, this is not a bug, but the expected behaviour. ** Package changed: ubuntu => systemd (Ubuntu) -- 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/1601932 Title: Xenial start problems with change UUID in fstab Status in systemd package in Ubuntu: New Bug description: Xenial started correct. Now an UUID changes because a partition was reformatted. The new UUID is independent of Xenial. Xenial aborts the start, since the new UUID is not registered in fstab. Ubuntu 12.04, 14.04, 14.10 and 15.04 and 15.10 have no problems with the changed UUID. Many years ago there was this error. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1601932/+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
