Thanks Beerman,
My issue was a little different, but your response led me on the right path.
I was missing the iommu command in Proxmox Grub.
"GRUB_CMDLINE_LINUX_DEFAULT=“quiet intel_iommu=on iommu=pt”
Strangely I had them on before. A proxmox update must have removed it.
Since rebooting proxmox, truenas has updated successfully.
I’ve noticed a substantial increase in idle CPU utilization, I have 7 debian vm’s running, I finally upgraded from 24.10 to 25.10 and beforehand idle CPU utilization would be 1-2% not it’s bouncing from 7-10%. this is on an Intel i7 10700. A quick G search shows another 25.10.4 report of the same.
Surprisingly I went from 3-5% idle to 0-1% from 24.10 to 25; anything interesting in tops?
@zpackrat & Fleshmauler. This should be a new thread or just join in this other, recent thread.
But if you don’t know the parameters that go into that determinism, then it can seem non-deterministic.
Thank you, this helped me as well!
FYI.
25.10.4 has reached the milestone as the most popular version of TrueNAS available. It is the recommended version for both Enterprise and CE for both General and Mission Critical use-cases.
Hello @GIEF and @Beerman , thanks for sharing the issues you have found upgrading to 25.10.4. I have experienced the same problem a couple weeks ago but didn’t put much effort into it and stumbled into your workarounds. I’ve tried adding intel_iommu=on on GRUB and running update-grub on the host, rebooted the host, confirmed the new parameter was in effect, and performed a new upgrade attempt. Stopped at busybox - same issue. Then I stopped the VM, changed vIOMMU to Intel (AMD Compatible), tried to start it, and got the following error from Proxmox:
kvm: -device vfio-pci,host=0000:07:00.0,id=hostpci0,bus=pci.0,addr=0x10: vfio 0000:07:00.0: Failed to set vIOMMU: aw-bits 48 > host aw-bits 39
TASK ERROR: start failed: QEMU exited with code 1
The PCI card I’m passing through is a LSI SAS3416 HBA. Looking through some Proxmox forums, some people advised setting vIOMMU as “Defaut (none)", as the setting would not be required anymore when passing through a PCI card. After setting vIOMMU as described, the upgrade succeeded.
Sharing this third solution path, hope this is useful, as well. Cheers.
Correct, you do not need vIOMMU when IOMMU is passed through from the host system. So setting to default (none) is required.
I’m sure we’ll still see posts on the TN subreddit asking if upgrading from a 6 year old version to v25 is safe. They’ll explain that they were scared to upgrade … for 6 years.
In better news, 25.10.4 works great for me. Zero issues.
The real issue is that TrueNAS 13.0 was very good… and still works very well. We did our best to make it very solid and reliable.
The good news is that TrueNAS 25.10.4 is even better, with many new capabilities. If and when users want to upgrade, they can.
How’s that an “issue” ?
It creates a pool of users who have very little need to update… but they don’t have ongoing security updates. We’d prefer that they have a plan to retire/refresh/upgrade their systems despite the lack of issues they are experiencing now.
