Looking at the screenshot of your ZVOL, it says the volume size is 100 GB and you appear to be using only 5 GB or 4% of that space.
In the first screenshot, it looks like your VM may not be able to reach the internet. I see 404 errors saying image not found. I’ve seen reports on the TrueNAS forum of people with similar issue, having a VM unable to reach the internet. (Reports are with Debian and Ubuntu so not necessarily related to HAOS specifically) Unfortunately, I am not proficient in troubleshooting this issue since I have not encountered it myself.
If you are a member on the TrueNAS forum, you might have a better luck and quicker help posting over there since there are more TrueNAS experts.
I assume you got to that CLI by clicking the display button for your VM in the TrueNAS UI? So, I guess your VM is online and DNS is working if you are able to resolve and ping Yahoo…
I see in your screenshot now… process fix up block from execution, not enough free space.
I’m not sure what we are missing here…
I’m on the road for work again this week but when I get done for the day and back to my hotel with a real computer, not on my phone, I’ll try to remote in to my home assistant and see how my df -h looks
So I can connect to my HA and reach the ssh addon, but I’m unsure how to get the HAOS CLI.
From my understanding, I can disable protection mode and gain access to the Home Assistant Container (or other addon containers), but I don’t know how to get to the actual HAOS CLI - I think that’s where I need to run df -h from.
I’ll keep thinking about this… but might have to wait until I get home (Thursday).
I could, if I was at home… I only have access to Home Assistant through Nabu Casa when I’m on the road. I don’t have remote access to my TrueNAS server.
Since we can now compare with my VM, I notice that your ZVOL may not be the correct size. I realize your Zvol Space Management screenshot shows a Volume Size of 100 GiB, but something is not adding up.
Here’s a full screenshot of my ZVOL details - It’s 64 GiB
If you’re still stuck at the beginning, maybe consider removing your current ZVOL and starting again. Also, be sure the path is correct when writing the image. (I’ve seen people mistakenly use the /mnt path, which is not correct) To be clear - the exact command to write the image to the ZVOL in your screenshot would be
sudo qemu-img convert -O raw haos_ova-10.2.qcow2 /dev/zvol/Data1/HAOS