6

I have a raspberry pi model b+ that I am attempting to boot with a root on an nfs share. The pi takes an ip address from dhcp, and makes request to my nfs server for the root share. The server reports this request in logs, but the pi hangs after printing its ip configuration. The last cmdline.txt I tried contained: root=/dev/nfs rw nfsroot=192.168.2.25:/srv/rpi-root-nfs,tcp ip=dhcp vers=3

/etc/exports on the nfs server contains: /srv/rpi-root-nfs 192.168.2.0/24(rw,sync,no_root_squash,no_all_squash,insecure)

Are there any problems with this configuration?

UPDATE (06-06-2016) -- took a picture of the boot logs with loglevel set to 7. The line [ 7.318013 ] ... rootpath= is odd, as rootpath should be set, according to the kernel line.

7.318013 rootpath is not set

  • 1
    Perhaps static IP addresses are more practical? – Darth Vader Jun 4 '16 at 14:50
  • 1
    I have tried using static IP addresses, the result is the same. – gnarly-line Jun 4 '16 at 15:12
  • Please check your steps. Looks like something is missing. Theoretically your configuration should work there is no any issues. Please see this thread for reference. I am not able to see the logs properly but you have compiled your linux kernel than make sure that linux kernel support is available over it. – Harshit Sep 28 '16 at 10:15
  • I have the same problem. Were you able to solve it? I’ve tried to add the kernel parameter nfsrootdebug, but it didn’t have any effect. – hfs Oct 10 '17 at 20:10
1

I had the same problem. For me the fix was to force NFS version 3, by appending v3 as option to nfsroot:

nfsroot=192.168.2.25:/srv/rpi-root-nfs,tcp,v3
  • I've removed the share since this question was posted and currently don't have a way to test, so I'll accept this answer if you're using the same Pi I was. Was this fix for a Pi B+? – gnarly-line Oct 12 '17 at 3:40
  • No, it’s for a Pi 3 B running Raspbian Stretch. I guess the kernel version is more important than the hardware. – hfs Oct 12 '17 at 8:41
0

First off thanks for asking this question. I did not realize this could be done so it was fun trying to get it to work.

I got it to work and here is how I did it.

  1. I created a folder to export on my NAS, mounted the Raspian Stretch Lite image and it's two partitions. I then copied the system ext4 partition contents to the NAS folder and the Boot partition contents to a fat32 partition on the boot medium (in this case a USB flash drive).

  2. I edited the /etc/fstab file commenting out the root mount line so it would not try to remount /.

  3. Since I had labeled the boot fat32 partition as BOOT, I changed the /boot line to: LABEL=BOOT /boot vfat defaults 0 2

  4. To the exports file on my NAS I added: /mnt/RPi 192.168.0.199(rw,sync,no_root_squash,insecure)

  5. I edited the cmdline.txt file in the boot partition and ended up with this line: wc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs rw nfsroot=192.168.0.99:/mnt/RPi,tcp ip=dhcp vers=3 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait splash

It booted without an error. Hope that helps.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.