This is not normal systemd behaviour, it waits for the resource, but only 1min 30s by default and then continues booting, (unless the services are considered critical for reaching certain target), logging a failed service, someone must have therefore explicitly configured a custom behaviour in your situation.
> The implementation is retarded.
May be, or may be whoever configured the server this way is, who knows?
> I have enough of that kind of deranged thinking to deal with coming from Windows
As I said above, this is not standard systemd behaviour.
I am not saying that systemd is perfect, but your case seems like misconfiguration, rather than "deranged thinking" from the systemd devs.
I'l encarouge you to read more on its configuration, it's actually fairly flexible, this[1] is a solid starting point.
(this was originally meant as a reply to above comment was mistakenly posted to grandparent.)
1 - https://www.freedesktop.org/software/systemd/man/systemd.ser...
2 - http://stackoverflow.com/questions/33776937/how-to-change-th...
The implementation is retarded. Last week my providers' iSCSI fabric suffered a glitch, which hosed a whole bunch of servers for hours because systemd refused to boot when it found the volumes not present. These were in no way critical to the operation of the stack. However, some moron somewhere decided that locking the system for 5 minutes on boot, and then simply refusing to boot properly, when everything required to boot is actually in place and OK is the correct course of action. I have enough of that kind of deranged thinking to deal with coming from Windows, I don't need it from my Linux machines.
Systemd sucks for servers. It might do a lot of nice fancy tech stuff, but it is extremely poorly thought out for use on the server.