Mounting NFS in Ubuntu (arm6410 Development Board)

You have encountered problems with mounting NFS file systems. I have burned a Linux system, and I have burned it down for less than 10 times with one click and USB! : L (I am also a newbie) I finally mounted it successfully last night. I will share with you how I mounted it successfully and some problems and precautions. It is expected to help those who have not been mounted successfully. Before mounting, check whether the following hardware devices are connected: 1. Connect the power cord 2. Connect the Development Board COM0 to PC 3. Connect the Development Board to PC with the USB cable 4. Plug in the network cable! Where

You have encountered problems with mounting NFS file systems. I have burned a Linux system, and I have burned it down for less than 10 times with one click and USB! : L (I am also a newbie)
After the mounting was successful last night, I will share with you how I mounted it successfully and some problems and precautions. It is expected to help those who have not been mounted successfully.
Before mounting, check whether the following hardware devices are connected:
1. Power Cord insertion
2. Connect the Development Board COM0 and PC with a serial line
3. USB cable connection Development Board and PC
4. Plug in the network cable!
The most easy to ignore is that the network cable is not plugged in, leading to problems like this that have never been solved.
Rpcbind: server x. x not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
Root-NFS: Server returned error-5 while mounting/home/glorin/sharetmp/filesys
To address this problem, note that except for the above network cable, the Host IP address (My Ubuntu IP address in the Virtual Machine) is not the same as the IP address of the Development Board.

CIDR blocks.
Solution 1. Change the Host IP address; 2. Change the IP address of the Development Board.
How can I know the IP address of the Development Board? I am a cainiao and didn't figure it out at first, so I thought it was just when setting the uboo startup parameter (that is, setenv bootargs ......).

You can set the IP address of the Development Board to be in the same network segment as the host IP address. It is actually wrong!
Correctly view the IP address on your development board. After setting the uboot startup parameter, use printenv to display the previous lines before setting the uboot parameter.
Ipaddress = x. x
Serverip = x. x
......
Here, the ipaddress is the real IP address on your development board. Even if you change it in setenv, It is not changed! You will find that the two ip addresses are in the same CIDR block.
Okay. This is the two ip addresses you want to set. In this case, change the ip address. (You do not need to modify the modified version)
How to change the Host IP Address:
$ Sudo vim etc/network/interfaces
Then set:
Auto lo
Iface lo inet loopback
Auto eth0
Iface eth0 inet static
Address 192.168.1.20 (for details, please write the IP address in the same network segment as ipaddress, or simply write the IP address in serverip)
Netmask 255.255.255.0
Gateway 192.168.1.1 (for details, please know how to set this)
After modification, restart the Network Configuration:
Sudo/etc/init. d/networking restart
Make sure the settings are correct. For ubuntu users, modify/etc/NetworkManager/nm-system-settings.conf
[Main]
Plugins = ifupdown, keyfile
[Ifupdown]
Managed = false
Change managed = ture to false.
Run sudo/etc/init. d/network-manager restart and reconfigure it. (For DNS, set sudo/etc/resolv. conf)
So far, the Host IP address is set.
Or you don't want to modify the Host IP address, so I still want to access the Internet. This has little to do with it. After successfully mounting and burning the file system, you can change it back.
Well, change the IP address on the Development Board. You can first enter the Development Board environment.