i have the same issue, after i installed Raspbian Stretch on the PXE-Server.
,vers=3 at the end of
nfsroot= parameter in
cmdline.txt fix that issue.
wc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.0.1:/srv/nfs/rpi-12345678-root,vers=3 rw rootwait ip=dhcp elevator=deadline
but it must be a bug or limitation of nfs mount ability of
because that PXE-Server is providing OS's for other x86 PC's as well, and those OS's are PXE booting and mounting nfsroot's without problems and without adding that additional
ubuntu-16.04.3, ubuntu-17.04, ubuntu-12-04.4, debian-live-9.1.0, raspberry pi jessie for x86 (2017-06-22), ...
i saw, all those OS's are using at least vers=3 to mount nfsroot - even that old and crusty ubuntu-12-04.4.
start.efi, or where ever the
nfsroot mount happens, should use vers=3 as minimum as well.
see here: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=191224 and also here: https://github.com/raspberrypi/documentation/issues/719
- Raspbian Jessie on the PXE-Server; RPi3 PXE network booting -> no problem;
- Raspbian Jessie to Stretch update + upgrade on the PXE-Server; RPi3 PXE network booting -> no problem;
- Raspbian Jessie to Stretch update + dist-upgrade on the PXE-Server; RPi3 not PXE network booting -> problem mounting nfsroot;
- Raspbian Stretch on the PXE-Server; RPi3 not PXE network booting -> problem mounting nfsroot;
PS.: my RPi3 is pxe network booting without any SD card. PPS.: my RPi-PXE-Server project
PPPS.: for the pxe client, i tried out all the boot files from master, stable and next brunch of https://github.com/raspberrypi/firmware all shows up that same behavior.