SMDK2450 board - Linux kernel root file system not getting mounted
Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
SMDK2450 board - Linux kernel root file system not getting mounted
Hello experts,
We have SMDK2450 board based on S3c2450 processor. We have beeen trying hard to get Linux kernel working on the board. The NAND flash interface is not working in the board. Hence we moved to boot the kernel using NFS root file system. But this is not going through. Here is the log:
Looking up port of RPC 100003 / 2 on 192.168.1.10
Root-NFS: Unable to get nfsd port number from server, using default
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.1.10
Root-NFS: Unable to get mountd port number from server, using default
Root-NFS: Server returned error -101 while mounting /opt/eldk/arm
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block (2,0)
I have checked NFS server setup in Ubuntu 9.1 host and also have cehcked that NFS is enabled in kernel. Any help would be of great help.
Thanks for looking into it. We did a re-installation of Ubuntu to just check whether that might be an issue based on suggestion from net.
But the situation remains the same and here is the server log:
qmax@Qmax-U910:~$ tail -f /var/log/daemon.log
Jan 5 10:33:53 Qmax-U910 xinetd[2786]: removing echo
Jan 5 10:33:53 Qmax-U910 xinetd[2786]: removing time
Jan 5 10:33:53 Qmax-U910 xinetd[2786]: removing time
Jan 5 10:33:53 Qmax-U910 xinetd[2786]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Jan 5 10:33:53 Qmax-U910 xinetd[2786]: Started working: 1 available service
Jan 5 10:33:57 Qmax-U910 tftpd[2789]: tftpd: trying to get file: zImage
Jan 5 10:33:57 Qmax-U910 tftpd[2789]: tftpd: serving file from /tftpboot
Jan 5 10:36:14 Qmax-U910 nfsd[2846]: nfssvc: Setting version failed: errno 16 (Device or resource busy)
Jan 5 10:41:39 Qmax-U910 NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
Jan 5 10:41:41 Qmax-U910 NetworkManager: <info> (eth0): carrier now ON (device state 8)
qmax@Qmax-U910:~$ exportfs -a
exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 13 (Permission denied)
exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 13 (Permission denied)
exportfs: can't lock /var/lib/nfs/etab for writing
qmax@Qmax-U910:~$ sudo exportfs -a
[sudo] password for qmax:
qmax@Qmax-U910:~$
Well, first you have this annoying error in your log message:
Code:
nfsd[2846]: nfssvc: Setting version failed: errno 16 (Device or resource busy)
So I am not sure that your NFS server is up and running.
Then, about the "exportfs" command, sorry but I made a mistake. In fact, I need the result of this command without any arguments, I mean:
Code:
exportfs
or the result of the following command:
Code:
cat /etc/exports
Another useful info would be the result of:
Code:
rpcinfo -p
Also, have you any error messages on server side (in daemon.log file) when client try to do its mount request ? Have you do any modifications in hosts.allow or hosts.deny files ?
qmax@Qmax-U910:~/BM/BSP/s3c-u-boot-1.1.6$ cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
# /filesystem qmax@Qmax-U910(rw,no_root_squash)
/home/qmax/blookmark/wordir/eldk/arm 192.168.1.20(rw,sync,no_root_squash,no_subtree_check)
Well it seems that on client side you try to mount the following directory: /opt/eldk/arm
But on the server side, you just have exported the following directory: /home/qmax/blookmark/wordir/eldk/arm
And it does not match :'(
You have to modify one of your config to make things matched.
I realized that and I changed the root path in the bootargs environment variable. Still there is no improvement. I also did a check on the kernel configuration that NFS is included. Now I am planning to change the bootargs in the U-boot code itself and try it once more ....
Monitor (tail -f) /var/log/messages on the NFS server while booting the SMDK2450 board. See if the requests for mounting are arriving, and what the NFS server is doing with any requests that arrive. Loosen up the client address range on the NFS server (and then restart the server), and try mounting the NFS export from another host; one that is fully booted and running. Show us the results of these tests.
Thanks again for the support and here is the /var/log/daemon.log output:
qmax@Qmax-U910://$ tail -f /var/log/daemon.log
Jan 10 11:05:37 Qmax-U910 xinetd[18527]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Jan 10 11:05:37 Qmax-U910 xinetd[18527]: Started working: 1 available service
Jan 10 11:05:37 Qmax-U910 nfsd[18548]: nfssvc: Setting version failed: errno 16 (Device or resource busy)
Jan 10 11:06:05 Qmax-U910 tftpd[18567]: tftpd: trying to get file: zImage
Jan 10 11:06:05 Qmax-U910 tftpd[18567]: tftpd: serving file from /tftpboot
Jan 10 11:12:15 Qmax-U910 ntfs-3g[18737]: Version 2010.3.6 external FUSE 28
Jan 10 11:12:15 Qmax-U910 ntfs-3g[18737]: Mounted /dev/sdc1 (Read-Write, label "", NTFS 3.1)
Jan 10 11:12:15 Qmax-U910 ntfs-3g[18737]: Cmdline options: rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,dmask=0077
Jan 10 11:12:15 Qmax-U910 ntfs-3g[18737]: Mount options: rw,nosuid,nodev,uhelper=udisks,silent,allow_other,nonempty,relatime,fsname=/dev/sdc1,blkdev,blksize=4096,default_permissions
Jan 10 11:12:15 Qmax-U910 ntfs-3g[18737]: Global ownership and permissions enforced, configuration type 1
E 28
Jan 10 11:12:15 Qmax-U910 ntfs-3g[18737]: Mounted /dev/sdc1 (Read-Write, label "", NTFS 3.1)
Jan 10 11:12:15 Qmax-U910 ntfs-3g[18737]: Cmdline options: rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,dmask=0077
Jan 10 11:12:15 Qmax-U910 ntfs-3g[18737]: Mount options: rw,nosuid,nodev,uhelper=udisks,silent,allow_other,nonempty,relatime,fsname=/dev/sdc1,blkdev,blksize=4096,default_permissions
I could not see any network related info in /var/log/messages and I have enclosed that file here as attachment.
I have also enclosed the serial log from kernel during boot process.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.