Upgrade v8 to v9 and Disk for TrueNAS OS is gone

dhenrickson

New Member
Sep 26, 2025
2
0
1
Michigan
Hello,
I recently did an upgrade from v8 to v9 and everything came back with my windows VMs, but my TrueNAS Scale did not. Got that QEMU error with Code 1 showing. I can click on the VM and see that Hard Disk (scsi0) is showing Disk-0 instead of Disk-1 like all of the other VMs show for the OS system. How do I get that back? Did I lose everything and have to rebuild that or is there a fix for this? I have read through this forum, and people have fixed this, but their fixes did not work for me. Plus, there are a lot of assumptions that people are "pros" on this when asking questions and some of the solutions were missing steps for me. Any and all help would be greatly appreciated!
 

Attachments

  • Proxmox 01.jpg
    Proxmox 01.jpg
    74.6 KB · Views: 10
  • Proxmox 02.jpg
    Proxmox 02.jpg
    23.4 KB · Views: 10
Remove the virtual IOMMU from the VM (which you most likely don't need) and you'll be fine. There is a known issue with the aw-bits but I'm too lazy to search for it. The error message is quite clear and the vm-201-disk-0 is not abnormal and has nothing to do with it.
 
Last edited:
Hi @dhenrickson , welcome to the forum.

Disk naming (indexing) can and does vary across the VMs. Whether the boot disk is disk-0 or disk-1 is completely irrelevant.

As @leesteken quickly pointed while I was typing - the error message is unrelated to disks and has to do with the highlighted configuration setting.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: leesteken
Remove the virtual IOMMU from the VM (which you most likely don't need) and you'll be fine. There is a known issue with the aw-bits but I'm too lazy to search for it. The error message is quite clear and the vm-201-disk-0 is not abnormal and has nothing to do with it.

Holy crap! that worked. So, the Virtual IOMMU worked in v8 when I set it up, but it does not work in v9? It might be clear to you, but I am just learning about this. I have only ever done OS to hardware systems. Proxmox is new new for me. I copies and pasted that error in Google and nothing that showed up suggested that I just remove that from the Machine settings. That was definitely a lot easier than trying to do what was suggested elsewhere in this forum. I appreciate your quick response and solid recommendation.