From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Error with Root-fs on NFS...
Date: 24 Jan 2002 12:29:52 +0100 [thread overview]
Message-ID: <shs1yggdm1b.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.30.0201241036100.29293-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0201241036100.29293-100000@mustard.heime.net>
>>>>> " " == Roy Sigurd Karlsbakk <roy@karlsbakk.net> writes:
> Hi all I apologize if this is a well-known error, but after
> searching all archives I can think of, including google, I
> still can't find anything but questions.
> Version: linux-2.4.17+Tux2.4.17a0+rmap11c+ide2.4.17.01192002
> sockets 1.0/SMP for Linux NET4.0. Looking up port of RPC
> 100003/2 on 192.168.144.247 RPC: sendmsg returned error 101
> portmap: RPC call returned error 101 Root-NFS: Unable to get
> nfsd port number from server, using default Looking up port of
> RPC 100005/1 on 192.168.144.247 RPC: sendmsg returned error 101
> portmap: RPC call returned error 101 Root-NFS: Unable to get
> mountd port number from server, using default RPC: sendmsg
> returned error 101 mount: RPC call returned error 101 Root-NFS:
> Server returned error -101 while mounting /croot VFS: Unable to
> mount root fs via NFS, trying floppy.
Well:
Is there a portmapper running on the server?
Is it accessible to the client (/etc/hosts.{allow,deny}, ipchains,...)?
Is the portmapper advertising NFS version 2 (BTW: the syntax is 'v3' not 'nfsvers=3' on NFSroot)?
Is it advertising mountd version 1?
Cheers,
Trond
next prev parent reply other threads:[~2002-01-24 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 10:35 Roy Sigurd Karlsbakk
2002-01-24 11:29 ` Trond Myklebust [this message]
2002-01-24 11:36 ` Roy Sigurd Karlsbakk
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=shs1yggdm1b.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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
all inboxes | Powered by JetHome®