/config folder is empty?

Have you tried inside Desktop/Lovelace with terminal?

try without the single quotes

‘cd /config’
‘ls -al’

Thanks! That shows the same:

total 0

(For some reason I can’t copy from the web terminal - but the output is the same as when I ssh’ed in.)

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.

after trying to copy something from the Lovelace terminal today the content of my config folders doesn’t show anything.

-> / ls -al
...
drwxr-xr-x    0  root root                  0 Jun 23 19:57 config
...

interestingly Check Configuration in dev tools still shows configuration ok

Have you tried using cd config

You are in the root directory as evidenced by the / in your command and drwxr-xr-x label in ls output.

I have, what you also can see in the ls extract is that the directory size is 0 which seems suspicious

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 :relieved:

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.

2 Likes

I ran into the same issue, restoring a backup. Reboot fixed it.

Thanks everyone! I finally had time to loop back to the issue. Sure enough, a simple host reboot solved my issue.

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.

find . -inum <insert_inode_for_file_to_delete> -delete
eg. find . -inum 1467823 -delete

Not sure if this would be classified as a bug within Terminal?

1 Like

Thanks, I run into the same issue today, reboot of my orchard solved it

1 Like

Thanks for this.
Got the same issue after restoring from backup. Restart of the host helped and resolved the issue.

1 Like

I am having the same issue. Any and all help appreciated greatly.

It started this morning and I have restored backup from 5 days ago, but not luck. I am rebooting between restores.

Of course nothing shows up in Studio Code Server either.

I tried to create a new YAML file and got an error.

I’m running the Generic x86-64 install.

image

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

Yeah, there have been daily updates of core and my config folder is back after one of the updates and restarts.

Thanks,

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.

Restart of host helped me with empty config folder :slight_smile: Thank you.

Hooooo you saved my life, i’ve been trying to solve this for month, and I had a file same as you.

Thx a lot !!!