Hello everyone , im starting to use hidden WiFi with VPN on my router and i notice that StartOS was disconnected after reboot and I had this problem ( clock sync failure ). Requiring manual reconnection. After rebooting from StratOS GUI, the bootloader failed, and I had to force shutdown the server (physically using the power button). When I turned it back on, it took a long time to start up, despite having a quad-core processor, 16GB RAM, and an SSD.
After startup, I had to manually reconnect the WiFi
Boot Issues and Performance:
Why is my server taking a long time to boot despite having an SSD and decent hardware specs ?
Could the forced shutdown have caused bootloader corruption or delays in startup? How can I check and fix this?
What logs should I check to diagnose slow boot times? (e.g., systemd-analyze blame on Linux or Event Viewer on Windows)
WiFi and Network Issues:
Why does my hidden WiFi network disconnect after a reboot, requiring manual reconnection?
Could the “clock sync failure” be related to the WiFi issue or a deeper hardware/software problem?
How can I make sure my server automatically reconnects to a hidden WiFi network after reboot?
Hardware and BIOS/UEFI Settings:
Could a BIOS/UEFI setting (like “Fast Boot”) be causing the slow startup or the WiFi issue?
What other BIOS/UEFI settings should I check to improve boot time and network stability?
Thank you so much for the support and have a nice day !
The clock sync failure will show any time StartOS boots, and cannot connect to the time server. It does this every time. So this is directly related to the WiFi issue.
There may be a bug in the proprietary WiFi driver, and/or how it interfaces with our network stack. StartOS inherits a lot of hardware compatibility from it’s Debian base, but it’s not bug for bug compatible, and StartOS is not tested on every possible hardware configuration. Just the servers we sell. Wifi support is sparse at best. Generally one should avoid WiFi all together on a server. StartOS is meant to run headless, without a mouse, monitor, and keyboard. For best results, tuck your server away in a corner, within Ethernet connection range of your router/network switch, and administer it from another machine on the LAN.
As far as the slow boot issue, this could be related to the WiFi issue as well. So it might just go away, once you use an Ethernet cable. Otherwise, I’d be curious to take a look at your OS, and Kernel logs. You can find them under System.
Thank you very much, today I will try to do some tests by connecting it directly via ethernet and I will do some reboots. In case I encounter any problems I will send you the logs. I wish you a good day.