• Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 492 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

error configuring NFS file-system

Bertrand Laborde
Prodigy 30 points
Other Parts Discussed in Thread: SYSCONFIG

Hello everyone,

I'm having issues configuring the NFS root file-system.
I have a OMAP3505 card (Micron) and my host machine runs under Fedora 9

I copied the nfs.tar.gz file from the SDK and extracted it in /mnt/omap3evmNfs in my host server (IP=131.167.122.141)
I set the IP of the OMAP card : 131.167.122.10

Then, I modified /etc/exports as follow:
--
/mnt/omap3evmNfs 131.167.122.0/255.255.252(rw,sync,no_subtree_check)
--

Then I executed the command:
> /usr/sbin/exportfs -ra

I kept the files /etc/hosts.allow and /etc/hosts.deny empty

I started nfs service because it seems it doesn't launch at boot time:
> /etc/init.d/nfs start
> /etc/init.d/nfslock start

Now, when I execute the command /usr/sbin/rpcinfo -p, I have:
 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   4003  status
    100024    1   tcp   4003  status
    100011    1   udp    875  rquotad
    100011    2   udp    875  rquotad
    100011    1   tcp    875  rquotad
    100011    2   tcp    875  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100021    1   udp   4002  nlockmgr
    100021    3   udp   4002  nlockmgr
    100021    4   udp   4002  nlockmgr
    100021    1   tcp   4002  nlockmgr
    100021    3   tcp   4002  nlockmgr
    100021    4   tcp   4002  nlockmgr
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100005    1   udp   4001  mountd
    100005    1   tcp   4001  mountd
    100005    2   udp   4001  mountd
    100005    2   tcp   4001  mountd
    100005    3   udp   4001  mountd
    100005    3   tcp   4001  mountd

Finally, I set up the OMAP EVM:

OMAP3EVM # printenv
bootargs=mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2
baudrate=115200
preboot=
bootfile="uImage"
filesize=cc4c44
fileaddr=81600000
ethaddr=00:50cc2:7e:8a:f8
ipaddr=131.167.122.10
serverip=131.167.122.141
netmask=255.255.252.0
gatewayip=131.167.135.254
get_kernel=run nand_kernel
get_initrd=run nand_initrd
nand_kernel=nand read.i 0x80000000 280000 200000
nand_initrd=nand read.i 0x81600000 780000 1000000
tftp_kernel=tftpboot 0x80000000 uImage
tftp_initrd=tftpboot 0x81600000 ramdisk.gz
bootargs_rd=mem=128M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,40M ramdisk_size=40960
bootargs_fs=mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2
addip=setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:on
boot_rd=run get_kernel; run get_initrd; setenv bootargs $(bootargs_rd); run addip; bootm 0x80000000
boot_fs=run get_kernel; setenv bootargs $(bootargs_fs); run addip; bootm 0x80000000
boot_nfs=run get_kernel; setenv bootargs $(bootargs_nfs); run addip; bootm 0x80000000
bootdelay=5
bootcmd=run boot_nfs
bootargs_nfs=console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=131.167.122.141:/mnt/omap3evmNfs, nolock mem=128M
stdin=serial
stdout=serial
stderr=serial
mmcboot=mmcinit;fatload mmc 0 0x80000000 uImage;fatload mmc 0 0x81600000 ramdisk.gz;bootm 0x80000000

--------
Now when I try to boot the card I get the error :
...
IP-Config: Complete:
      device=eth0, addr=131.167.122.10, mask=255.255.252.0, gw=131.167.135.254,
     host=131.167.122.10, domain=, nis-domain=(none),
     bootserver=131.167.122.141, rootserver=131.167.122.141, rootpath=
Looking up port of RPC 100003/2 on 132.166.132.141
eth0: link up, 100Mbps, full-duplex, lpa 0x8DE1
Looking up port of RPC 100005/1 on 132.166.132.141
call_verify: unknown auth error: 7
Root-NFS: Server returned error -5 while mounting /mnt/omap3evmNfs
VFS: Unable to mount root fs via NFS, trying floppy.
...

I disabled the firewire but I have always the same problem.

Please can you help me ?

Sincerly

  • TI__Mastermind 41665 points

    I am curious what host Linux distribution you are using?

    In the past typically I have seen the -5 error fixed by disabling the host's firewall, however just recently another forum member LorryAstra was getting this same -5 error and was able to trace it to a recent update to his Fedora 10 host machine as shown in his post here.

  • in reply to Bernie Thompson TI
    Prodigy 30 points

    I'm using Fedora 9 (kernel 2.6.27.9-73).

    Thanks for your link, I checked and ping works fine on both sides and tftp too. I have indeed enabled updates on Fedora and unfortunately I can't reinstall all my system.

    I'm wondering if nfs is activated on my client (evm). I can't check it from my server:

    # /usr/sbin/rpcinfo -p 131.167.122.10
    rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused

    I get this even when my firewall is disabled. What does it mean ?

  • in reply to Bertrand Laborde
    TI__Mastermind 41665 points

    As long as you are booting the provided kernel with the suggested U-Boot arguments you should have NFS on the EVM side, I suspect this is a host configuration issue. This particular error seems to be discussed a lot on the net, it seems that this means that portmapper is not running or that your /etc/hosts is configured to block portmapper, see the bottom of this web page where this is mentioned, there are other places on the net that discuss this it seems so I am sure you can find a solution through google, unfortunately since I do not have your exact host environment it is not practical for me to try to reproduce the issue so I cannot say exactly what is going wrong.

  • in reply to Bernie Thompson TI
    Prodigy 30 points

    I solved the problem but I don't know how. I saw people on the net having trouble with nfs under Fedora 10. They downgrade the nfs-utils package. I tried this and started again the configuration. I kept the files /etc/hosts.allow and /etc/hosts.deny empty. I uncommented the following lines in /etc/sysconfig/nfs:

    RQUOTAD_PORT=875
    LOCKD_TCPPORT=32803
    LOCKD_UDPPORT=32769
    MOUNTD_PORT=892
    STATD_PORT=662

    and opened those ports on my firewall.

    Then I restarted all the services:

    # /etc/init.d/rpcbind restart

    # /etc/init.d/nfs restart

    # /etc/init.d/nfslock restart

    I all was working fine. Then I tried this with the last version of nfs-utils and it was working too!

    I was quietly sure I had tested this before but maybe I made a mistake somewhere.

    Anyway thanks a lot for your help