Hi! Thanks all. I have created a new instance and attached my previous volume, it works correctly. How can I delete the root disk? Or create a new instance where my HAOS volume is the root disk?
@oriaj3 - It’s my understanding that the root disk is a sparse volume, so it takes an insignificant amount of space.
I believe there will be more options coming in the TrueNAS 25.10 release. Supposedly, there will be the ability to directly import the qcow2 image without using the command line or writing the image to your zvol. Hopefully, it will be imported to the root disk, but we’ll have to wait and see.
For now, this post in the TrueNAS forums may help.
Your screenshot shows you seem to have multiple IP addresses assigned to your bridge. Do you need three IP addresses assigned to TrueNAS? I only have one IP address assigned to my bridge: the IP of my TrueNAS server. You also have three bridge members assigned. I would try removing the two unconnected ones, so the only bridge member remaining is enp2s0f1.
I don’t know how much I can help with networking issues. I can not reproduce these issues on my system, so I can’t troubleshoot them myself. I’ll share my settings for you to compare with yours. Maybe you’ll see something that can help.
Here’s a screenshot of my TrueNAS network and bridge settings. I created the bridge following Stux’s YouTube video.
My Instances Global Settings - Default Network are at the default values.
When I created the VM, I unchecked Use default network settings and selected the bridge I created under Bridged Adaptors.
1 Like
I had someone else try your same steps and watched them do it. It booted up just fine for them.
Error/issue was in the CPU configuration, I set it to 1-4. When the other person set it up, they just used 4 and it booted up just fine.
Gotta love those easy gotchas, right?
I had another friend help me fix this, I did set it to just 1 bridge members. The screenshot with the 3 was 2x IPv4 and 1x IPv6 ports being assigned to it. Suspect of the 2x IPv4 was some router/switch issues where it needed releasing and renew of the IP. That caused it to need two different ports. Was able to reset the connections and get it back down to just one.
Thanks again for the steps to try.
1 Like
Somehow after several trys with new zvols and even testing a older version of haos its now working.
At first i used zvols with 33000MB. I changed that to 35000MB, with that haos 15.1 and 15.2 are working.
My network configuration was fine.
1 Like
I’m glad it’s working now. I’m still not sure why some folks are having trouble with the recommended 32 GiB size. No matter how many times I try, I can’t reproduce the issue.
Even my main instance of HAOS, which has been running for about 4 years now, only uses 8 GiB