nfs mounting problem
Manjunath AM
Manjunath.AM at Lntemsys.com
Wed Jan 24 00:23:45 EST 2007
Thanks for your reply, Yes portmap is running and when i give netstat -an
| grep ":111 " this server shows the below:
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:111 0.0.0.0:*
Thanks & Regards
MANJUNATH AM
Senior Software Engineer
Emsys
Larsen & Toubro Limited
Mysore-570018
Mobile:9886375926
Andre Haupt <haupt.andre at gmx.de>
01/23/2007 06:29 PM
To
Manjunath AM <Manjunath.AM at Lntemsys.com>
cc
linuxppc-embedded at ozlabs.org, kernelnewbies at nl.linux.org
Subject
Re: nfs mounting problem
Manjunath AM wrote:
>
> Hi,
Hi,
>
> Looking up port of RPC 100003/2 on 192.168.178.110
> portmap: server 192.168.178.110 not responding, timed out
> Root-NFS: Unable to get nfsd port number >from server, using default
> Looking up port of RPC 100005/1 on 192.168.178.110
> portmap: server 192.168.178.110 not responding, timed out
> Root-NFS: Unable to get mountd port number from server, using default
> mount: server 192.168.178.110 not responding, timed out
> Root-NFS: Server returned error -5 while mounting
> /opt/montavista/pro/devkit/ppc/82xx/target
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "nfs" or unknown-block(2,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
> <0>Rebooting in 180 seconds..
is portmap actually running?
try ps -e | grep portmap
if it is
netstat -an | grep ":111 "
should report something like this.
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:111 0.0.0.0:*
Best regards,
Andre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20070123/b3a5cf74/attachment.htm
More information about the Linuxppc-embedded
mailing list