All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maximus <john.maximus@gmail.com>
To: nfs@lists.sourceforge.net
Subject: Nfs Server not responding ?
Date: Wed, 6 Jul 2005 07:32:46 -0400	[thread overview]
Message-ID: <3634de7405070604326a08bedd@mail.gmail.com> (raw)

Hi,
  I am getting the following error in my system

I have a root file system ar /home/rootfs

I dont know what is the problem. please help.

The Kernel is getting copied on target ; But root file system is not
getting mounted
using NFS.

The Kernel and the root file system is in the same machine
XX.YY.13.112.

IP-Config: Got DHCP answer from XX.YY.13.112, my address is XX.YY.13.65
IP-Config: Complete:
      device=3Deth0, addr=3DXX.YY.13.65, mask=3D255.255.255.0,
gw=3D255.255.255.255,
     host=3DXX.YY.13.65, domain=3D, nis-domain=3D(none),
     bootserver=3DXX.YY.13.112, rootserver=3DXX.YY.13.112,
rootpath=3D/home/rootfs
Looking up port of RPC 100003/2 on XX.YY.13.112
Looking up port of RPC 100005/1 on XX.YY.13.112
Root-NFS: Server returned error -13 while mounting /home/rootfs
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: No root yet, retrying to mount root on nfs (unknown-block(2,0))
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=3D" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0)

File : /etc/exports looks like this
/home/rootfs (rw,no_root_squash,no_all_squash)

File:/etc/dhcpd.conf looks this this

ddns-update-style ad-hoc;
allow bootp;
subnet XX.YY.13.0 netmask 255.255.255.0 {
default-lease-time 1209600;
max-lease-time 31557600;
group {
host hello.i2.com {
hardware Ethernet 00:0E:99:XX:YY:ZZ;
fixed-address XX.YY.13.65;
option root-path "/home/rootfs";

}
}
}


I also face one more issue i am facing is:
   i have 2 kernels (both of them 2.6.12) made out of the same
defconfig but compiled using 2 different tool chains.

For Kernel1:

If I specify bootargs=20
mem=3D30M console=3DttyS0,115200 rw root=3D/dev/nfs
nfsroot=3DXX.YY.13.112:/home/rootfs ip=3DXX.YY.13.65:XX.YY.13.112

it Works.

Otherwise it does not work ?.

For Kernel2:
Does not work with the above bootargs

Works Only if bootargs are mem=3D30M console=3DttyS0,115200 rw root=3D/dev/=
nfs=20

Please advice,

I dont know what the problem is ?.

How to analyse the problem and solve it ?.



Regards,
John


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2005-07-06 11:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3634de7405070604326a08bedd@mail.gmail.com \
    --to=john.maximus@gmail.com \
    --cc=nfs@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.