>From the log:
[...]
usr1_handler: Received SIGUSR1 (network device up)
[...]
queue_fsck: /mnt/music: no check required
mounting /mnt/music
spawn: mount -a -t nfs -o rsize=8192,wsize=8192,noexec,nosuid
192.168.0.2:/mnt/music /mnt/music
spawn: mount /mnt/music [1320]
[...]
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mountall: mount /mnt/music [1320] terminated with status 32
mountall: Filesystem could not be mounted: /mnt/music
What version of nfs-common did you have installed when generating this
log? This should have been fixed in nfs-common 1:1.2.0-2ubuntu5:
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.
If these error messages are showing up in your latest mountall log, and
you're running nfs-common 1:1.2.0-2ubuntu5 or later, then we still have
a bug even if your shares all get mounted in the end.
(It's also a bug that the error messages are visible on console, but
that's not a bug in nfs-utils; other packages are supposed to take care
of hiding those for us during a normal boot.)
--
mount of nfs fails at boot - Karmic beta
https://bugs.launchpad.net/bugs/445181
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
