darknao's stuff

To content | To menu | To search

Wednesday 14 March 2018

Net boot (PXE + iSCSI) with a RaspberryPi 3

I'll show you here how to boot and run your Raspberry Pi 3 without SD card.
I'm using a Synology NAS to host an iSCSI LUN which will be used as the root filesystem for the pi.
In order to mount this LUN, the pi will need a starting kernel & initrd image to get the network up, connect to the iSCSI target (the NAS) and mount the root filesystem.
This kernel & module will be provided by a PXE server (also running on that NAS).


Before going further, I'll assume you already have a PXE server up and running. In this tutorial, I use ISC-DHCPd server and tftp-hpa.
You'll also need a running install of Raspbian on your pi to do all the preparation.

Enable PXE Boot capabilities

Check if the usb_boot_mode is set in your OTP memory :

$ vcgencmd otp_dump | grep 17:

If the usb_boot_mode bit is set, the value should be 3020000a
If this is not the case, install the last firmware update (important, this will not work with the current stable firmware):

$ sudo rpi-update

Add this line to your config.txt to set the usb_boot_mode bit in the OTP memory:


Then reboot

Now, if you check the OTP again, you should get the wanted value

$ vcgencmd otp_dump | grep 17:

If everything is ok, remove the "program_usb_boot_mode" line from your config.txt

You can now check that the PXE boot mode is working by power cycling your pi, without SDcard and with a ethernet cable plugged in.
The ethernet leds should light up after a few seconds.

Put the SDcard back, and reboot.

LUN creation and configuration

In my case, the LUN will be created on a Synology NAS (DS413).
I'll not describe how to create a LUN, there is already plenty of tutorial on Google.
Just the basics:
You'll need a LUN (obviously) and a iSCSI Target with this new LUN mapped to it
To connect to this target, you'll need to provide the IQN of this target, the IP of the iSCSI server (the NAS in my case), and your authentication credentials, if any.

Pi iSCSI configuration

Install the open-iscsi service & utilities

$ sudo apt-get install open-iscsi

Start the iscsi service

$ sudo systemctl start open-iscsi

You can define your own initiator name in /etc/iscsi/initiatorname.iscsi or keep the generated one.


Discover all target available on your iSCSI server

$ sudo iscsiadm -m discovery -t sendtargets -p <IP_OF_YOUR_ISCSI_SERVER>


$ sudo iscsiadm -m discovery -t sendtargets -p,1 iqn.2000-01.com.synology:BlackSyno.PiTarget

You should find here your newly created target. Log into it

$ sudo iscsiadm -m node -l -T <TARGET_IQN> -p <IP_OF_YOUR_ISCSI_SERVER>


 $ sudo iscsiadm -m node -l -T iqn.2000-01.com.synology:BlackSyno.PiTarget -p
 Logging in to [iface: default, target: iqn.2000-01.com.synology:BlackSyno.PiTarget, portal:,3260] (multiple)
 Login to [iface: default, target: iqn.2000-01.com.synology:BlackSyno.PiTarget, portal:,3260] successful.

Check if your pi has detected your new drive

$ tail /var/log/messages or fdisk -l

In most of the case, your new disk should be named /dev/sda ex:

Nov  5 17:04:12 raspberrypi kernel: [ 2441.542921] sd 4:0:0:1: Attached scsi generic sg1 type 0
Nov  5 17:04:12 raspberrypi kernel: [ 2441.545681] sd 4:0:0:1: [sda] 25165824 512-byte logical blocks: (12.9 GB/12.0 GiB)
Nov  5 17:04:12 raspberrypi kernel: [ 2441.550756] sd 4:0:0:1: [sda] Write Protect is off
Nov  5 17:04:12 raspberrypi kernel: [ 2441.551927] sd 4:0:0:1: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Nov  5 17:04:12 raspberrypi kernel: [ 2441.587028] sd 4:0:0:1: [sda] Attached SCSI disk

In order to be able to connect to your iSCSI drive during the boot, you'll need to load an initrd image with the required module.
Creating an initrd image is quite simple on Raspbian

First, tell the initramfs tool to include the iscsi module by creating the required flag file

$ sudo touch /etc/iscsi/iscsi.initramfs

And create the initramfs image for you current kernel

$ sudo update-initramfs -v -k `uname -r` -c

Your new initrd can be found in /boot

$ ls -lrt /boot/init*
-rwxr-xr-x 1 root root 9937953 Nov  5 17:27 /boot/initrd.img-4.4.27-v7+

Before continuing on your PI, it's time to set your PXE server ready for the PI

PXE Configuration

I assume here you already have a PXE server running at your disposable.
On my NAS, I use ISC-DHCPd server and tftp-hpa
You can use whatever you want, but you must be able to set the Vendor-Option Option 43 in your DHCP server or the PI will never initiate the boot
You will need the MAC address of your pi (ip a), and its serial number (grep Serial /proc/cpuinfo)

On your PXE server, in /opt/etc/dhcpd.conf (for isc-dhcp), add the following paragraph

  host pi {
    hardware ethernet b8:27:eb:1e:57:f7;
    filename "";
    # Very important (Vendor-Option Option 43)
    option vendor-encapsulated-options "Raspberry Pi Boot   ";

If you have more than one raspberry (like, for a cluster) you can use a group instead :

  group {
    filename "";
    option vendor-encapsulated-options "Raspberry Pi Boot   ";

    host redpi {
      hardware ethernet b8:27:eb:45:53:f8;
    host bluepi {
      hardware ethernet b8:27:eb:ed:73:b9;
    host greenpi {
      hardware ethernet b8:27:eb:0b:56:29;
    host whitepi {
      hardware ethernet b8:27:eb:a5:b4:83;

On your TFTP server root, in /opt/tftpboot in my case, create a directory with your PI serial (strip all leading 0)

$ mkdir /opt/tftpboot/511e57f7

Retrieve all boot files from your PI to this new folder

$ scp -r pi@yourPi:/boot/* /tftpboot/511e57f7/

Put the bootcode.bin file at the root of your tftp server

$ cp /tftpboot/511e57f7/bootcode.bin /tftpboot/

Modify your config.txt (in your tftp server), and add the following line

initramfs <YOUR_INITRD_IMAGE> followkernel


initramfs initrd.img-4.4.27-v7+ followkernel

New system installation

You now need to install a raspbian (or any other distribution) on your new iSCSI drive
Two possibilities:
- Copy your current installation
- Deploy a new installation image

Copy your current installation (easier)

Format your new disk

$ sudo mkfs.ext4 /dev/sda

Get your new drive UUID, will be used in your cmdline.txt later

$ sudo blkid /dev/sda
/dev/sda: UUID="afb74bd9-1934-42d7-a7d6-289d2f3ba0d7" TYPE="ext4"

Now, mount your new disk

$ mount /dev/sda /mnt

And copy your current rasbian install (apt-get install rsync may be needed here)

$ sudo rsync -avhP --exclude /boot --exclude /proc --exclude /sys --exclude /dev --exclude /mnt / /mnt/

Create all system directories

$ sudo mkdir /mnt/{dev,proc,sys,boot,mnt}

Deploy a new installation image

Download your distro image on your PI
In my case, i'll use the raspbian lite image
You can use dd to copy the image in your new iSCSI drive:

$ sudo dd bs=4M if=/tmp/2016-09-23-raspbian-jessie-lite.img of=/dev/sdb

You'll need your new root partition UUID from your new drive, will be used in your cmdline.txt later

$ sudo blkid /dev/sdb2
/dev/sdb2: UUID="3598ef8e-09be-47ef-9d01-f24cf61dff1d" TYPE="ext4" PARTUUID="5a7089a1-02"

Mount your new installation

$ sudo mount /dev/sdb2 /mnt

Prepare the new system & chroot in it

sudo mount --bind /proc /mnt/proc
sudo mount --bind /dev /mnt/dev
sudo mount --bind /sys /mnt/sys
sudo mount --bind /run /mnt/run
sudo chroot /mnt

Refresh the APT cache, and install rpi-update

apt-get update
apt-get install rpi-update

Install the last firmware update on this new system (this is to get the same kernel modules level you have on your sd card)


Install the iscsi module

apt-get install open-iscsi

Create the initramfs iscsi flag file, for future initrd generation

touch /etc/iscsi/iscsi.initramfs

New system installation is complete

Final tuning

Since your root directory will be mounted during the initrd phase, you'll not need it in fstab, same for /boot
So, basically, remove everything sdcard related (/dev/mmcblk0p*) from your /mnt/etc/fstab
But, the update-initramfs command look into this file to get the FS type of your /, and include the related fsck command into the initrd (like fsck.ext4)
It's not mandatory, but you can add your newly created root FS at the begginning :

UUID=3598ef8e-09be-47ef-9d01-f24cf61dff1d       /       ext4    defaults        1       1

Your network interface will also be configured at boot time during the initrd phase, so you may want to disable the dhcp client for this card or you will get 2 addresses for a single interface
in /mnt/etc/dhcpcd.conf, add

denyinterfaces eth0

If you do that, you will also need to manually set your DNS, in /mnt/etc/resolvconf.conf


Now, you need to set all required parameters to connect to your iSCSI drive during the boot
For that, modify your cmdline.txt (on your tftp server), and add this ( keep everything on a single line )


If you use CHAP authentication on your iSCSI target, use ISCSI_USERNAME and ISCSI_PASSWORD variables

so your file should look like this

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 ip=::::superpi:eth0:dhcp root=UUID=3598ef8e-09be-47ef-9d01-f24cf61dff1d rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait qmap=fr ISCSI_INITIATOR=iqn.2016-11.org.raspberrypi:superpi ISCSI_TARGET_NAME=iqn.2000-01.com.synology:BlackSyno.PiTarget ISCSI_TARGET_IP= ISCSI_TARGET_PORT=3260 rw

Now, you can shutdown, remove the SDcard, and power your pi back on.

Additional stuff

Green led

The green led usually flash on SD card activity. Since we don't use it anymore, you can stop it from blinking.

Add this line to your config.txt:


Other triggers are available if you want (heartbeat is a nice alternative)

Disable ipv6

You can disable ipv6 if you don't need it.

in /etc/sysctl.conf :

# Disable IPv6
net.ipv6.conf.all.disable_ipv6 = 1

Then apply :

$ sudo sysctl -p

Resize your root partition

In case of a new installation, you may want to increase you root FS to take all your disk.
Use fdisk to do that (delete then recreate the partition using the same start sector)
Reboot, then resize2fs /

Manage kernel update

To keep the kernel up to date on your PXE server, you can mount it at boot on your pi.
in your /etc/fstab (replace with your PXE IP and Pi serial) :      /boot   nfs     nfsvers=3,nolock        0       0  

The bootcode.bin and start.elf are the first two files to be loaded by your PI. Since they are located in the root directory of your Tftp server, they'll be shared with all your Pi (if you have more than one).
Make sure to do some backup, you'll need it if the upgrade go south and your Pi can't boot anymore.

After that, you can update your distro with apt-get dist-upgrade

The kernel update **SHOULD** recreate your inirtd, but if not, you'll have to do it yourself :

sudo update-initramfs -v -k 4.4.26-v7+ -c

Don't forget to edit your config.txt with this new initrd img

reboot, and pray

More information:

Friday 9 October 2015

G27 Quick Release mod part III

Long time since my last post, got lazy apparently, so I'll do a quick update about the SRW-S1 part of this project (which is actually the easiest part, kind of).

So, now that the quick release hub is installed on the G27, I "just" need an adapter plate for the F1 rim.

I cut a simple piece of wood which can be placed on the back of the srw-s1, and sit between the paddles. 01_-_QR_adapter_plate_for_the_srw-s1.jpg

I've drilled 6 holes on it, but only 3 of them go through the srw-s1.
You have to be careful here to get the the wheel, adapter plate and quick release aligned!

You may also noticed two little things on this picture :
This wheel has 2 set of paddles: big analog ones which can be use for the clutch, and a smaller digital set for the shifter.
These paddles can be switched with each other with little modifications, so I decided to use the bigger ones as shifter (especially since I'll have no use of the analog paddles).

The second thing is the small hole in the center of the wood plate.
I'll use it later for the USB cable. I don't want any flying cable around the wheel, so the idea here is to get this cable go through the wheel shaft down to the back of the g27.
That will be the next post subject ;)

02_-_ZQrxsql.jpg Here is how it look from the other side.
As you can see, only 3 bolts go through the wheel because of the lack of space.

Fitting test: 05_-_SRW-S1_fitting_test.jpg Seems good!

The SRW-S1 has not been made with FFB in mind, and the handle may not survive long to this kind of structural constraint.
I've read that using epoxy glue can help to fortify the fixation points of the handles, I hope this will be enough. 09_-_gTaTtjR.jpg

One issue I have now, is the 3 dials takes a lot more space than I expected, and doesn't fit anymore in the case with the 2 bolts behind them...
So for now, I got them removed until I find a workaround about this.

Anyway, I can reassemble everything, and try this baby :) 15_-_srw-s1_on_G27.jpg


Remain the USB connection to take care about, but I saved it for next time :)

That's all for today!

Wednesday 12 August 2015

G27 Quick Release mod part II

Previously, in Part I: The idea here was to mount a F1 wheel (SRW-S1 from SteelSeries) on the G27 with a quick release system, to be able to easily switch between the stock rim and the new one. All that trying to keep the cost low enough.

So, now that i have the quick release hub and the adapter plate from Ignition-Controls, i can see what i can do. I was not sure if the adapter plate was enough by itself to fit on the g27 and the quick release, but luckily, it was. No need of the base plate. G27QR_test_fit_front I removed the inside part of the QR in order to pull some cables for buttons or other stuff later.

G27QR_test_fit_side The QR will sit on bolts head for better holding, but I'll need to add some spacers if i want to do that correctly (right now, there is a little play between the plate and the QR).

I can now mount any standard wheel to the G27 base, except, the g27 one is not one of them. So, If I want to mount it, I'll need another adapter plate.
Two solutions here: either buy another plate like the one I use for the wheel base, or made my own.
I choose the second option to keep the cost low, and since I already had a spare plywood plate laying around.

I used the QR plate as template, and make a copy of it. G27QR_adapter_plate_front

Does it fit? G27QR_adapter_plate_front_mounted All good!

Buttons cables will go through the center hole, and be connected to the original PCB. G27QR_adapter_plate_back_mounted Except, connecting them by hand every time will be a pain in the ass, and kind of defeat the purpose of the quick release :p
I'll have to find a better way to handle the connection between the wheel (any wheel actually) and the G27 base (We'll see that on a next part).

Forget about buttons for now, let's try this first! G27QR_test_fit_2_front Looks good!

G27QR_test_fit_2_side I used spacers on the base plate this time, and there is no noticeable play anymore. Solid and sturdy.

Only one thing: The shifter paddles are a little bit far away from the wheel now, and even with my big hands, it's not easy to reach them. But I'll take care of that later.

Now that the G27 rim part is almost complete, it's time to work on the F1 wheel, cause, you know, that was the primary goal after all ;)

Thursday 6 August 2015

G27 Quick Release mod part I


Some times ago, i started to drive the McLarren MP4-12C on iRacing, and although the stock G27 rim is a good one, i wanted something more immersive, like F1 looking rim.

MP4-12C wheel

Since the G27 doesn't allow standard rim changing like the Thrustmaster or Fanatec base wheel, i also needed to find a way to fix the new rim, but not in a permanent way since i still wanted to use the stock rim eventually.

After a few googling, i found this : http://simulaje.blogspot.com.es Simulaje QR

This is a really well made quick release system for the G27, and it can come with an adapter plate for the SteelSeries SRW-S1 (which is a really affordable F1 rim btw).
They also sells a few custom rims, with a lot of buttons, encoders, SLI display ... Most of them are replica of real car wheel like the HPD-ARX or the MP4-12C.

Unfortunately, this system is a little bit expensive (more than 200€ for the full QR system + the connector and adapter plate for the SRW-S1 + shipping)
That's almost the cost of a brand new G27 (and i still need to buy the F1 rim afterward).

So I've tried to find a cheaper way.
Since i know you can easily buy (or made) some g27 adapter plate for standard 6 holes steering wheel, you surely can use this plate for a standard quick release system instead.
Figured out you can find really cheap quick release hub on ebay (a little bit more than 10$, including shipping) like this one: slim quick release hub Took 2 of them.

Now, for the adapter plate, there is several sellers that offer this kind of product. Among them, ignitioncontrols have an add-on plate that fit this exact same quick release hub. ic_qr_plate.PNG

I guess this is supposed to work with the G27 Base Plate they also sell, but since it add another 49$ to the bill, I've choose to buy it alone and see if i can use it as it.

I now have everything to mount a QR hub on the G27 for less than 50$.
Except the QR hub is only compatible with standard steering wheel mount, which is not the case of the g27 wheel (nor the SRW-S1), so I'll have to craft my own adapter plate (See part II)