Failing to boot because of bind mount in fstab.

After updating my Pogoplug Series 4 and SheevaPlug today both failed at boot and I couldn't ssh to both.
Latest system update for both was 16-Nov.

I didn't had the time to look at the Pogoplug.

A quick peek in the bootlog after connecting with serial to the SheevaPlug showed that the system is failing at bind mount.
The error in the journal is
$this->bbcode_second_pass_quote('', 'F')ailed at step EXEC spawning /bin/plym

[WarheadsSE]

plym or plymouth?

[dhead666]

It's plymouth of course.

$this->bbcode_second_pass_quote('', 'a')rch-sheeva systemd[115]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
-- Subject: Process /bin/plymouth could not be executed
-- Defined-By: systemd

[dhead666]

Full log
http://pastebin.com/J8iMa2Rx

[WarheadsSE]

Well the good news is that is far from just us. Have a google around "nfs mount plymouth"

[dhead666]

Thanks WarheadsSE.

I guess the best solution is to set a high priority so it will be mounted before nfs.

/home/user /srv/nfs4 none bind 0 0