[Solved]Controlling systemd's 'emergency-behaviour'

Question

So after boot-cycling some systems only to return to the 'emergency-console' because something went wrong during boot, I'm wondering if there is any way to control 'when' exactly the system(d) decides it can no longer continue booting.
More specifically, I know why the boot fails, its because of a certain mount line in /etc/fstab.
Sometimes the filesystem just isn't available, in my case because the kernel-module needed hasn't been rebuilt after a kernel upgrade, but its easy to image other scenarios like networked filesystems and such.
So I'm wondering how to stop systemd from dropping into 'emergency-room-mode' just because of a failed mount line in /etc/fstb, and more generally if/where/how more fine grained control is possible.
Any ideas?
Last edited by hungerfish (2014-08-17 13:32:05)

Answer 1

...but for my purposes I'd rather the boot process be as permissive as possible.
Exactly my point, it could be more permissive in case such as non-essential fs not being available.*
The 'nofail' option apparently does just that (tell the system that a fs is not essential). This fixes my 'problem'.
And it gets to chose when to stick to the rules and when to ignore some, and it gets to chose which ones to ignore.
The whole point of me asking was to find out how to to instruct the system towards behaving in a appropriate fashion. The 'nofail' option tells the system to 'ignore some stuff', in this case a filesystem, I don't get your angle.
What's the problem, again?
*While using 'nofail' works fine, the 'problem/nag' that remains is that this could be the default for non-essential mountpoints thus eliminating the need for adding the option manually. But I guess there's a ton of reasons for it not being so, or maybe not...