Hi All,
I just started with an AM1808 EVM Development Kit.
I’m trying to boot via tftp and use nfs as root filesystem.
My Target(AM1808) ip assigned as - 192.168.1.100
My Host Ubuntu(10.04LTE)server - 192.168.1.200.
I have modified few steps for NFS as follows:
- I have modified in /etc/exports the following line:
/home/kumar/AM1808/filesys *(rw,sync,no_subtree_check)
- And, in /etc/hosts.allow:
portmap mountd nfsd statd lockd rquotad : 192.168.1.10
- And, in /etc/hosts.deny:
portmap mountd nfsd statd lockd rquotad : ALL
- Then I started my NFS services:
root$ service portmap start
root$ /etc/init.d/nfs-kernel-server restart
- NFS service is running on Ubuntu as below:
root@ubuntu:/etc# ps -e | grep nfs
671 ? 00:00:00 nfsiod
2145 ? 00:00:00 nfsd4
2146 ? 00:00:00 nfsd
2147 ? 00:00:00 nfsd
2148 ? 00:00:00 nfsd
2149 ? 00:00:00 nfsd
2150 ? 00:00:00 nfsd
2151 ? 00:00:00 nfsd
2152 ? 00:00:00 nfsd
2153 ? 00:00:00 nfsd
- I Run this command to check the NFS service is running or not:
root@ubuntu:/etc# chkconfig | grep nfs
nfs-kernel-server on
umountnfs.sh 0
- I have Checked rpc service is started or not using following comment:
root@ubuntu:/etc# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 59266 status
100024 1 tcp 51333 status
100021 1 udp 47282 nlockmgr
100021 3 udp 47282 nlockmgr
100021 4 udp 47282 nlockmgr
100021 1 tcp 45584 nlockmgr
100021 3 tcp 45584 nlockmgr
100021 4 tcp 45584 nlockmgr
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 56583 mountd
100005 1 tcp 41591 mountd
100005 2 udp 56583 mountd
100005 2 tcp 41591 mountd
100005 3 udp 56583 mountd
100005 3 tcp 41591 mountd
- Exporting the file systems for mounting
root@ubuntu:/etc# sudo exportfs -ra
exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/home/kumar/AM1808/filesys".
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x
- root@ubuntu:/etc# /etc/init.d/nfs-kernel-server restart
* Stopping NFS kernel daemon [ OK ]
* Unexporting directories for NFS kernel daemon... [ OK ]
* Exporting directories for NFS kernel daemon...
exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/home/kumar/AM1808/filesys".
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x [ OK ]
* Starting NFS kernel daemon [ OK ]
root@ubuntu:/etc# chkconfig | grep nfs-kernel-server
nfs-kernel-server on
- root@ubuntu:/etc# service portmap restart
portmap start/running, process 700
- root@ubuntu:/etc# chkconfig | grep portmap
portmap off
portmap-boot off
portmap-wait off
Target Bootargs
ethaddr=00:08:EE:04:32:85 serverip=192.168.6.16 eth0 192.168.1.10 sereverip=192.168.1.1 bootdelay=3 baudrate=115200 autoload=no get_kernel=run
tftp_kernel eth0=192.168.1.200 bootserver=192.168.1.100 addr=192.168.1.200 mask=255.255.255.0 gw=192.168.1.1 host=192.168.1.100 ipaddr=192.168.1.10 serverip=192.168.1.100 filesize=2040D0 fileaddr=C0700000 loadaddr=0xc0700000 ip=192.168.1.100:192.168.1.200:192.168.1.1:255.255.255.0::eth0:off mmcboot=mmc init;
fatload mmc 0 0x80000000 uImage; bootm 0x80000000 get_initrd=run
nand_initrd serverip=192.168.1.200 netmask=255.255.255.0 gatewayip=192.168.1.1 dnsip=192.168.1.1 nfshost=192.168.1.100 rootpath=/targetNFS bootfile=uImage bootcmd=static;tftp;bootm ipaddr=192.168.1.100:192.168.1.200:192.168.1.1:255.255.255.0::eth0:off bootargs=console=ttyS2,115200n8
noinitrd rw ip=192.168.1.100:192.168.1.200:192.168.1.1:255.255.255.0::eth0:off
root=/dev/nfs nfsroot=192.168.1.200:/targetNFS, nolock mem=32M stdin=serial stdout=serial stderr=serial ver=U-Boot 2009.11
(Mar 25 2010 - 14:39:42)
After target is
booting the uImage through tftp transfer, I am getting the following error
related to nfs:
omap_rtc omap_rtc:
setting system clock to 2000-01-01 00:00:00 UTC (946684800) eth0: attached PHY
driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=1:00, id=7c0f1) IP-Config: Complete: device=eth0, addr=192.168.1.100,
mask=255.255.255.0, gw=192.168.1.1, host=192.168.1.100, domain=,
nis-domain=(none), bootserver=192.168.1.200,
rootserver=192.168.1.200, rootpath= Looking up port of RPC
100003/2 on 192.168.1.200 PHY: 1:00 - Link is Up
- 100/Full rpcbind: server
192.168.1.200 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.200 rpcbind: server
192.168.1.200 not responding, timed out Root-NFS: Unable to
get mountd port number from server, using default Root-NFS: Server
returned error -110 while mounting /home/kumar/AM1808/filesys 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 256 mtdblock0 (driver?) 1f01 64 mtdblock1 (driver?) 1f02 7808 mtdblock2 (driver?) 1f03 64 mtdblock3 (driver?) Kernel panic - not
syncing: VFS: Unable to mount root fs on unknown-block(2,0) Backtrace: [<c0031730>]
(dump_backtrace+0x0/0x114) from [<c0320420>] (dump_stack+0x18/0x1c) r7:00008000 r6:c1c13000 r5:c0025a08
r4:c0446f38 [<c0320408>]
(dump_stack+0x0/0x1c) from [<c0320488>] (panic+0x64/0x13c) [<c0320424>]
(panic+0x0/0x13c) from [<c0008fec>] (mount_block_root+0x1e0/0x220) r3:00000001 r2:00000001 r1:c1c23f60
r0:c03b5856 [<c0008e0c>]
(mount_block_root+0x0/0x220) from [<c00090f0>] (mount_root+0xc4/0xfc) r8:00000000 r7:00000000 r6:00000000
r5:00000000 r4:00200000 [<c000902c>]
(mount_root+0x0/0xfc) from [<c0009298>] (prepare_namespace+0x170/0x1c8) r5:c0025a08 r4:c0446a20 [<c0009128>]
(prepare_namespace+0x0/0x1c8) from [<c00084c8>] (kernel_init+0xf0/0x12c) r5:00000000 r4:c04467e0 [<c00083d8>]
(kernel_init+0x0/0x12c) from [<c0045424>] (do_exit+0x0/0x6b4) r5:00000000 r4:00000000
I believe this is because mount is not connected properly. Can I know the issue where I have missed it? Please give a suggestions.
Thanks,
Francis