UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor devarun@18
Visitor
100 Views
Registered: ‎10-12-2018

NFS mount on ZC702 is not happening

Jump to solution

Hi,

I am trying to get the kernel up.

The kernel comes up fine, but I am facing a issue while mounting the root fs with NFS.

The only error I get is “VFS: Unable to mount root fs via NFS, trying floppy.”

 

Below are the steps I followed :

  1. This are my bootargs : bootargs=console=ttyPS0,115200 root=/dev/nfs rootfstype=nfs rootwait nfsroot=134.XX.X.XXX:/proj/nfs/rootfs,v3,tcp ip=dhcp rw
  2. After the uboot is up, I use the “run netboot” command (netboot=tftpboot ${netstart} ${kernel_img} && bootm).
  3. The image gets downloaded from the NFS server through tftp properly and starts booting.
  4. After that I encounter the below error :

 

VFS: Unable to mount root fs via NFS, trying floppy.

List of all partitions:

0100           16384 ram0

(driver?)

0101           16384 ram1

(driver?)

0102           16384 ram2

(driver?)

0103           16384 ram3

(driver?)

0104           16384 ram4

(driver?)

0105           16384 ram5

(driver?)

0106           16384 ram6

(driver?)

0107           16384 ram7

(driver?)

0108           16384 ram8

(driver?)

0109           16384 ram9

(driver?)

010a           16384 ram10

(driver?)

010b           16384 ram11

(driver?)

010c           16384 ram12

(driver?)

010d           16384 ram13

(driver?)

010e           16384 ram14

(driver?)

010f           16384 ram15

(driver?)

b300         3776512 mmcblk0

driver: mmcblk

b318             128 mmcblk0rpmb

(driver?)

b310           16384 mmcblk0boot1

(driver?)

b308           16384 mmcblk0boot0

(driver?)

No filesystem could mount root, tried:

nfs

 

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

 

I have also added the below lines in /etc/init.d/rcS file of the rootfs file system in the server.

  1. Mount -n -t nfs -o nolock,rsize=32768,wsize=32768,tcp 134.XX.X.XXX:/proj/nfs/rootfs/home/root /root
  2. Mount -n -t nfs -o nolock,rsize=32768,wsize=32768,tcp 134.XX.X.XXX:/proj/nfs/rootfs/ /mnt

 

I have also added the below lines in /etc/export of my NFS server( which is a VM):

  1. /proj/nfs 134.XX.0.0/24(rw,no_root_squash,async)
  2. /proj/nfs/rootfs 134.XX.0.0/24(rw,no_root_squash,async)

 

But I am still getting the above error.

 

The kernel is configured with below configs for nfs boot:

  1. CONFIG_NETWORK_FILESYSTEMS
  2. CONFIG_NFS_FS
  3. CONFIG_ROOT_NFS

 

The contents of the rootfs folder itself is the extracted part of rootfs.cpio built during the petalinux build process.

I used the “sudo pax -rvf rootfs.cpio” to extract it.

 

Please note my nfs server is in a VM.

If some extra configuration is needed in the VM for the same, do let me know.

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Visitor devarun@18
Visitor
49 Views
Registered: ‎10-12-2018

Re: NFS mount on ZC702 is not happening

Jump to solution

I found the solution, I had configured the ethernet port to phy address 3 by using dtsi file. But it seems nfs boot only binds to phy address 0. Addressing this, solved my issue.

0 Kudos
2 Replies
Scholar watari
Scholar
87 Views
Registered: ‎06-16-2013

Re: NFS mount on ZC702 is not happening

Jump to solution

Hi devarun@18 

 

Would you make sure your NFS server setting ?

 

I guess it seems network issue or firewall issue.

 

At least, NFS server on VM should go over gate way, in my experience...

 

Best regards,

0 Kudos
Highlighted
Visitor devarun@18
Visitor
50 Views
Registered: ‎10-12-2018

Re: NFS mount on ZC702 is not happening

Jump to solution

I found the solution, I had configured the ethernet port to phy address 3 by using dtsi file. But it seems nfs boot only binds to phy address 0. Addressing this, solved my issue.

0 Kudos