Root-NFS: Unable to get mountd port number from server, using de

Forum: Linux
vatti 
Hi All

Regarding NFS File system

eth0: link down                                                            
    
IP-Config: Guessing netmask 255.255.255.0                                  
    
IP-Config: Complete:                                                       
    
     device=eth0, addr=192.168.1.0, mask=255.255.255.0, gw=255.255.255.255,
    
     host=192.168.1.0, domain=, nis-domain=(none),                         
    
     bootserver=255.255.255.255, rootserver=192.168.1.1, rootpath=         
    
Looking up port of RPC 100003/2 on 192.168.1.1                             
    
eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1                            
    
rpcbind: server 192.168.1.1 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.1.1                             
    
rpcbind: server 192.168.1.1 not responding, timed out                      
    
Root-NFS: Unable to get mountd port number from server, using default      
    
Root-NFS: Server returned error -5 while mounting /export/fs               
    
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; here are the available
partitions: 
1f00             384 mtdblock0 (driver?)                                   
    
1f01            2048 mtdblock1 (driver?)                                   
    
1f02          128640 mtdblock2 (driver?)                                   
    
1f03          131072 mtdblock3 (driver?)                                   
    
b300         1931264 mmcblk0 driver: mmcblk                                
    
  b301          203616 mmcblk0p1                                           
    
  b302          203616 mmcblk0p2                                           
    
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)  

could you please suggest me,to solve this problem.

mizch 
> device=eth0, addr=192.168.1.0, mask=255.255.255.0,

Giving your eth0 an IP od xxx.xxx.xxx.0 is a bad idea.  This IP (in
conjunction with the above netmask) is reserved for a net, not an
individual member of the net.  Better use something in the range .1 ...
.254 (and take care that it doesn't collide with other members of the net,
i.e. the chosen IP must be unique on your net).

> rpcbind: server 192.168.1.1 not responding, timed out              

This may be or may be not a consequence of the above error.  Correct it,
and if the error message persists, check that there is indeed an NFS server
on 192.168.1.1 listening and your mini2440's IP is there allowed to access
it ("man exports" will be of help for the latter one).  If all is well up
to this point, check the server's logfile.

vatti 
Thnks for reply

device=eth0, addr=192.168.1.25, mask=255.255.255.0

where we can find server's logfile.

mizch 
> where we can find server's logfile.

Erm ... that depends on the operating system the server is running.  If it
is Linux, have a looh into the directory /var/log.

mizch 
s/looh/look/

duraisamy 
dear Friend 


check your firewall setting and also disable your firewall...


it will work

vinge 
I have a problem just like your's
http://www.friendlyarm.net/forum/topic/3049

I can even ping the qemu's virtual net card(not the tap0 ip,but the 2440's
）

can duraisamy tell us how to disable firewall?

whitebank 
Hi
In Ubuntu, you can disable firewall by this:
$sudo ufw disable

You can link to here for more information connected by NFS
http://mini2440vietnam.blogspot.com/2012/05/share-files-with-nfs.html

cacster 
Have you solve your problem?

$$$dollar 
Hi, guys..
Regarding NFS fs

eth0: link down                                                            
    
IP-Config: Guessing netmask 255.255.255.0                                  
    
IP-Config: Complete:                                                       
    
     device=eth0, addr=192.168.1.6, mask=255.255.255.0, gw=255.255.255.255,
    
     host=192.168.1.6, domain=, nis-domain=(none),                         
    
     bootserver=255.255.255.255, rootserver=192.168.1.5, rootpath=         
    
Looking up port of RPC 100003/2 on 192.168.1.5                            
    
eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1                            
    
rpcbind: server 192.168.1.5 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.1.5                            
    
rpcbind: server 192.168.1.5 not responding, timed out                      
    
Root-NFS: Unable to get mountd port number from server, using default      
    
Root-NFS: Server returned error -5 while mounting /export/fs               
    
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; here are the available
partitions: 
1f00             384 mtdblock0 (driver?)                                   
    
1f01            2048 mtdblock1 (driver?)                                   
    
1f02          128640 mtdblock2 (driver?)                                   
    
1f03          131072 mtdblock3 (driver?)                                   
    
b300         1931264 mmcblk0 driver: mmcblk                                
    
  b301          203616 mmcblk0p1                                           
    
  b302          203616 mmcblk0p2                                           
    
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown
block(2,0)
Please help...fixing the problem....

canyiah 
I had a similar problem with my mini2440 using fedora 14 I may have had
several problems i was using virtualbox first make sure that your eth0 is
actually the physical Ethernet port(settings->Network in adapter 1 select
bridged adapter, Ethernet controller(mine was Realtek PCIe GBE Family
Controller) you can probably use NAT but i wanted to be able to get on the
internet as well make sure cable connected is checked. this is extra if you
are using a usb to serial goto settings->USB and add the usb device this
will automatically enable it each time the vm starts. connect your device
to your computer(it must be powered) type ifconfig eth0 should be whatever
ip address you assigned to eth0 for my example eth0 should have been
192.168.1.27 i changed it using GUI System->Admin->Network edit eth0
statically seet ip 192.168.1.27 netmask 255.255.255.0 default gateway
192.168.1.1 but for some reason eth0 was not changing so i manually changed
it using command line in terminal(ifconfig 192.168.1.27 netmask
255.255.255.0 as disabled the firewall service iptables save, service
iptable stop, chkconfig iptables off) then it worked.

Gautam 
>>>>>>>>>>>>>>>>>>>>>>>>>>

rpcbind: server 192.168.1.5 not responding, timed out                      
    
Root-NFS: Unable to get nfsd port number from server, using default

<<<<<<<<<<<<<<<<<<<<<<<<<<



Hmmm... looks like the portmapper daemon of NFS server isn't responding.
The portmapper daemon is responsible for exposing the ports on which the
other NFS daemons (nfsd, mountd, statd etc.) listen.

Use 'rpcinfo -p' command to check status of all RPC utility programs on the
server.

HTH,

Gautam

Babu Alikapati 
Hi, 

I am Having the same problem as shown above. below is the log for 

"rpcinfo -p". What can i do now...?


/mini2440/u-boot/u-boot_20100701$ rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  48161  status
    100024    1   tcp  51204  status
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049
    100227    3   tcp   2049
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049
    100227    3   udp   2049
    100021    1   udp  52670  nlockmgr
    100021    3   udp  52670  nlockmgr
    100021    4   udp  52670  nlockmgr
    100021    1   tcp  53778  nlockmgr
    100021    3   tcp  53778  nlockmgr
    100021    4   tcp  53778  nlockmgr
    100005    1   udp  40120  mountd
    100005    1   tcp  52715  mountd
    100005    2   udp  37540  mountd
    100005    2   tcp  48922  mountd
    100005    3   udp  53744  mountd
    100005    3   tcp  35378  mountd

vic pucknell 
This is almost aways the linux internal firewall. 
  Mark the port as trusted then incoming requests for NFS helper functions
can get through