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.

Booting from MMC Using NFS File System Error

Hi,

I boot AM3517EVM from MMC using nfs file system and  get those error

Afer a sequence of boot up,I get those error

eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:00, id=7c0f1)

Sending DHCP requests .

PHY: 1:00 - Link is Up - 10/Half

., OK

IP-Config: Got DHCP answer from 192.168.1.18, my address is 192.168.1.152

IP-Config: Complete:

     device=eth0, addr=192.168.1.152, mask=255.255.255.0, gw=192.168.1.18,

     host=dhcppc52, domain=, nis-domain=(none),

     bootserver=192.168.1.18, rootserver=192.168.1.112, rootpath=

Looking up port of RPC 100003/2 on 192.168.1.112

Looking up port of RPC 100005/1 on 192.168.1.112

VFS: Mounted root (nfs filesystem) on device 0:13.

Freeing init memory: 152K

INIT: version 2.86 booting

Please wait: booting...

Starting udev

/etc/rcS.d/S03udev: line 50: can't create /tmp/uname: Read-only file system

touch: /tmp/uname: Read-only file system

Remounting root file system...

WARNING: Couldn't open directory /lib/modules/2.6.32-rc5: No such file or directory

FATAL: Could not open /lib/modules/2.6.32-rc5/modules.dep.temp for writing: No such file or directory

I go to watch my host nfs directory also not see those directory but i can find 2.6.31-rc7-omap1 directory

I develop base on PSP-SDK-03.00.00.05 and don't compiler anything just use original ramdisk nfs kernel image  

root: mount: mounting rootfs on / failed: No such file or directory

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create /etc/volatile.cache: Read-only file system

Setting up IP spoofing protection: rp_filter.

Configuring network interfaces... udhcpc (v1.13.2) started

Sending discover...

Sending select for 192.168.1.152...

Lease of 192.168.1.152 obtained, lease time 259200

/etc/udhcpc.d/50default: line 46: can't create /etc/resolv.conf: Read-only file

system

adding dns 168.95.192.1

/etc/udhcpc.d/50default: line 46: can't create /etc/resolv.conf: Read-only filesystem

adding dns 168.95.1.1

/etc/udhcpc.d/50default: line 46: can't create /etc/resolv.conf: Read-only filesystem

done.

rm: cannot remove '/tmp/nfs.tar.gz': Read-only file system

rm: cannot remove '/tmp': Read-only file system

ln: /tmp/tmp: Read-only file system

Wed Dec  2 19:27:00 UTC 2009

Collected errors:

 * Could not obtain administrative lock (ERR: Bad file descriptor) at /usr/lib/opkg/lock

rm: cannot remove '/etc/rcS.d/S98configure': Read-only file system

/etc/init.d/rc: /etc/rcS.d/S99finish.sh: line 5:

Could anyone tall me how to resovle those problem or give a hint?Thanks

Best Regards,

Mark

  • Could you describe the Linux host machine which contains the NFS?  Is it Ubuntu/Red Hat/other?  And what version?

    Could you also provide the /etc/exports file from the host and the u-boot environment variable containing the definition of nfsroot?  May look something like:

    /home/user/rfs *(rw,nohide,insecure,no_subtree_check,async,no_root_squash)

    It appear as if either the parameters in /etc/exports are incorrect/incomplete or some variable in bootargs is missing (or both).  Either could casue the NFS to be read-only.  Do you have "rw" defined as part of the bootargs in u-boot.  It would also help to see the kernel command line from the beginning of the kernel boot sequence.  May look something like:

    Kernel command line: mem=128M console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=128.247.107.65:/home/user/rfs,nolock,rsize=1024,wsize=1024

     

  •  I found my host nfs filesystem didn't set up correctly.

     Now, I already resolve my problem. Thanks! 

    Regards,

    Mark