OK, thanks for the screenshots. I see a problem - notice how only 588MiB of data is written.
It should use more space than this (after it starts the first time). It looks like HAOS has failed to expand correctly. You may need to try again.
I just created a test VM to grab some screenshots. The first screenshot is right after running the qemu-img convert command. Notice that the data written is around 574 MiB - right now, this looks good because I have not started the VM yet.
Next, I’ll start the VM for the first time. I give HAOS a few minutes to start and recheck ZVOL details. Notice the data written has increased to 3 GiB. We want to see this as it indicates successful file system expansion!
I can see here you have tried this a few times.
Let’s delete ALL of those downloads and extracted images, then try again.
rm haos_ova-10.5.*
Your ZVOL size looks good, so we can just overwrite the existing install with a fresh one. You can still use the existing VM as well, just make sure it’s stopped before moving on.
wget https://github.com/home-assistant/operating-system/releases/download/10.5/haos_ova-10.5.qcow2.xz
unxz haos_ova-10.5.qcow2.xz
qemu-img convert -O raw haos_ova-10.5.qcow2 /dev/zvol/Proba/home_vm1
If you have any errors, stop, and please share the output from all the commands you have run to that point. After running qemu-img convert, check your ZVOL details, and you should have around 574 MiB of data written. If that looks good, start the VM and give it an extra minute or two for the initial bootup. Check your ZVOL details a final time and hopefully, you see around 3 GiB of data written.
Good luck!
EDIT: Looking at your VM setting - I also recommend the following changes.
There’s nothing wrong with having loads of CPU HAOS, but unless you know it’s needed, you can also reduce the number of threads to free up resources for TrueNAS.