maybe provide a little more detail?
I just upgrade on my proxmox and it was fine went from 25.10.1 > 25.10.2 so this is not a generalized issue
note i once had errors like your on a physical machine when i found an disk has changed index, if you are passing through nvme drives for booting the truenas that can happen in a virtual env too, the error was cuased by initramfs startup sequence looking for the missing drive in a mirror to boot and not falling back to the one remaining drive (which makes me question why have an effing mirror, lo)
i also happend to upgrade my proxmox host (did you do that any time recently) if you did i note i had to finagle once again with my blacklists and modprobes, i am wondering if your truenas can see all the drives it is supposed to - do you boot from a virtual disk or something else in the vm?
I boot from virtual disk, all other disks are passthrough nvme or SATA controller pass though with the following, this changes binding order and while a softdep wont prevent a host drive from grabbing something if it really wants to this usually prevents it and is important because of how drivers are loaded BEFORE the vfio-pci is replaced by ha-manager on proxmox (it’s a classic race condition)
root@pve-nas1:/etc/modprobe.d# cat vfio-pci.conf
softdep nvme pre: vfio-pci
softdep ahci pre: vfio-pci
softdep nouveau pre: vfio-pci
softdep nvidia pre: vfio-pci
options vfio-pci ids=2646:5024,8086:2700,1cc1:8201,1bb1:5018,1e60:2864,10de:1e07,1022:7901,10de:2bb1,10de:22e8
i found in the current version of proxmox these do nothing (they used to tho), including for completenss incase you wereusing this ro prevet drivers claiming devices (in the case below this used udev to force-vfio on my SATA controllers
# Replace BDFs with yours — repeat these two lines for each controller you want on VFIO
ACTION=="add", SUBSYSTEM=="pci", KERNELS=="0000:ea:00.0", ATTR{driver_override}="vfio-pci"
ACTION=="add", SUBSYSTEM=="pci", KERNELS=="0000:ea:00.0", RUN+="/bin/sh -c 'modprobe vfio-pci; echo 0000:ea:00.0 > /sys/bus/pci/drivers/vfio-pci/bind'"
ACTION=="add", SUBSYSTEM=="pci", KERNELS=="0000:ea:00.1", ATTR{driver_override}="vfio-pci"
ACTION=="add", SUBSYSTEM=="pci", KERNELS=="0000:ea:00.1", RUN+="/bin/sh -c 'modprobe vfio-pci; echo 0000:ea:00.1 > /sys/bus/pci/drivers/vfio-pci/bind'"
ACTION=="add", SUBSYSTEM=="pci", KERNELS=="0000:42:00.0", ATTR{driver_override}="vfio-pci"
ACTION=="add", SUBSYSTEM=="pci", KERNELS=="0000:42:00.0", RUN+="/bin/sh -c 'modprobe vfio-pci; echo 0000:42:00.0 > /sys/bus/pci/drivers/vfio-pci/bind'"
ACTION=="add", SUBSYSTEM=="pci", KERNELS=="0000:42:00.1", ATTR{driver_override}="vfio-pci"
ACTION=="add", SUBSYSTEM=="pci", KERNELS=="0000:42:00.1", RUN+="/bin/sh -c 'modprobe vfio-pci; echo 0000:42:00.1 > /sys/bus/pci/drivers/vfio-pci/bind'"
# …add entries for the remaining 7 BDFs…
root@pve-nas1:/etc/udev/rules.d#
lot of random info there but good luck, most more info if you can, i am about tl fly for a week so won’r be able to reply
tl;dr there is no general 25.10.2 in proxmox issue
