[Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot

Tjd 1384502 at bugs.launchpad.net
Fri May 6 19:01:53 UTC 2016

Workaround: add the 'bootwait' option to the /home fstab entry.

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.

  fstab entry for nfs /home fails to mount on boot

Status in mountall package in Ubuntu:

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic
  Uname: Linux 3.13.0-38.65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list