NFS mounts don't mount on boot

Status changed to 'Confirmed' because the bug affects multiple users.

This bug was fixed in the package rpcbind - 0.2.0-8.2ubuntu1

---------------
rpcbind (0.2.0-8.2ubuntu1) saucy; urgency=low

  * Merge from Debian unstable (LP: #1217610); remaining changes:
    - Migrate /etc/init/portmap.conf to /etc/init/rpcbind.conf
  * All other Ubuntu changes have now been merged upstream.
 -- Steve Langasek <email address hidden> Sat, 31 Aug 2013 12:59:57 -0700

Thanks,

This is fixed on my Asus 1000HE.

This has stopped working again.

I'm not able to reproduce this problem here. There was a known issue, but it's been fixed and the rpcbind package hasn't had any relevant changes since. You might want to trace back the updates to your system to identify which package reintroduced the problem for you.

It's something with mountall. It was upgraded from 2.49 to 2.50 and 2.51 before the last reboot. I reverted to 2.50 and the problem still occured. I reverted to 2.49 and the NFS mounts come up on boot. I'll take a look at what changed in the mountall package between 2.49 and 2.50.

Hmm, so if I revert this change to the init script:
     . /etc/default/rcS || true
     [ -f /forcefsck ] && force_fsck="--force-fsck"
     [ "$FSCKFIX" = "yes" ] && fsck_fix="--fsck-fix"

+ # Doesn't work so well if mountall is responsible for mounting /proc, heh.
+ if [ -e /proc/cmdline ]; then
+ for arg in $(cat /proc/cmdline); do
+ case $arg in
+ -q|--quiet|-v|--verbose|--debug)
+ debug_arg=$arg
+ ;;
+ esac
+ done
+ fi
     # set $LANG so that messages appearing in plymouth are translated
     if [ -r /etc/default/locale ]; then
         . /etc/default/locale || true
         export LANG LANGUAGE LC_MESSAGES LC_ALL
     fi

- exec mountall --daemon $force_fsck $fsck_fix
+ exec mountall --daemon $force_fsck $fsck_fix $debug_arg
 end script

it works. It seems strange that this would stop NFS from mounting on boot.

On Tue, Sep 17, 2013 at 02:47:47AM -0000, Joseph Yasi wrote:

> + # Doesn't work so well if mountall is responsible for mounting /proc, heh.
> + if [ -e /proc/cmdline ]; then
> + for arg in $(cat /proc/cmdline); do
> + case $arg in
> + -q|--quiet|-v|--verbose|--debug)
> + debug_arg=$arg
> + ;;
> + esac
> + done
> + fi
> # set $LANG so that messages appearing in plymouth are translated
> if [ -r /etc/default/locale ]; then
> . /etc/default/locale || true
> export LANG LANGUAGE LC_MESSAGES LC_ALL
> fi

> - exec mountall --daemon $force_fsck $fsck_fix
> + exec mountall --daemon $force_fsck $fsck_fix $debug_arg
> end script

> it works. It seems strange that this would stop NFS from mounting on
> boot.

Yes, that is strange. I see two possible explanations for this:

 - the script is causing mountall to fail to start; in that case, more
   mounts than just nfs mounts would fail to mount.
 - you are passing one of these options on the kernel commandline (--quiet,
   --verbose, --debug), and this is causing a timing change in mountall
   which is affecting the boot-time behavior.

What's /proc/cmdline on this system in the case where the nfs mounts fail?

/proc/cmdline is:
BOOT_IMAGE=/boot/vmlinuz-3.11.1-customatom root=UUID=708b3ba8-c42a-4adf-a195-c0fb8d8f8dd3 ro

So, none of those options are passed to the kernel. Mountall is starting, and everything but the NFS mounts are mounting fine. When NFS fails to mount without those lines, mountall is still running after boot and frozen. When I remove those lines, everything mounts and mountall finishes so it is no longer running after boot. It is very strange.

On Tue, Sep 17, 2013 at 03:52:57AM -0000, Joseph Yasi wrote:
> /proc/cmdline is:
> BOOT_IMAGE=/boot/vmlinuz-3.11.1-customatom root=UUID=708b3ba8-c42a-4adf-a195-c0fb8d8f8dd3 ro

> So, none of those options are passed to the kernel. Mountall is
> starting, and everything but the NFS mounts are mounting fine. When NFS
> fails to mount without those lines, mountall is still running after boot
> and frozen. When I remove those lines, everything mounts and mountall
> finishes so it is no longer running after boot. It is very strange.

Ok. If you *do* boot with --verbose on the kernel commandline, do you get a
/var/log/upstart/mountall.log file? Can you attach the contents?

Also, would you mind filing a separate bug report on the mountall package
for this regression?

Filed as: #1226766

Just wanted to say this bug seems to still be in existence. I just did a fresh install of ubuntu 12.04.3 and I am receiving the same "mountall: Disconnected from Plymouth" error when I have a nfs share mounted in fstab. Once I login I am able to manually mount the share without issue.

When I remove the nfs entry from fstab the error does not occur on bootup.

Jake, please file a separate bug report for your issue. *This* bug was never present in 12.04.

> I am receiving the same "mountall: Disconnected from Plymouth" error

That is not diagnostic of the problem; all this means is that mountall was still running at the point that plymouth exited, which happens if mountall is waiting for remote filesystems that are not required for boot. It tells us nothing about the root cause of why the nfs filesystems aren't mounted.