The Industrial Raspberry Pi Forum

We've noticed that the revPI core sometimes doesn't startup fully after a "sudo reboot".
It doesn't happen often - a rough guess: 1/50.
When it happens the only solution seems to be to power cycle the device. The system never fails to start after a Power cycle.

After a failed reboot-start, the device is typically listed in a network discovery but with limited services, no port 80, no SSH and no applications.
Questions:
1. Can you elaborate what is the difference between a power cycle start and a reboot?
2. How can we troubleshoot this issue?
3. is there an alternative method to 'reboot' ?

This sounds somehow weird and we never ever experienced such a behaviour. Can you definitly elimiate that this is caused by your network? Are you running on DHCP? If you experience such a failed boot could you try recovering the services by unplugging and replugging the Ethernet connection? Could you possibly loose your connection to teh switch or whatever is the closest device connected? Or are you connecting directly a PC running a DHCP server? Could this DHCP server behave different when cold starting the RevPi instead of rebooting it by reboot command?

Thanks for the reply - helpful information. I will test to change the timing during startup, maybe delay some stuff.