HA OS won't Initialize

Hi all, my installation has been working well for 18 months on an RPi4 B 4GB with an SD card, but it started to glitch this week so I’m moving to an SSD. I have the StarTech USB3 to SATA III 2.5" cable and a 240GB Patriot SSD. My power supply is a 3.5 amp Canakit. I’m getting this error from the HA OS configuration log,

22-08-24 21:13:25 INFO (SyncWorker_0) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/raspberrypi4-64-homeassistant:landingpage to ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.8.6
22-08-24 21:13:25 INFO (SyncWorker_0) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi4-64-homeassistant with tag 2022.8.6.
22-08-24 21:14:42 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.8.6: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2022.8.6&fromImage=ghcr.io%2Fhome-assistant%2Fraspberrypi4-64-homeassistant&platform=linux%2Farm64: Internal Server Error ("Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)")
22-08-24 21:14:42 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec

I have formatted/reformatted the drive and rebuilt the install using both the RPi flasher and Balena Etcher with the official 8.6 GitHub link. I checked the drive partitions created by RPi and Balena Etcher, they match exactly. Any ideas on how to fix this?

EDIT to add: I have a SanDisk 480GB external SSD that I made into a HAOS boot drive with Balena Etcher and I’m getting the same error from my RPi4.

I also used Raspbian Lite to ensure my EEPROM was updated to the latest stable version and double check that USB boot first was selected.

The issue is not likely SSD or USB or EEPROM.

Per the log - your Pi cannot get to internet so install failed.
So fix that first.

1 Like

I finally let it sit for a hour and a half and it decided to work, finally. The router DNS was already set to 1.1.1.1 and 8.8.8.8.