• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 394 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.

NFS boot last error

jang soyoung
Prodigy 10 points

My error message is here..

Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000
   Image Name:   Linux-2.6.10_mvl401
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1578804 Bytes =  1.5 MB
   Load Address: 80008000
   Entry Point:  80008000
## Booting image at 80700000 ...
   Image Name:   Linux-2.6.10_mvl401
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1578804 Bytes =  1.5 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
OK
 
Starting kernel ...
 
Uncompressing Linux...............

.......

eth0: link down
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 192.168.0.10, my address is 192.168.0.150
IP-Config: Complete:
      device=eth0, addr=192.168.0.150, mask=255.255.255.0, gw=192.168.0.1,
     host=192.168.0.150, domain=carrote.co.kr, nis-domain=carrote.co.kr,
     bootserver=192.168.0.10, rootserver=192.168.0.10, rootpath=
Looking up port of RPC 100003/2 on 192.168.0.10
Looking up port of RPC 100005/1 on 192.168.0.10
VFS: Mounted root (nfs filesystem).
Freeing init memory: 180K
Warning: Cannot create /dev/console: -2Warning: unable to open an initial consol
e.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
 <6>eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
 

I confirmed  VFS: Mounted root (nfs filesystem). message.

Then, I meet a error message at the next line.

so I cannot process next step ( like a login)

Already, Host started NFS, PORTMAP, DHCP and firewall was disabled. (so I can success VFS mount).

and /etc/exports file is like below

 /nfsroot  192.168.0.150(rw,no_root_squash)

 I didn't know why nfs boot is not working.

As I boot u-boot mode, I have no problem.

Please help me..

 

 

 

 

  • 0
    TI__Guru 64440 points

    This type of error message generally happens because the target filesystem which is being mounted does not contain the appropriate files.  I would agree that you are successfully getting communications between the target board and the NFS server going, but the filesystemon the NFS server is not complete.

    Did you copy the target filesystem when logged in as the root user?  This is important as the creation of the target filesystem requires these root permissions to create certain files, such as the inodes in the /dev directoty, etc.

  • 0
    TI__Mastermind 41665 points

    In addition to extracting the files as root as Brandon mentioned, I have also seen this happen if you copy the filesystem you are mounting on the host without the -a option of cp, if you do a plain old cp you end up breaking symbolic links leading to a lack of init.

    Also, I use (rw, no_root_squash,no_all_squash,sync) for the NFS settings in my /etc/exports file, though I think this just changes other behavior of the NFS service and will not directly relate to this particular issue.