I am pretty new to Home Assistant - I started migrating from HomeKit a few months ago. After upgrading to 2022.5, I can’t see my config files.
My devices all seem fine - I can see and control things on the dashboard. But I can’t see where my configuration.yaml and other files are. File editor and Studio Code Server act like the config folder is empty, and sure enough, here’s what I see when I ssh in:
➜ ~ pwd
/root
➜ ~ cd config
➜ config ls -la
total 0
➜ config
Here’s what the ‘about’ screen shows:
Home Assistant Core 2022.5.4
Home Assistant Supervisor 2022.05.1
Home Assistant OS 7.6
Kernel version 5.10.103-v8
Agent version 1.2.1
Path to configuration.yaml: /config
(Some back story. Last week I tried updating from 2022.2. I updated Mosquitto at the same time, which broke some MQTT integrations I have. So I restored a backup – at least I think I did. So possibly things are in a wonky state?)
Did you resolve this? I also restored from a backup recently and just noticed that my /config folder is empty. I’m running the latest of everything (Core is 2022.5.5).
My issue is resolved, at least for now. I looked at the console and saw some “Out of memory” errors. Then I noticed that HA stopped responding altogether. A reboot fixed it and now I can see the files in the /config directory.
restored partial backup from latest core update, backup actually contains the config folder but after restarting nothing changed regarding local config folder.
daniels-MBP:~ daniel$ ssh homeassistant.local
| | | | /\ (_) | | | |
| |__| | ___ _ __ ___ ___ / \ ___ ___ _ ___| |_ __ _ _ __ | |_
| __ |/ _ \| '_ \ _ \ / _ \ / /\ \ / __/ __| / __| __/ _\ | '_ \| __|
| | | | (_) | | | | | | __/ / ____ \\__ \__ \ \__ \ || (_| | | | | |_
|_| |_|\___/|_| |_| |_|\___| /_/ \_\___/___/_|___/\__\__,_|_| |_|\__|
Welcome to the Home Assistant command line.
System information
IPv4 addresses for eth0: 192.168.17.40/24
IPv4 addresses for wlan0:
IPv4 addresses for enp1s0u1u2: 10.30.0.100/24
OS Version: Home Assistant OS 8.2
Home Assistant Core: 2022.6.6
Home Assistant URL: http://homeassistant.local:8123
Observer URL: http://homeassistant.local:4357
➜ ~ ll
total 0
lrwxrwxrwx 1 root root 7 Jun 16 16:24 addons -> /addons
lrwxrwxrwx 1 root root 7 Jun 16 16:24 backup -> /backup
lrwxrwxrwx 1 root root 7 Jun 16 16:24 config -> /config
lrwxrwxrwx 1 root root 6 Jun 16 16:24 media -> /media
lrwxrwxrwx 1 root root 6 Jun 16 16:24 share -> /share
lrwxrwxrwx 1 root root 4 Jun 16 16:24 ssl -> /ssl
➜ ~ ll /config
total 0
➜ ~ ll /
total 120K
drwxr-xr-x 2 root root 4.0K Feb 3 2021 addons
drwxr-xr-x 2 root root 4.0K Jun 23 20:21 backup
drwxr-xr-x 1 root root 4.0K Jun 11 05:43 bin
drwxr-xr-x 2 root root 12.0K Mar 8 14:55 command
drwxr-xr-x 0 root root 0 Jun 23 19:57 config
drwxr-xr-x 3 root root 4.0K Jun 16 16:24 data
drwxr-xr-x 16 root root 4.0K Jun 16 16:17 dev
drwxr-xr-x 1 root root 4.0K Jun 16 16:24 etc
drwxr-xr-x 1 root root 4.0K Jun 16 16:24 home
-rwxr-xr-x 1 root root 907 Mar 8 14:55 init
drwxr-xr-x 1 root root 4.0K Jun 11 06:02 lib
drwxr-xr-x 2 root root 4.0K Feb 3 2021 media
drwxr-xr-x 2 root root 4.0K May 24 04:53 mnt
drwxr-xr-x 2 root root 4.0K May 24 04:53 opt
drwxr-xr-x 6 root root 4.0K Mar 8 14:55 package
dr-xr-xr-x 300 root root 0 Jun 16 16:24 proc
drwxr-xr-x 1 root root 4.0K Jun 24 21:26 root
drwxr-xr-x 1 root root 4.0K Jun 16 16:24 run
drwxr-xr-x 1 root root 4.0K Jun 11 06:02 sbin
drwxr-xr-x 2 root root 4.0K Feb 3 2021 share
drwxr-xr-x 2 root root 4.0K May 24 04:53 srv
drwxr-xr-x 2 root root 4.0K Feb 3 2021 ssl
dr-xr-xr-x 12 root root 0 Jan 1 1970 sys
drwxrwxrwt 1 root root 4.0K Jun 24 21:26 tmp
drwxr-xr-x 1 root root 4.0K Jun 11 05:43 usr
drwxr-xr-x 1 root root 4.0K Jun 11 05:43 var
➜ ~
seems that the folder has been corrupted on Jun 23 19:57
Now everything still works fine and as mentioned earlier ‘Check Configuration’ in Dev Tools tells me that the Configuration is valid.
Is there a way to fix this strange issue or do I need to reinstall everything from scratch?
Had some more thoughts about the issue and as ha is running as a docker container on the py4 it is only the mapping of the config folder to the docker container that might be broken.
Considering this I rebooted the host and /config is back to normal
Just for the records if someone else stumbles over this tread. Be aware that after restoring a backup you might need to restart the host to fix broken links into the docker container running HA.
I came across a similar issue today on 2022.8.4 (RPi), where in the Lovelave/File Editor NO files appeared under /config directory. Subdirectories appeared normally, with all files within subdirectories visible. Neither HASSOS restarts or server reboot resolved this, and my HA config was working normally.
I noticed all files were visible on a network connected Windows PC (samba share, I think), and using HA Terminal the ls command listed all files. I eventually noticed a file under /config with the name ???@@??, visible under Terminal but not Windows.
Using rm I couldn’t delete the file, but the following steps (using Terminal) worked for me:
cd config
ls -li
This lists files with their unique “inode” as the first field on each row. I was then able to delete the file using the find command.
Had the same issue today, went into Add-Ons, File editor and clicked “configuration” then “Directories First” also restarted Samba Share whilst in the add-ons section and BOOM file editor came back
I just had the same issue after restoring a backup.
I was a little nerves about restarting while the config folder was empty, but did so anyway and everything now is back.
Thank you.