ggRock Client Machine boot stuck on "Nothing to boot: No such file or directory"
The following error appears on bootup:
Nothing to boot: No such file or directory (http://ipxe.org/2d03e13b)
No more network devices
No bootable device.
Additional error messages may include:
"Operation not supported"
"The socket is not connected"
Access the ggRock server console (Debian Control Panel) via https://yourserver:9090/ or via SSH, or a directly at a keyboard/mouse/monitor connected to the server.
Log into the root account, or any other administrative account present on the server.
View iptables rules using "iptables -S" command. The stock configuration should have only three entries allowing all traffic.
4. If any iptables other than the above appear, please utilize the "iptables -F" command to delete all rules in all chains, then utilize the "iptables -S" command to confirm the output is as displayed below.
5. Attempt booting clients again.
Only proceed past step 5 if it is discovered that the iptables rules revert on reboot and the issue recurs.
6. Install the iptables-persistent package to keep the iptables settings on reboot.
7. Optionally, save current IPv4 rules when prompted.
7. Once the package is installed, restore iptables to its stock configuration as above, then issue the following command to permanently save settings:
iptables-save > /etc/iptables/rules.v4
8. Attempt booting clients again.
Cisco switches have a security feature related to DHCP (DHCP snooping). Your network administrator may need to mark the switch port that your ggRock server is connected to as trusted in order for the server to receive DHCP packets.
Refer to the following Cisco support article for more details: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/4_1/nx-os/security/configuration/guide/sec_nx-os-cfg/sec_dhcpsnoop.html
Iptables rules should not block DHCP-related packets (including broadcast) in order for ggRock proxy DHCP to be able to reply.