[Bug 275451] Re: nfs mounts specified in fstab is not mounted on boot.

[Michael Thompson]

I as well have been plagued by this problem (NFS mounts failing on
bootup) ever since upstart was introduced to Ubuntu.

Not sure why it's so hard to have the network up before things like
mount are called, but apparently it is with Ubuntu.

I have a fixed IP address in /etc/network/interfaces, tried _netdev as a
mount option, forcing the ethernet module to be loaded on boot in
/etc/modules, etc., etc. with no luck.

The only workaround I have found is to use an IP address instead of a
hostname in /etc/fstab.

At least one part of the problem is DNS resolution not working properly
by the time mount is called.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/275451

Title:
  nfs mounts specified in fstab is not mounted on boot.

Status in NULL Project:
  Invalid
Status in “sysvinit” package in Ubuntu:
  New
Status in “nfs-utils” package in Debian:
  Incomplete
Status in “sysvinit” package in Debian:
  New

Bug description:
  
  I have the home directory mounted over NFS by listing it in /etc/fstab. has been working fine up until a few days ago. 

  now after boot I have to first login as root and issue command "mount
  -a" to be able to login as any user since otherwise there will be no
  home directory.