Custom OS boot issue

[yrjoseppa]

I've installed PiServer on two PCs: the 1st one runs Raspbian for PC (PiServer preinstalled), the 2nd one runs Debian9 (PiServer manually installed with additional dependencies).

When booting the client (Raspberry Pi3+) everything goes fine with the Raspbian PC, but when trying the same with the Debian9 (with the same custom OS file) the boot stops after notifying the IP settings got from DHCP (PiServer as a standalone DHCP, fixed IP 192.168.9.1/24 with client range .50->.150, only PiServer and the clinets on this "closed" LAN), and after a while there is a kernel panic (cannot access rootfs). BUT, if I make a clone of that custom OS, boot goes fine with that clone!

There is no problem at all with the official Raspian Lite, Raspbian or Raspbian full (vers 2018-04-08), however.

Is this PiServer issue?

[maxnet]

Does "ls -ld /var/lib/piserver/os" show any differences in the file permissions of the folder that has your custom OS and the clone of it? No special characters in the name of the folder?

"cat /var/lib/piserver/os/name-of-your-os/boot/cmdline.txt" does show the right server IP in the nfsroot parameter? If not, run "sudo piserver --update-ip" or change any setting in the settings tab of the piserver GUI.