Comment 6 for bug 1157171

The problem of NFS shares not being mounted does still exist.
/var/log/upstart/mountall.log showed the following today:

mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
mountall: mount /video0 [940] terminated with status 32
mountall: mount /mp3 [949] terminated with status 32
mountall: Disconnected from Plymouth

My /etc/fstab looks like this for the two mounts:
192.168.3.42:/mnt/grave/video0 /video0 nfs rsize=32768,wsize=32768,rw,hard,intr,tcp,nfsvers=3,addr=192.168.3.42 0
192.168.3.42:/mp3 /mp3 nfs nfsvers=3,rsize=2048,wsize=2048,tcp

I would also guess, that there is some kind of race condition where nfs filesystems are supposed to mounted before statd and/or network is running.
As long as eth0 got its IP via DHCP there were also lines like this in the log:

mount.nfs: Network is unreachable
mount.nfs: Network is unreachable
mountall: mount /video0 [812] terminated with status 32
mountall: mount /mp3 [815] terminated with status 32

BTW: My machine boots from a 250GB SSD.

When the mounting of the above filesystems fail, it does not start a self added service which should start on the following conditions:

start on (started dbus and started udev and started irserver and mounted MOUNTPOINT=/video0)