Raspberry PI: network boot explained - Cronologia

MiB: /* Phase 1: DHCP */

2018-01-24T19:05:23Z

Phase 1: DHCP

MiB: /* Phase 1: DHCP */

2018-01-24T19:01:37Z

Phase 1: DHCP

Renzo il 08:40, 15 gen 2018

2018-01-15T08:40:05Z

Renzo il 11:44, 10 gen 2018

2018-01-10T11:44:58Z

Renzo: /* Still to be tested */

2018-01-10T11:37:23Z

Still to be tested

Renzo: /* Final Remarks */

2018-01-10T11:37:07Z

Final Remarks

Renzo: /* Still to be tested */

2018-01-10T11:26:59Z

Still to be tested

Renzo: /* Final Remarks */

2018-01-10T11:26:14Z

Final Remarks

Renzo: /* Phase 3: NFS */

2018-01-10T11:08:10Z

Phase 3: NFS

Renzo: /* Phase 3: NFS */

2018-01-10T11:02:15Z

Phase 3: NFS

@@ Riga 31: / Riga 31: @@
 [[File:bootrpidhcp.jpg]]
-The screenshot shows the DHCP request. The MAC address of my Raspberry PI is: be:27:eb:15:e4:ef
+The screenshot shows the DHCP request. The MAC address of my Raspberry PI is: b8:27:eb:15:e4:ef
 The next step is to configure a DHCP server to provide the Raspberry PI with its own IP address.
@@ Riga 48: / Riga 48: @@
 The option ''pxe-service'' notifies the Raspberry pi that this server supports the net boot.
-Restart dnsmaq:
+Restart dnsmasq:
 <pre>
 sudo systemctl restart dnsmasq.service

@@ Riga 37: / Riga 37: @@
 In this test I'll use DNSmasq.
-This is the configuration to assign the IP address 192.168.1.100 to the MAC be:27:eb:15:e4:ef on the interface eth0.
+This is the configuration to assign the IP address 192.168.1.100 to the MAC b8:27:eb:15:e4:ef on the interface eth0.
 <pre>interface=enx0050b6175c07
 bind-interfaces
 dhcp-range=192.168.1.100,192.168.1.100,255.255.255.0,1h
-dhcp-host=be:27:eb:15:e4:ef,192.168.1.100,1h
+dhcp-host=b8:27:eb:15:e4:ef,192.168.1.100,1h
 pxe-service=0,"Raspberry Pi Boot"
 log-dhcp

@@ Riga 5: / Riga 5: @@
 This example-tutorial uses a Raspberry PI as a boot client and a Debian server (maybe another Raspberry PI running Raspian).
-The tools needed on the server are dnsmasq and nfs-kernel-server. The packets can be loaded in this way:
+The tools needed on the server are dnsmasq and nfs-kernel-server. The required packets can be loaded in this way:
 <pre>
 # apt-get install dnsmasq nfs-kernel-server
@@ Riga 14: / Riga 14: @@
 (although I have not tested it yet).
-The SD card need to contain one FAT partition and inside it one file: bootcode.bin.
+The SD card needs to contain one FAT partition and inside it one file: bootcode.bin.
 The latest version of bootcode.bin can be dowloaded from [https://github.com/raspberrypi/firmware/tree/master/boot here]. It is a 50K file so any size of SD Card is okay. Even a partially damaged SD card or a fake SD card can be used for this purpose. This file will be read at boot time and never modified so the card should not be further damaged.
@@ Riga 62: / Riga 62: @@
 [[File:bootrpidhcpreply.jpg]]
-Packet #39 is the DHCP reply whish assigns the address to the Raspberry PI, then packet #42 tries to load the file "6c15e4ef/start.elf" via TFTP...
+Packet #39 is the DHCP reply whih assigns the address to the Raspberry PI, then packet #42 tries to load the file "6c15e4ef/start.elf" via TFTP...
 We are ready for the second phase.
@@ Riga 106: / Riga 106: @@
 </pre>
-The IP address and path of the directory exported as root partition need to be change to suit your environment.
+The IP address and path of the directory exported as root partition need to be changed to suit your environment.
 Restart dnsmasq,
@@ Riga 115: / Riga 115: @@
 If you have a monitor connected to the Raspberry PI now if everything is working properly it boots and.... fails.
-It should terminate (after a while) with Kernel Panic complying that it is unable to mount the root partition.
+It should terminate (after a while) with Kernel Panic complaining that it is unable to mount the root partition.
 It is correct as the third phase is still missing.

@@ Riga 5: / Riga 5: @@
 This example-tutorial uses a Raspberry PI as a boot client and a Debian server (maybe another Raspberry PI running Raspian).
-The tool needed on the server are dnsmasq and nfs-kernel-server. The packets can be loaded in this way:
+The tools needed on the server are dnsmasq and nfs-kernel-server. The packets can be loaded in this way:
 <pre>
 # apt-get install dnsmasq nfs-kernel-server

← Versione meno recente		Versione delle 11:37, 10 gen 2018
Riga 195:		Riga 195:

	* RPI 3 booting without any SD card		* RPI 3 booting without any SD card
−	* ssh enable on headless net-booted RPIs

@@ Riga 172: / Riga 172: @@
 <pre>
 sudo exportfs -a
 </pre>

← Versione meno recente		Versione delle 11:26, 10 gen 2018
Riga 187:		Riga 187:
	* RPI 3 booting without any SD card		* RPI 3 booting without any SD card
	* ssh enable on headless net-booted RPIs		* ssh enable on headless net-booted RPIs
−	* mount the boot partition on nfs to permit firmware updates from the client.

← Versione meno recente		Versione delle 11:26, 10 gen 2018
Riga 152:		Riga 152:

	Now power cycle the Raspberry PI and the boot process should be complete up to the login prompt.		Now power cycle the Raspberry PI and the boot process should be complete up to the login prompt.
		+
		+	== Mount /boot via NFS ==
		+
		+	This is an optional extra feature. It is possible to mount via NSF the boot partition (the one whose file have been loaded via TFTP at boot time).
		+
		+	This enhancement permits to the client to manage and update its own kernel and configuration as if it where a standard Raspberry PI using its own SD card.
		+
		+	In order to reach this goal one line must be added to /etc/exports:
		+	<pre>
		+	/tftpboot/6c15e4ef 192.168.1.100/255.255.255.255(rw,sync,insecure,no_subtree_check,no_root_squash)
		+	</pre>
		+
		+	and a line in the client's fstab ''/srv/nfs/raspianroot/etc/fstab'':
		+	<pre>
		+	192.168.1.1:/tftpboot/6c15e4ef /boot nfs4 defaults 0 0
		+	</pre>
		+
		+	When /etc/exports is updated, exportfs is needed to inform the NFS server of the new configuration:
		+	<pre>
		+	sudo exportfs -a
		+	</pre>

	== Final Remarks ==		== Final Remarks ==

@@ Riga 147: / Riga 147: @@
 restart the nfs server:
 <pre>
 sudo systemctl restart nfs-kernel-server.service
 </pre>

← Versione meno recente		Versione delle 11:02, 10 gen 2018
Riga 151:		Riga 151:

	Now power cycle the Raspberry PI and the boot process should be complete up to the login prompt.		Now power cycle the Raspberry PI and the boot process should be complete up to the login prompt.
		+
		+	== Final Remarks ==
		+
		+	If something is not working properly, the main debug tools are wireshark and
		+	<var>
		+	tail -f /var/log/syslog
		+	</var>
		+
		+	In fact the analysis of the network traffic and the log file on the server can show what is going wrong.
		+
		+	== Still to be tested ==
		+
		+	* RPI 3 booting without any SD card
		+	* ssh enable on headless net-booted RPIs
		+	* mount the boot partition on nfs to permit firmware updates from the client.