Network File System configuration - Revision history

JulienB: /* Timemouts in U-Boot */

2026-07-29T13:00:51Z

Timemouts in U-Boot

← Older revision		Revision as of 15:00, 29 July 2026
Line 243:		Line 243:

	===Timemouts in U-Boot===		===Timemouts in U-Boot===
	* If you think all your NFS server config is OK but still have Timeouts ("T") in U-Boot when using run nfsboot, then you can try this (tested on Ubuntu 22.04):		* If you think all your NFS server config is OK but still have Timeouts ("Loading: T T T T T T T T") in U-Boot when using ''run nfsboot'', then you can try this (tested on Ubuntu 22.04):

	<pre class"host">		<pre class"host">

2026-07-29T12:59:48Z

Kernel debug

@@ Line 240: / Line 240: @@
 <pre class="apf">
 # mount -t nfs -o vers=3,nolock 192.168.0.152:/nfsroot /mnt/nfs
 </pre>

2026-07-27T13:50:43Z

Portmap/RPCbind

@@ Line 220: / Line 220: @@
 <pre class="apf">
 mount -o port=2049,nolock,proto=tcp 192.168.0.2:/local/export /mnt/nfs/
 </pre>

2022-02-01T11:17:36Z

Troubleshooting

← Older revision		Revision as of 13:17, 1 February 2022
Line 207:		Line 207:
	</pre>		</pre>
	If ''portmap/rpcbind'' is not listed, then launch it manually or install it:		If ''portmap/rpcbind'' is not listed, then launch it manually or install it:
	<pre class="apf">		<pre class="apf"
	# /etc/init.d/S13portmap		# /etc/init.d/S13portmap
	</pre>		</pre>
Line 221:		Line 221:
	mount -o port=2049,nolock,proto=tcp 192.168.0.2:/local/export /mnt/nfs/		mount -o port=2049,nolock,proto=tcp 192.168.0.2:/local/export /mnt/nfs/
	</pre>		</pre>

			===Kernel debug===
			* If none of the above workarounds was successful -> no luck ! :-) You can still activate NFS debugging by recompiling your kernel with CONFIG_SUNRPC_DEBUG options and use ''setenv extrabootargs nfsrootdebug'' in U-Boot. And then you dig...

	==NFS Server under Windows==		==NFS Server under Windows==

2022-02-01T10:57:54Z

← Older revision		Revision as of 12:57, 1 February 2022
Line 131:		Line 131:
	# ls /mnt/nfs		# ls /mnt/nfs
	</pre>		</pre>

	When you have a problem, verify that the NFS server is running on the host:		When you have a problem, verify that the NFS server is running on the host:
	<pre class="host">		{\| border="1" cellpadding="5" cellspacing="0" summary="Status of NFS server depending on your distribution"
			\|- style="background:#efefef;"
			! '''On Fedora''' \|\| '''On Ubuntu/Kubuntu/debian''' \|\| '''On OpenSUSE''' \|\| '''On Gentoo'''
			\|-

			\| <pre class="host">
			$ /sbin/service nfs status
			</pre>

			\|\|<pre class="host">
	$ /etc/init.d/nfs-kernel-server status		$ /etc/init.d/nfs-kernel-server status
	</pre>		</pre>
	or		\|\|
	~~<pre class="host">~~
	~~$ /sbin/service nfs status~~		\|\|
	~~</pre>~~		\|}

	===Boot from NFS===		===Boot from NFS===

2017-07-19T16:01:46Z

Portmap

← Older revision		Revision as of 18:01, 19 July 2017
Line 190:		Line 190:
	* In that case, restart the NFS service on your Host (see [[Network_File_System_configuration#Restart_of_NFS_server\|above]]).		* In that case, restart the NFS service on your Host (see [[Network_File_System_configuration#Restart_of_NFS_server\|above]]).

	===Portmap===		===Portmap/RPCbind===
	* To successfully mount a NFS drive, ''portmap'' daemon should be running on your APF, if not, system will hang during some minutes when you launch the mount !!		* To successfully mount a NFS drive, ''portmap''/''rpcbind'' daemon should be running on your APF/OPOS, if not, system will hang during some minutes when you launch the mount !!
	To check if ''portmap'' is running, look at the running processes:		To check if ''portmap''/''rpcbind'' is running, look at the running processes:
	<pre class="apf">		<pre class="apf">
	# ps faux		# ps faux
	</pre>		</pre>
	If portmap is not listed, then launch it manually:		If ''portmap/rpcbind'' is not listed, then launch it manually or install it:
	<pre class="apf">		<pre class="apf">
	# /etc/init.d/S13portmap		# /etc/init.d/S13portmap
	</pre>		</pre>
			* Note: ''portmap'' is obsolete since 2017

	===Connection refused===		===Connection refused===

2017-06-20T06:49:46Z

NFS server on your development Host

← Older revision		Revision as of 08:49, 20 June 2017
Line 11:		Line 11:
	* On OpenSUSE:		* On OpenSUSE:
	$ sudo zypper install yast2-nfs-server		$ sudo zypper install yast2-nfs-server
	* On Gentoo:		* On Gentoo:
	# emerge -av nfs-utils		# emerge -av nfs-utils

			You can also take a look at the [https://wiki.gentoo.org/wiki/Nfs-utils gentoo wiki]
	===Configuration===		===Configuration===
	====/etc/exports====		====/etc/exports====

2017-06-20T06:39:18Z

NFS server on your development Host: Gentoo

← Older revision		Revision as of 08:39, 20 June 2017
Line 11:		Line 11:
	* On OpenSUSE:		* On OpenSUSE:
	$ sudo zypper install yast2-nfs-server		$ sudo zypper install yast2-nfs-server
			* On Gentoo:
			# emerge -av nfs-utils
	===Configuration===		===Configuration===
	====/etc/exports====		====/etc/exports====
Line 54:		Line 56:
	{\| border="1" cellpadding="5" cellspacing="0" summary="Restart of NFS server depending on your distribution"		{\| border="1" cellpadding="5" cellspacing="0" summary="Restart of NFS server depending on your distribution"
	\|- style="background:#efefef;"		\|- style="background:#efefef;"
	! '''On Fedora''' \|\| '''On Ubuntu/Kubuntu/debian''' \|\| '''On OpenSUSE'''		! '''On Fedora''' \|\| '''On Ubuntu/Kubuntu/debian''' \|\| '''On OpenSUSE''' \|\| '''On Gentoo'''
	\|-		\|-

Line 76:		Line 78:
	\|\| <pre class="host">		\|\| <pre class="host">
	# /etc/init.d/nfsserver restart		# /etc/init.d/nfsserver restart
			</pre>

			\|\| <pre class="host">
			# /etc/init.d/nfs restart
	</pre>		</pre>
	\|}		\|}

2017-03-01T16:49:23Z

Portmap

← Older revision		Revision as of 18:49, 1 March 2017
Line 183:		Line 183:

	===Portmap===		===Portmap===
	* To successfully mount a NFS drive, ''portmap'' daemon should be running on your APF, if not system will hang during some minutes when you launch the mount !!		* To successfully mount a NFS drive, ''portmap'' daemon should be running on your APF, if not, system will hang during some minutes when you launch the mount !!
	To check if ''portmap'' is running, look at the running processes:		To check if ''portmap'' is running, look at the running processes:
	<pre class="apf">		<pre class="apf">

2017-03-01T16:34:55Z

Restart of NFS server

← Older revision		Revision as of 18:34, 1 March 2017
Line 52:		Line 52:

	====Restart of NFS server====		====Restart of NFS server====
	* '''On Fedora:'''		{\| border="1" cellpadding="5" cellspacing="0" summary="Restart of NFS server depending on your distribution"
	<pre class="host">		\|- style="background:#efefef;"
			! '''On Fedora''' \|\| '''On Ubuntu/Kubuntu/debian''' \|\| '''On OpenSUSE'''
			\|-

			\|<pre class="host">
	# /sbin/service nfs restart		# /sbin/service nfs restart
	</pre>		</pre>
Line 65:		Line 69:
	</pre>		</pre>

	* '''On Ubuntu/Kubuntu/debian:'''		\|\| <pre class="host">
	<pre class="host">
	$ sudo /etc/init.d/nfs-kernel-server restart		$ sudo /etc/init.d/nfs-kernel-server restart
	</pre>		</pre>
	Next time you boot, you can check your NFS server status with:		Next time you boot, you can check your NFS server status with:
	System Settings->System services		''System Settings->System services''
			\|\| <pre class="host">
	* '''On OpenSUSE'''
	# /etc/init.d/nfsserver restart		# /etc/init.d/nfsserver restart
			</pre>
			\|}

	==NFS usage on your Armadeus board==		==NFS usage on your Armadeus board==