• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 929 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.

Mount NFS error after linux booting

ben zhan
Intellectual 700 points

4572.dvsdk-omapl138 nfs error.txt

hi,

     I boot the linux from /dev/mtdblock4 of nandflash,  and I can boot the linux from nfs filesystem after uboot booting.   These two booting methods are ok!,   So this can proof the NFS sever is ok.         I start the kernel and jffs2 filesystem ok, but when I use the command under below:

"mount -o nolock -t nfs 192.168.6.103:/home/disk/dvsdkfs /mnt/fs"  I got some errors below:

mount -o nolock -t nfs 192.168.6.103:/home/disk/dvsdkfs /mnt/fs

   mount: wrong fs type, bad option, bad superblock on 192.168.6.103:/home/disk/dvsdkfs,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

I used the package "arago-base-tisdk-image-da850-omapl138-evm.tar.gz " to make jffs2 fs.    details in the file uploaded!

I don't know how to solve the problem, please give me hand ,thanks!

  • 0
    Guru 26430 points

    A few people on this forum have had this problem. They solved it by repeating the NFS server address in the mount options, eg.

    mount -o nolock,addr=192.168.6.103 -t nfs 192.168.6.103:/home/disk/dvsdkfs /mnt/fs

     

  • 0 in reply to Norman Wong
    Intellectual 700 points

    hi,Norman

           Thanks for your reply.   My problem  was solved.  But I can't understand why we should repeat the nfs server addr ,but in some fs it is not necessary!

     

     

  • 0 in reply to ben zhan
    Guru 26430 points

    I believe the mount command is not the same code across all platforms. Most embedded systems use the "do all" BusyBox implementation. Others use the a standalone program, I think it's part of the GNU Linux utils package. Both interpret the command line parameters differently before eventually calling mount in the kernel.