Correct. This isn’t a Debian based system.
Without looking at the code I couldn’t tell you but I’m pretty sure, as I stated in my previous comment, that it’s /mnt/data
100% incorrect. The files are literally sitting there on the filesystem. It’s accessible
Sounds like you didn’t get very far with setting it up. What you have done so far sounds very easy to reproduce. You may save yourself a lot of trouble and time by starting over again.
Just remember, the FIRST thing you do with hassio is install the ssh addon!
Thanks Moe.
I’m indeed looking around in /mnt/data.
Found this link and i don’t have a resin-data either.
I definately learned that now 
Actually, I’ve set up a VM on my home server under Ubuntu with docker. I feel much better about taking snapshots of the configs now.
That said, I’ve already re setup my mqtt server and some rules, what I really want out of the sysetm is the network key and some of the buttons I had working to move to new setup.
Plus just to understand where I broke the last system.
Found a solution!
use the extfs tool from paragon allows me to see the memory card details
Now I can remove the offening parts of my config…
For future folks, not sure if this directory is accessible from hassos> or # >
It is 100% accessible from #>
I was unable to find it from the # prompt, but that doesn’t mean it’s not there but absent of commands to find/locate it, I was just looking through directors.
Moveing the SD card over to a PC allowed me to see 4 file systems and the files I was looking for were easily found.
FYI, I was able to find the config files under /mnt/data/supervisor/homeassistant/, but this was a NUC using the VMDK with Proxmox. Not sure if the pi image is the same.
I’ve given up trying from the #> prompt and have edited the configuration from an external machine reading the memory card.
Old thread but I just ran into the same issue. Home Assistant refused to boot even after I had it check my config file and said it was good.
I’m running HomeAssistant (formerly Hass.io according to this) via VirtualBox to experiment with but the same steps should work as long as you have access to the command line of whatever machine you’ve installed it on (even a Pi with an SD card install).
After running login from the command prompt I was given when it booted up (where it seemed to be restricted to just ha commands) I got to the host prompt and started playing around with docker inspect to see where the docker images that home assistant uses map their data too. This was the revealing command:
docker inspect -f '{{ .Mounts }}' homeassistant
The key piece of the output was:
{ bind /mnt/data/supervisor/homeassistant /config ...
So the /config directory inside the main docker container (same file structure you get when using the SSH Add-on in the Home Assistant UI) is mapped to /mnt/data/supervisor/homeassistant/ in the host OS (i.e. the SD card or VM or wherever you installed it).
I edited the config file with the vi command (i.e. vi /mnt/data/supervisor/homeassistant/), undid my latest changes, rebooted the VM…
Problem solved
Actually this might not work with a Pi install or any install where you SSH in via the add-on. Apparently you cannot get to the host when connected via the SSH add-on. Seems you’d have to use this method which highlights the admin pains I’ve heard others describe.
