Failure of initial setup on R-Pi4 with USB NVMe due to Time / Date issue

I’ve been using my R-Pi4 with HAOS for years now. It’s always used the SD card and I wanted a more robust solution, so I decided to get an NVMe SSD and a kit for it. After much frustration and finding that I needed a 5A power cable, I finally got to the point where HA is trying to install, but the time / date is showing May 27th 2024 and thus can’t download anything due to certificates being too new to be trusted. I have a keyboard / monitor plugged in, but I can’t find a way to set the time and date. I don’t have SSH enabled and I can’t get into the GUI because it hasn’t fully downloaded yet. NTP isn’t blocked and working fine as far as I can tell. Network is functional and I’m able to browse to the HAOS Pi. Can anyone assist in telling me how I can get the date updated?

Logs are below:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
[21:49:24] INFO: Using udev information from host
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
[21:49:24] INFO: Starting local supervisor watchdog…
s6-rc: info: service legacy-services successfully started
2024-05-27 21:49:29.362 INFO (MainThread) [main] Initializing Supervisor setup
2024-05-27 21:49:29.389 INFO (MainThread) [supervisor.docker.network] Can’t find Supervisor network, creating a new network
2024-05-27 21:49:29.734 INFO (MainThread) [supervisor.bootstrap] Setting up coresys for machine: raspberrypi4-64
2024-05-27 21:49:29.747 INFO (MainThread) [supervisor.docker.supervisor] Attaching to Supervisor Package aarch64-hassio-supervisor · GitHub with version 2024.12.3
2024-05-27 21:49:29.748 INFO (MainThread) [supervisor.docker.supervisor] Connecting Supervisor to home assistant OS-network
2024-05-27 21:49:29.945 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state initialize
2024-05-27 21:49:29.949 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2024-05-27 21:49:29.950 INFO (MainThread) [main] Setting up Supervisor
2024-05-27 21:49:30.299 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2
2024-05-27 21:49:30.414 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor
2024-05-27 21:49:30.418 INFO (MainThread) [supervisor.dbus.manager] Connected to system D-Bus.
2024-05-27 21:49:30.419 INFO (MainThread) [supervisor.dbus.agent] Load dbus interface io.hass.os
2024-05-27 21:49:30.420 INFO (MainThread) [supervisor.dbus.hostname] Load dbus interface org.freedesktop.hostname1
2024-05-27 21:49:30.422 INFO (MainThread) [supervisor.dbus.logind] Load dbus interface org.freedesktop.login1
2024-05-27 21:49:30.423 INFO (MainThread) [supervisor.dbus.network] Load dbus interface org.freedesktop.NetworkManager
2024-05-27 21:49:30.424 INFO (MainThread) [supervisor.dbus.rauc] Load dbus interface de.pengutronix.rauc
2024-05-27 21:49:30.425 INFO (MainThread) [supervisor.dbus.resolved] Load dbus interface org.freedesktop.resolve1
2024-05-27 21:49:30.425 INFO (MainThread) [supervisor.dbus.systemd] Load dbus interface org.freedesktop.systemd1
2024-05-27 21:49:30.426 INFO (MainThread) [supervisor.dbus.timedate] Load dbus interface org.freedesktop.timedate1
2024-05-27 21:49:30.828 INFO (MainThread) [supervisor.host.services] Updating service information
2024-05-27 21:49:30.838 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
2024-05-27 21:49:30.844 WARNING (SyncWorker_0) [supervisor.host.sound] Can’t update PulseAudio data: Failed to connect to pulseaudio server
2024-05-27 21:49:31.042 INFO (MainThread) [supervisor.host.network] Updating local network information
2024-05-27 21:49:31.222 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {‘home assistant OS-supervisor’}
2024-05-27 21:49:31.565 WARNING (MainThread) [supervisor.utils.whoami] Whoami service failed with SSL verification: Cannot connect to host services.home-assistant.io:443 ssl:True [SSLCertVerificationError: (1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1000)’)]
2024-05-27 21:49:31.565 INFO (MainThread) [supervisor.core] Whoami service SSL error
2024-05-27 17:49:31.675 WARNING (MainThread) [supervisor.core] System time/date shift over more than 3 days found!
2024-05-27 17:49:31.676 INFO (MainThread) [supervisor.host.control] Setting new host datetime: 2025-03-06T20:05:01+00:00
2024-05-27 17:49:31.687 CRITICAL (MainThread) [supervisor.core] Fatal error happening on load Task <coroutine object Core._adjust_system_datetime at 0x7f78c676a0>: Automatic time synchronization is enabled
2024-05-27 17:49:31.696 INFO (MainThread) [supervisor.docker.monitor] Started docker events monitor
2024-05-27 17:49:31.697 WARNING (MainThread) [supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection

HAOS will contact time servers on the internet to set the time and date, but something seems to go wrong.

I am not sure what the error says here, other than it looks like the error is not with getting the time of the internet, but instead actually setting the clock on the device.

Thanks Wally, I agree. The R-Pi doesn’t have a clock on it, so I’m not sure what could be wrong.

I can say that I purchased (unknowingly at the time) an undocumented expansion board (Amazon.com: GeeekPi M.2 NVME SSD Storage Expansion Board for Raspberry Pi 4, Only Support M.2 NVME SSD (Pi Board or M.2 NVME SSD NOT Included) : Electronics). I didn’t think to look at the huge thread of people having trouble with different kinds before I ordered. I figured anything that worked with my version of the Pi would be fine.

I doubt it has anything to do with it, since it’s able to boot and is doing things, but I figured it might be worth a mention. No idea why it can’t set the date correctly. To be clear, I have rebooted several times and re-installed the HAOS via the Pi Imaging tool probably 3 or 4 times now. I’m able to browse the SSD when connecting to my windows machine, so I don’t think anything is wrong with it and I just ran Pi OS on an SD card just last night before I got this 5amp power adapter that could finally properly power this thing. I just wish I could figure out a way in the CLI to update / refresh NTP or manually configure the time, but I haven’t found any useful information in google searches or the documentation yet.

Add a monitor and a keyboard directly to the RPi.
You should get a prompt then.
If it is a HA prompt, then the “login” command should give you OS access.

I have it sitting here on my desk and connected to one of my monitors. The problem is I don’t know what commands that I can enter to be able to update the date / time…

type login.

Then try this:

Holy crap, I just needed to type “login” to make changes? :man_facepalming:

Anyway, I got in, but it seems that I still can’t change anything unfortunately. Automatic time is turned on, can’t be turned off and I can’t set it manually due to that.

Time appears to be fine on the NTP server that the Pi has configured:

However, the Pi is coming up with something way off and I can’t change it. Can’t elevate with Sudo or su, so…?

You should already be root, so elevation with sudo/su is not necessary.

Can the date command be used?

Holy crap, maybe?

It’s doing stuff! lol

Thank you so much! I have no idea if it will eventually figure out the date properly or not, but I’m hoping that now that it trusts hosts on the internet, it should be able to figure itself out and will persist! Much appreciate your assistance! I have a little Linux knowledge but I’m rusty and I think you just saved my install. Much appreciated!

Well, if it happens again, then you know how to fix it now. :slight_smile:

Absolutely! Hopefully it helps someone else in the future as well :stuck_out_tongue:

Looks like I’m back on track and should be able to restore one of my previous backups. Thanks again!

Well, it’s incredibly faster now with the new drive, and I guess I can add my SSD Expansion board to the “working list” in the long thread now. Thanks again @WallyR, I owe ya a beer or 10!

I do not like beers that much, but I would love if you will pass it on and help others here. :wink:

2 Likes