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
Iâve updated the OP to include steps for creating a VM in TrueNAS 25.04!
⌠And now theyâre bringing the previous implementation back in version 25.04.2
1 Like
Hi everyone. Great thread! Iâm new to TrueNAS and HAOS, but I installed it without a hitch using the instructions here. My only problem is getting Zigbee2MQTT to work.
TrueNAS SCALE: Fangtooth 25.04
HA Core: 2025.7.2
Zigbee dongle: Sonoff Zigbee 3.0 USB Dongle Plus
TrueNAS âInstancesâ VM for HAOS
*** HAOS Settings ***
Under Devices & services > Integrations there are 2 related items:
1) MQTT > Mosquitto broker 6.5.1
Broker: core-mosquitto
Port: 1883
Username: mqtt-user
Password: ****************************
2) Zigbee Home Automation > Sonoff Zigbee 3.0 USB Dongle Plus
> CC2652 by Texas Instruments, firmware: Z-Stack 20240710
radio type: znp
serial port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fe3158e2c46bef11bc6897adc169b110-if00-port0
baudrate: 115200
Under Add-ons there are 2 related items:
1) Mosquitto broker 6.5.1
2) Zigbee2MQTT 2.5.1-1
data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: "-d -d"
log: false
mqtt:
server: mqtt://core-mosquitto:1883
user: mqtt-user
password: ****************************
serial: (blank)
Zigbee2MQTT Onboarding:
Found Devices: usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fe3158e2c46bef11bc6897adc169b110-if00-port0 (ITead), /dev/ttyUSB0, zstack
Coordinator/Adapter Port/Path: /dev/ttyUSB0
Coordinator/Adapter Type/Stack/Driver: zstack
Coordinator/Adapter Baudrate: 115200
Coordinator/Adapter Hardware Flow Control ("rtscts: true"): No
Closest WiFi Channel: 6
Network Channel: 11
Generate network? No
MQTT Base Topic: zigbee2mqtt
MQTT Server: mqtt://core-mosquitto:1883
MQTT User: mqtt-user
MQTT Password: ****************************
Frontend enabled? Yes
Frontend port: 8099
Home Assistant enabled: Yes
Log Level: info
Zigbee2MQTT log onboarding results
[2025-07-15 13:57:28] info: z2m: Logging to console, file (filename: log.log)
[2025-07-15 13:57:28] info: z2m: Starting Zigbee2MQTT version 2.5.1 (commit #unknown)
[2025-07-15 13:57:28] info: z2m: Starting zigbee-herdsman (4.3.1)
[2025-07-15 13:57:28] info: zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"fe3158e2c46bef11bc6897adc169b110","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fe3158e2c46bef11bc6897adc169b110-if00-port0","vendorId":"10c4","productId":"ea60"} => zstack: 4
[2025-07-15 13:57:28] info: zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
[2025-07-15 13:57:28] error: z2m: Error while starting zigbee-herdsman
[2025-07-15 13:57:28] error: z2m: Failed to start zigbee-herdsman
[2025-07-15 13:57:28] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-07-15 13:57:28] error: z2m: Exiting...
[2025-07-15 13:57:28] error: z2m: Error: Error Resource temporarily unavailable Cannot lock port
[13:57:28] INFO: Preparing to start...
[13:57:28] INFO: Socat not enabled
[13:57:28] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
Iâve looked at several different websites and hours of YouTube videos and tried many different combinations, including direct configuration instead of the Onboarding tool, but no dice. 
Is anyone out there using the current versions of TrueNAS Scale Instances and HAOS with Zigbee2MQTT?
As a new user, I can only post 1 screenshot per post. Let me know if there are any other settings are needed. Thanks!
LOL - I typed all that out and I figured out the problem.
Under Devices & services > Integrations, I had to disable the âZigbee Home Automationâ integration.
Itâs working! 
1 Like
I did it like this but conbee doesnât wantâŚ
Controller Type
nec-xhci
Device
usb_1_2 Zigbee gatewayâŚ
Device Order
1005
[05:57:04] INFO: Preparing to start...
[05:57:04] INFO: Socat not enabled
[05:57:04] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-07-28 05:57:06] debug: z2m: Removing old log directory '/config/zigbee2mqtt/log/2025-07-28.05-51-20'
[2025-07-28 05:57:06] info: z2m: Logging to console, file (filename: log.log)
[2025-07-28 05:57:06] debug: z2m: Loaded state from file /config/zigbee2mqtt/state.json
[2025-07-28 05:57:06] info: z2m: Starting Zigbee2MQTT version 2.5.1 (commit #unknown)
[2025-07-28 05:57:06] info: z2m: Starting zigbee-herdsman (4.3.1)
[2025-07-28 05:57:06] debug: z2m: Using zigbee-herdsman with settings: '"{\"network\":{\"panID\":40000,\"extendedPanID\":[156,190,148,210,92,98,33,19],\"channelList\":[11],\"networkKey\":\"HIDDEN\"},\"databasePath\":\"/config/zigbee2mqtt/database.db\",\"databaseBackupPath\":\"/config/zigbee2mqtt/database.db.backup\",\"backupPath\":\"/config/zigbee2mqtt/coordinator_backup.json\",\"serialPort\":{\"baudRate\":115200,\"rtscts\":false,\"path\":\"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2138439-if00\",\"adapter\":\"deconz\"},\"adapter\":{\"disableLED\":false}}"'
[2025-07-28 05:57:06] debug: zh:adapter:discovery: Connected devices: [{"path":"/dev/ttyACM0","manufacturer":"dresden elektronik ingenieurtechnik GmbH","serialNumber":"DE2138439","pnpId":"usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2138439-if00","vendorId":"1cf1","productId":"0030"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"}]
[2025-07-28 05:57:06] debug: zh:adapter:discovery: Unable to match USB adapter: deconz | /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2138439-if00
[2025-07-28 05:57:06] debug: zh:controller: Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":"HIDDEN","panID":40000,"extendedPanID":[156,190,148,210,92,98,33,19],"channelList":[11]},"serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2138439-if00","adapter":"deconz"},"adapter":{"disableLED":false},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json"}'
[2025-07-28 05:57:06] debug: zh:deconz:driver: Opening serial port: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2138439-if00
[2025-07-28 05:57:06] debug: zh:deconz:driver: Serialport opened
[2025-07-28 05:57:06] debug: zh:deconz:driver: Query firmware parameters
[2025-07-28 05:57:06] debug: zh:deconz:driver: Reset firmware watchdog
[2025-07-28 05:57:06] debug: zh:deconz:driver: Send write parameter request from queue. seq: 1 parameter: DEV_WATCHDOG_TTL
[2025-07-28 05:57:08] debug: zh:deconz:driver: tx timeout for cmd: 0b, seq: 1
[2025-07-28 05:57:16] debug: zh:deconz:driver: Send read firmware version request from queue. seq: 2
[2025-07-28 05:57:16] debug: zh:deconz:driver: Reset firmware watchdog failed
[2025-07-28 05:57:18] debug: zh:deconz:driver: tx timeout for cmd: 0d, seq: 2
[2025-07-28 05:57:26] error: z2m: Error while starting zigbee-herdsman
[2025-07-28 05:57:26] error: z2m: Failed to start zigbee-herdsman
[2025-07-28 05:57:26] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-07-28 05:57:26] error: z2m: Exiting...
[2025-07-28 05:57:26] error: z2m: undefined
TypeError: Cannot read properties of undefined (reading 'includes')
at Controller.start (/app/lib/controller.ts:113:42)
at start (/app/index.js:149:5)
Unfortunately, the Conbee Zigbee devices are known to not work with USB passthrough in TrueNAS VMs. Youâll need to use PCI passthrough for the USB controller to which the Conbee is connected.
Yes, but then it blocks everything if I only share it with the VM.
Which stick would be compatible?.. 
Thereâs always some stupid problemâŚ
I donât use Zigbee myself, but the Conbee is the only one I know of that has a problem. If you want to deal with the hassle of starting your VM with a script, thereâs a work around in the second post, but youâll need to wait for 25.04.2 to be released and use the classic virtualization based on libvirt.
I am trying to do this in Truenas Scale Community Edition and I canât get it to work. I get âError: VM agent isnât currently runningâ.
I am running the TrueNAS 25.04.2 nightly right now, so I am unable to help troubleshoot VMs created using the Instances menu.
Please wait until 25.04.2 is released. I believe that should be released some time later today. Installing VMs under the current Instances menu in TrueNAS 25.04.0 and 25.04.1 is using is using Incus to manage KVM, but that is being removed in the next release. 25.04.2 will add Virtual Machine menu that will use libvirt instead of Incus. For automatic VM migration in TrueNAS 25.10, it is highly recommended to wait for 25.04.2.
TrueNAS 25.04.2 is now available. The OP has been updated!
Iâm trying to install Home Assistant on my TrueNAS, and when I follow all the steps, I get this error: âVNC Display Available Connect using a VNC client to: 0.0.0.0:5900â
Iâm new to this, Iâm still learning. Can someone please help me with this?
Thatâs not an error message. It is telling you that a VNC Display is Available and to connect using a VNC client.
TrueNAS no longer opens the VMâs VNC connection in the browser. Youâll need to use a VNC client on another computer. In the VNC client, enter your TrueNAS IP and use port 5900.
For example, on Windows you might use TightVNC or RealVNC Viewer.
Alternatively, if you want the VMâs display to show in the web browser, you can use a Spice display. First, stop your VM, then click Devices
If youâre not going to use the VNC display, you can delete it from the three-dot menu. Click the Add button in the top right corner to add a Spice display.
Adding the Spice display is straightforward. Set the Type to Display and the Display Type to SPICE. Bind can be either 0.0.0.0 or your TrueNAS IP. You have to set a password, but it can be as little as one character. Finally, ensure the Web Interface box is checked and click Save.
Thatâs it! Now, the Display button should open the HAOS terminal in the web browser.
Hi,
I am trying to install HAOS on my truenas server using this guide (was previously on my RPi) Installing HAOS in a VM on TrueNAS . After I enter wget https://github.com/home-assistant/operating-system/releases/download/16.3/haos_ova-16.3.qcow2.xz I get an error saying âCannot write to âhaos_ova-16.3.qcow2.xzâ (Operation not permitted).â what could be the issue? I have created the zvol dataset and should have admin priv on my account so Im not entirely sure what the issue could be. Any help would be greatly appreciated