Results 1 to 5 of 5

Thread: NFS mount fails at boot

  1. #1
    Join Date
    Nov 2009
    Beans
    11

    NFS mount fails at boot

    Update: See post 2 for a more proper fix

    I had some problem booting up my appliances after upgrading to 9.10. The home directories were mounted over NFS at boot time and after the upgrade, it wouldn't mount anymore, unless i mounted it manually after boot.

    Message that showed:
    Code:
    init: statd pre-start process (505) terminated with status 1
    ...
    mount.nfs: Either use '-o nolock' to keep locks local, or start statd
    Since i am not at all familiar with Upstart, it took some time to figure this out..
    It seems like a line is missing from the pre-start script in /etc/init/statd.conf

    Before 'status portmap | grep -q start/running || start portmap' add:
    Code:
    exec rpc.statd -L $STATDOPTS
    Then nfs mounts works at boot again.

    Regards
    /Janne
    Last edited by jblomb; November 17th, 2009 at 04:40 PM.

  2. #2
    Join Date
    Nov 2009
    Beans
    11

    Re: NFS mount fails at boot

    Update:

    Someone just posted another fix for this at:

    https://bugs.launchpad.net/ubuntu/+s...ls/+bug/484209

    In essence change the line:

    Code:
    status portmap | grep -q start/running || start portmap
    to

    Code:
    status portmap | grep -q start/ || start portmap

  3. #3
    Join Date
    May 2007
    Beans
    10
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: NFS mount fails at boot

    Janne, thanks for the tip. It helped solve a similar NFS mount failure that originated from a different cause.

    After a recent upgrade to Karmic my desktop began complaining at boot-up that it couldn't mount an NFS share which is used for backups and file sharing. The NFS share is an NAS (Network Attached Storage, i.e. hard drive) that was auto-mounted with an entry in /etc/fstab. There were no network changes or connection problems and the fstab file was intact.

    Your referral to Bug #484209 led me to check my system's version of nfs-utils. Not only did I lack nfs-utils -1:1.2.0-2ubuntu9, there were no NFS packages installed at all. The upgrade, via Update Manager, removed the Jaunty version of NFS but failed to replace it with an updated version.

    A fresh install of nfs-common and associated dependencies was all that was needed to auto-mount the NAS at the next boot.

    The NFS auto-mount works on this machine even with the original, problematic /etc/init/statd.conf file. The patched nfs-utils appears to be included within the nfs-kernel-server package, which is not installed here. Also, unlike your installation, my /home directory resides on the same disk as the operating system.

  4. #4
    Join Date
    Nov 2009
    Location
    Bari, Italy
    Beans
    24
    Distro
    Ubuntu 11.04 Natty Narwhal

    Talking Re: NFS mount fails at boot

    Janne thanks a lot for your posting!!! This was actually the only solution that worked:

    Quote Originally Posted by jblomb View Post

    Before 'status portmap | grep -q start/running || start portmap' add:
    Code:
    exec rpc.statd -L $STATDOPTS
    (It was not working the solution on https://bugs.launchpad.net/ubuntu/+s...ls/+bug/484209 page)

    my statd.conf file actually is: (I'm using Lucid Lynx 10.04 LTS)
    Code:
    [...]
            [ "x$NEED_STATD" != xno ] || { stop; exit 0; }
    
            start portmap || true
            exec rpc.statd -L $STATDOPTS
            status portmap | grep -q start/ || start portmap
            exec sm-notify
    end script
    [...]

  5. #5
    Join Date
    Mar 2008
    Location
    Victoria BC
    Beans
    38
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: NFS mount fails at boot

    keep reading...

    https://bugs.launchpad.net/ubuntu/+s...09/comments/12

    to summarize atti's fix is problematic

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •