Bug 302

Description of problem:
If /etc/fstab contains an entry which failed to mount during boot (even if it is not critical for work), the boot process stops and system enters emergency mode, which contains absolutely no indication as to what the source of the problem was, and therefore the diagnosis becomes a very difficult process containing mostly of googling.

Users expect that the system boots even if some of their permanently configured mount points are inaccessible (e.g., CD is ejected, or a network resource became unavailable), so that they could reconfigure the faulty items. And at the very least, there should be some information as to what caused the problem. Maybe, there is, but it must be hidden somewhere very deep, because I searched through various log files and failed to find anything of use...


Version-Release number of selected component (if applicable):
systemd-39.3


Steps to Reproduce:
1. Edit /etc/fstab by adding at the end something like:
/dev/cdrom /mnt auto defaults 0 0
2. Eject the CD/DVD disk (if you had one inserted) and reboot the system.
3. Instead of login screen, a "Welcome to emergency mode" message appears, and until the fstab entry becomes mountable (or commented/removed), it is impossible to boot the system normally.