Comment 2 for bug 504776

In my case the error message in consistent (bug #504224) , and also have no similarities with escapes to the recovery shell etc. The (bug 470776), where mountall forgot a previous network ready state, and for mountall in Lucid this is fixed. Unfortunately, this can not be applied or be tested in Karmic. In (bug #431248) everything hangs during boot, but some similarities exists. One comment was that the problem is not related to mountall, but to portmap or nfs-common.

I changed my fstab stanza to 'shire.gigahome.net:/home/bekr/nfs /home/bekr/nfs nfs defaults 0 0'

Consistently I see similar results as above:
mount.nfs : rpc.statd not running. etc...
It was also suggested (bug #413248) that network-manager may be involved, and since I use static addresses on my LAN (many servers) I removed network-manager, but the error messages are the still the same. The comment #8, in this (bug #413248) report is very similar to what I see. Then patches for nfs-utils and portmap package are discussed.

I also edited /etc/default/nfs-common and enabled:
# Do you want to start the statd daemon?
NEED_STATD=yes

This did not change the overall behavior. Interestingly though, I can still mount the share manually once the boot process finished.

Here is the installed versions in Karmic:
dpkg -l mountall nfs-utils nfs-common portmap
ii mountall 1.0 filesystem mounting tool
ii nfs-common 1:1.2.0-2ubuntu8 NFS support files common to client and server
ii portmap 6.0-10ubuntu2 RPC port mapper
No packages found matching nfs-utils.

apt-cache show nfs-utils
W: Unable to locate package nfs-utils
E: No packages found

I'm puzzled about this nfs-utils package though.

System is using latest updates.
Linux odin 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux