Messages in this thread | | | Subject | Re: 2.1.60 NFS probs... | From | Ketil Z Malde <> | Date | 28 Oct 1997 15:52:21 +0100 |
| |
Matthew Kirkwood <matthew.kirkwood@lmh.ox.ac.uk> writes:
> ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov) > NE*000 ethercard probe at 0x300: 00 00 e8 2b 76 73 > eth0: NE2000 found at 0x300, using IRQ 4. > Looking up port of RPC 100003/2 on 163.1.138.129 > Looking up port of RPC 100005/1 on 163.1.138.129 > VFS: Mounted root (nfs filesystem).
> Once root is mounted, various daemons fire off, and then the attempt > to mount /home produces: > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > lockd_up: makesock failed, error=-111 > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending)
> Although this may be due to the RH startup scripts producing a broken > routing table. After this everything's OK and I can log in, fix the > routes and fire up Quake, ftp, telnet, ssh, etc...
FWIW, I see the same kind of messages on 2.1.58 compiled on RH thunderbird, when trying to mount up NFS volumes at boot. If make them ``noauto'' in fstab, I can mount them painlessly after boot.
The network card is 3Com Etherlink III, and the NFS server is a Solaris box, if that matters.
~kzm -- If I haven't seen further, it is by standing in the footprints of giants
| |