Broken NFS server (or client?)

[Lincoln Peters]

>From: ME <dugan at passwall.com>
>Reply-To: <talk at nblug.org>
>To: talk at nblug.org
>Subject: Re: Broken NFS server (or client?)
>Date: Wed, 8 Aug 2001 19:04:37 -0700 (PDT)
>
>
>Some questions:
>
>I assume the test client has a local HD since you have LILO being used for
>the netboot testing. This is true?

No, LILO is installed on the boot floppy.  There is no hard disk.
(although since it's a VMWare virtual machine, I can add one with little 
difficulty)


>
>When you boot the client from the local disk, are you able to nfs mount
>the exported volume and use it as you desire to use with a netbooted
>system?

When I tried to mount the root filesystem on another client (it is supposed 
to be mountable to any system that wants to mount it), I got a similar error 
message.

>
>When you write about this error, are you saying that you can't even mount
>your root filesystem via NFS from the client, or once you have the client
>machine net-booted in Linux you get this error when you ry to start up the
>vmware application?

I can't mount the root filesystem via NFS.  I don't think that VMWare is 
causing any problems.

>
>Does the client get a different IP address fron the network when it
>netboots vs. when it is running from a local HD?

It does not have a local HD, but since each system that I run with VMWare 
always seems to get the same IP address every time I run it (I'm not saying 
that they all share a single IP address), I can (hopefully) safely assume 
that the IP addresses are the same.

>
>Is the error logged from the server or the client or both?

The error can't be logged by the client since it has nowhere to log to; it 
just gave me that "Error -101" message that I already described.  And I 
cannot find any NFS logs on the server.

>
>"The client IP address is in the lilo configuration" how? is this an
>"append=" statement? Often those are passed to scripts that do the actual
>work of setting up your interfaces. Is it just getting its IP and nfs root
>server/volume from bootp/dhcp?

The appended lines are:
root=/dev/nfs
nfsroot=192.168.0.6:/

It is configured to get its network configuration from a DHCP server.  
However, I did notice that there is no entry in the DHCP log that looks like 
my test client.  The problem still appeared on the test client as an NFS 
error, though.


>
>Thanks,
>-ME

I hope that this helps.

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp