Cannot acces via web UI anymore, [Errno5] and configuration.yaml not found

Configuration
1

Hi guys,

I’m a bit panicking because my Home Assistant setup (Rasp Pi 4) seems to have a serious problem. First of all: I can’t access via web UI (http://homeassistant.local:8123). It’s stuck at the starting screen which says “Home Assistant is a Project by the Open Home Foundation”.

But I can access via Companion app which is now my only way to check logs and other things. I find a lot of troubling issues. For example, I’m not able to restart Home Assistant. Error message:

the system cannot restart because the configuration is not valid: Error loading /config/configuration.yaml: [Errno 5] I/O Error: ‘config/configuration.yaml’

I guess this might be the main issue here. Somehow the configuration.yaml seems to be gone? I also can’t access yaml files with Studio Code Server (it shows a blank page).

I searched the forum and found out, that Errno 5 usually relates to a backup error. This is also true, as the latest backups (System > Backups) failed. An hour ago 3 backups were listed here (saved on system) but when I tried to download them to my phone to be sure to keep them they weren’t found and now they aren’t shown anymore.

Furthermore, trying to access the Add-on tab shows a blank page with “Troubleshoot”-message. It tells me to check the Observer, restart the Host (I can’t) and check the system state (link leads to a blank browser page).

Also, every single automation has a warning in their details. It says:

The automation cannot be edited in the user interface, because it isn’t saved in automations.yaml or doesn’t have an ID.

I’m relatively new to Home Assistant and I don’t understand the error logs. I also don’t know where to start digging.

What did break the thing: I don’t know. Yesterday everything seemed fine, I worked on a few automations (web interface and Companion) and checked them hours later. I didn’t install any new Add-ons, services or integrations. Today I stumbled over all these errors.

I have backups on Google drive from Dec 3rd and before, but I have worked a lot on Home Assistant since then. Unfortunately I didn’t realize these daily updates stopped working.

Does someone has some advice?

System Information:

System Information

version | core-2025.12.2

– | –

installation_type | Home Assistant OS

dev | false

hassio | true

docker | true

container_arch | aarch64

user | root

virtualenv | false

python_version | 3.13.9

os_name | Linux

os_version | 6.12.47-haos-raspi

arch | aarch64

timezone | Europe/Berlin

config_dir | /config

Home Assistant Community Store

GitHub API | ok

– | –

GitHub Content | ok

GitHub Web | ok

HACS Data | ok

GitHub API Calls Remaining | 5000

Installed Version | 2.0.5

Stage | running

Available Repositories | 2488

Downloaded Repositories | 7

Home Assistant Cloud

logged_in | true

– | –

subscription_expiration | 1. Januar 2018 um 01:00

relayer_connected | false

relayer_region | null

remote_enabled | false

remote_connected | false

alexa_enabled | true

google_enabled | true

cloud_ice_servers_enabled | true

remote_server | null

certificate_status | null

instance_id | e4488def5d7d4fba977098c9d1c1b224

can_reach_cert_server | ok

can_reach_cloud_auth | ok

can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 16.3

– | –

update_channel | stable

supervisor_version | supervisor-2025.12.3

agent_version | 1.7.2

docker_version | 28.3.3

disk_total | 56.6 GB

disk_used | 22.3 GB

nameservers | 192.168.178.1

healthy | true

supported | true

host_connectivity | true

supervisor_connectivity | true

ntp_synchronized | true

virtualization |

board | rpi5-64

supervisor_api | ok

version_api | ok

installed_addons | Matter Server (8.1.1), Advanced SSH & Web Terminal (22.0.3), Studio Code Server (6.0.1), Cloudflared (7.0.1), Home Assistant Google Drive Backup (0.112.1), Mosquitto broker (6.5.2), eufy-security-ws (1.9.3), Govee to MQTT Bridge (2025.11.25-60a39bcc)

Dashboards

dashboards | 4

– | –

resources | 4

views | 5

mode | storage

Network Configuration

adapters | lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth18bfe6e (disabled), veth10a3e94 (disabled), veth149cedf (disabled), vethc088bcb (disabled), veth2a1f925 (disabled), vethc9d8ccb (disabled), veth37d89f4 (disabled), vetha11ccd4 (disabled), veth50d5b7e (disabled)

– | –

ipv4_addresses | lo (127.0.0.1/8), end0 (192.168.178.68/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth18bfe6e (), veth10a3e94 (), veth149cedf (), vethc088bcb (), veth2a1f925 (), vethc9d8ccb (), veth37d89f4 (), vetha11ccd4 (), veth50d5b7e ()

ipv6_addresses | lo (::1/128), end0 (fe80::657d:809d:c621:3626/64), hassio (fe80::c01e:b1ff:feb3:b56a/64), docker0 (fe80::9890:5eff:fe16:6f7a/64), veth18bfe6e (fe80::7403:35ff:fe89:61db/64), veth10a3e94 (fe80::3021:24ff:fe00:b75e/64), veth149cedf (fe80::98b3:91ff:fea0:60dd/64), vethc088bcb (fe80::d043:24ff:fe15:99b2/64), veth2a1f925 (fe80::5414:1bff:fe50:c543/64), vethc9d8ccb (fe80::bc20:d9ff:feed:2358/64), veth37d89f4 (fe80::f432:8ff:fe4a:8b31/64), vetha11ccd4 (fe80::825:aff:fec7:bea4/64), veth50d5b7e (fe80::9475:72ff:fe60:fe90/64)

announce_addresses | 192.168.178.68, fe80::657d:809d:c621:3626

Recorder

error | failed to load: unknown

– | –

Spotify

api_endpoint_reachable | ok

– | –

2

SD Card is the most likely, followed by power supply problems.

2 Likes
3

Thanks for your response! You think the SD Card might be defective? So I could copy the contents to another one and then it could work?

I checked again and I even use a Raspberry 5 with 8 GB of RAM. The power supply unit provides 27W and is labeled with “official” for Raspberry.

4

Probably no. If you have i/o error, meaning input output error while reading data from sd card, that could point out that you sd card is failing. If it can’t read data or cant read all data you will not be able to copy it to another sd card. but you can try.
If you can better use hard disk of your choice then sd card.

2 Likes
5

More likely write a new one from scratch and restore your backup. If the image is not good enough to boot, it won’t be good enough to clone either. Assuming the card is bad.

1 Like
6

Thanks for your help. I wasn’t aware that SD cards are such a poor choice for HA since I bought a starter kit and assumed that this is a good idea.

Now I did some research and ordered a M2 SSD which I hopefully get to work with my existing backup. Also I’m trying to retrieve data from the old SD card, maybe not everything from the past week is gone.

1 Like
7

I would think about getting it working with the better SD card, then look into adding an external SSD with a USB3 powered hub to keep the strain off the power supply then switching the boot to there.

1 Like
8

Home Assistant is back and my home works smart again. I picked a camera SD card and set up a fresh HA installation. After that I used the 10 days old Google backup to restore most settings. And then I spent some hours on rebuilding things I worked on over the last days.

It was some work but I’m happy there was a more or less fresh backup and I’ll migrate everything to the internal SSD once it arrives. Have to find out how to install HA on it though. I hope the PSU will provide enough power while running SD and SSD at the same time.

1 Like