Comment 21 for bug 431248

Hi Jonas,

No, your issue is probably not related to bug #447654. I believe your problem is fixed with the latest upload of nfs-utils, which arranges for statd to be started (if not already running) whenever we are asked to mount an NFS filesystem.

 nfs-utils (1:1.2.0-2ubuntu5) karmic; urgency=low
 .
   * Set upstart jobs to also start on mount attempt, in the event that
     mountall gets to them before the daemons are done starting. Really-fixes
     LP: #431248.
   * Call 'stop' in the pre-start scripts for all jobs when we want to prevent
     the job from starting; this lets upstart know that it's a clean stop,
     and avoids boot-time messages about service start failures

In your case, since you're netbooting it's entirely possible that it's not a timing issue at all - depending on how your filesystems and network devices are set up, the signal might never have arrived that would retry the mount on your system after statd was started. With the above change, though, I think it should work reliably for you.