HassOS Hanging on Boot: Stuck at "Wait Until Kernel Time Synchronized"

This happened again today.
Unifi network was reporting it as the right IP, but it wouldn’t resolve.

Running a ping to the HA address then activating the port with the NMCLI command and it popped right back up again.

Checking my email and I see that the Unifi Switch that my HA connects to updated this morning.
Even after a reboot of HA it didn’t come back until I ran the NMCLI commands

My questions:

  1. Did you successfully boot into bash ?
  2. Without a bash, how can you input command NMCLI ???

It looks to me it’s NEVER ending Wait Until Kernel Time Synchronized. Stuck there forever…

I’m booting home-assistant independently without ssh or virtual machine, it’s just a fresh rebooting, with HDMI connected…

Any solution so far? BTW, I flashed haos_rpi3-64-10.3.img.xz for my testing.

Hi, same problem for me. RPI5 with HassOS 12 installed on NVME drive. First start failed as yours.
Added a bunch of NTP servers to /etc/systemd/timesyncd.conf with vi (time.goole.com and time1.google.com). Restarted and everything worked fine.
I had the exactly same issue with an RPI3 with HassOS installed on an SD card at the first start.
I think that in my case my ISP or my router have no access to default HassOS NTP server cloudfare.

Hope that this can help someone.

Made my day. Thank you!

1 Like

Works like a charm, i was disable lan in bios, and get same error, thanks!

This fixed the problem for me. Here The vi version worked for me

Incase the link goes dead in the future.

ha > login
 
mkdir -p /mnt/boot/CONFIG # echo -e "[Time]\nNTP=10.20.30.40\nFallbackNTP=10.20.30.41" > /mnt/boot/CONFIG/timesyncd.conf

Replace 10.20.30.40 and 10.20.30.41 with your desired NTP servers.

Alternatively you can:


vi /mnt/boot/CONFIG/timesyncd.conf


i

[Time] NTP=10.20.30.40 FallbackNTP=10.20.30.41

escape

:w

:q

I = start editing (insert)
escape = stops editing(insert)
:w = save
:q = quit

Once /mnt/boot/CONFIG/timesyncd.conf has been created you can reboot the Host


reboot

The /mnt/boot/CONFIG folder is removed after reboot. This is normal, and your changes should persist future reboots.