From: Andre Haupt <haupt.andre@gmx.de>
To: Manjunath AM <Manjunath.AM@Lntemsys.com>
Cc: kernelnewbies@nl.linux.org, linuxppc-embedded@ozlabs.org
Subject: Re: nfs mounting problem
Date: Tue, 23 Jan 2007 13:59:55 +0100 [thread overview]
Message-ID: <45B606CB.4050305@gmx.de> (raw)
In-Reply-To: <OF08754E94.1194DC2D-ON6525726C.0043EADB-6525726C.0044D6F4@lntemsys.com>
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 prev parent reply other threads:[~2007-01-23 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 12:33 nfs mounting problem Manjunath AM
2007-01-23 12:59 ` Andre Haupt [this message]
2007-01-23 13:23 ` Manjunath AM
2007-01-23 13:57 ` Andre Haupt
2007-01-23 15:32 ` Scott Wood
2007-01-24 8:10 ` Andre Haupt
2007-01-30 18:41 ` Manjunath AM
2007-10-12 9:13 ` Abhijit Naik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45B606CB.4050305@gmx.de \
--to=haupt.andre@gmx.de \
--cc=Manjunath.AM@Lntemsys.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).