Don't doubt that... but NFS is not mounted and the problem is real.. Here the /var/log/boot.log
fsck from util-linux-ng 2.17.2 fsck from util-linux-ng 2.17.2 /dev/sda1: clean, 235/124496 files, 65983/248832 blocks /dev/mapper/git-root: clean, 57793/474208 files, 334796/1895424 blocks mount.nfs: Failed to resolve server 192.168.88.252: Name or service not known mountall: mount /mnt/repos [560] terminated with status 32 * Starting AppArmor profiles ESC[80G ^MESC[74G[ OK ] 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 /mnt/repos [690] terminated with status 32 Apparently id doesn't resolve 192.168.88.252 (?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933575 Title: NFS not being mounted at boot time - rpc.statd is not running but is required for remote locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/933575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
