Netboot client error for Raspberry Pi OS Full 64-bit on a RPi 4B

[mccap079]

Issue:

Clients unable to boot with Raspberry Pi OS Full 64-bit, getting this error on client boot:

mount: /boot: can't find in /etc/fstab.
sed: couldn't open temporary file /boot/sed6vZAgF: Read-only file system
sed: couldn't open temporary file /boot/sedPvle8J: Read-only file system
mount: /boot: mount point not mounted or bad option
cat: '/sys/block/*/lib/partition': No such file or directory
cat: /sys/block/loop0//partition: No such file or directory
fdisk: cannot open /dev/*: No such file or directory
cat: '/sys/block/*/size': No such file or directory
Error: Could not stat device /dev/* - No such file or directory.

Steps:

1. Installed PiServer on a RPi 4B running Bullseye (from source, based on readme instructions, to create an arm64 package build)
2. Setup another couple SD-cardless, Pi 4B's as clients to the PiServer, running Raspberry Pi OS Full 64-bit

• I can see the OS installed at /var/lib/piserver/os/Raspberry_Pi_OS_Full_(64-bit)-2022-09-22/
• I can see the boot files for each client at /var/lib/piserver/tftproot/<MAC_ADDR>/

3. Proxy DHCP server running

• In the PiServer GUI, I can see that the client Pi's are detected on the DHCP network

4. After PiServer setup wizard is complete, power cycle client Pi's
5. Client Pi's will flash the test rainbow texture then print the error message

Expected result:

Clients should netboot Raspberry_Pi_OS_Full_(64-bit)-2022-09-22 normally.

Raspberry Pi OS Lite (32-bit) works
Raspberry Pi OS Lite (64-bit) works
Raspberry Pi OS (64-bit) works

---

I followed this guide, except that I am using Bullseye not Stretch. I'm assuming no extra config should need to be done, like manually adding an fstab entry? Maybe deeper linux knowledge was assumed so I missed some implicit steps. Doesn't seem like a network issue.