How can I use the command line to see NFS drives that have been configured as storage through the UI?

[teeeeee]

I am running Home Assistant OS, and have added some NFS drives as storage in the UI:

I want to have a Shell command action or a command line sensor to A) test whether the two storages are accessible (i.e. the NFS mount is present), and B) check the storage disk usage on each of the NFS mounts.

At the moment, I can’t even see these locations mounted anywhere (that I would expect) in the directory structure from the terminal:

They are also not appearing in the output of the df command:

I am able to do HASS backups to these storages from the UI, so I know they are working correctly. How can I find them from the command line?

[WallyR (Wally)]

Addons are separate containers.
It is like it is a completely different server.
Available commands between the HA container and the terminal addon container might also be different.

[teeeeee]

@WallyR

I see. So, is it possible to use a Shell command to for example create a file on an NFS storage?

[WallyR (Wally)]

Should be, if the command is available.

[teeeeee]

This is what I’m asking. Since it’s not located in /mnt/ or /media/ or /share/ , where is the NFS drive?

[WallyR (Wally)]

I tried to say it.
You are not connected to HA, but to the terminal addon.

[teeeeee]

So, how to connect to HA instead?

[WallyR (Wally)]

HOWTO: How to access the Home Assistant OS host itself over ssh

It took a while to figure this out, so I might as well document this. Looking at the amount of search hits on this subject, I wasn’t not the only one that needed access to the host itself. When debugging an issue related to the OS or docker, you might need access to the host itself. The Terminal & SSH Add-on drops you in a container, while this might be enough for users, you sometimes want to access the real operating system, to examine some docker issue for example. There is a well written do…

[teeeeee]

Thanks @WallyR .

I now completely understand what is going on, and have learned something new.

The host system (which I accessed through the Proxmox console) correctly shows the mounted drives.

When running HAOS, the drives that are configured in the UI under
“Settings → System → Storage → Network Drives” are NOT bind-mounted into the “homeassistant” docker container from the host. I guess they don’t need to be.

It seems that instead the mounted network storage drives are bind-mounted into the supervisor container (instead of the homeassistant container, which runs the frontend). This can be seen by first logging into the supervisor container and then showing the mounts:

The mounted network drive on the main VM host is located at:

/mnt/data/supervisor/mounts/

but this directory is mapped to

/data/mounts/

in the hassio_supervisor docker container.