Hi, It is posted at the iXsystems/TrueNAS support channels but the problem was on the VM settings on the proxmox side. I had vIOMMU: VirtIO and changed it to Default and now it works.
Currently you can only override this manually in /etc/network/interfaces by creating an entry for the VXLAN interface there - ifupdown2 automatically merges it:
iface vxlan123 inet static
address 192.0.2.0/24
Agree that this should be implemented, could you open a bugzilla entry at https://bugzilla.proxmox.com ?
As a workaround, in the meanwhile you can set it in /etc/network/interfaces directly:
iface wg0 inet manual
mtu 1420
This should not...
The solution itself is simple, I flashed the controller in IT-mode.
https://github.com/EverLand1/9300-8i_IT-Mode
hard drives determined, zraid, production.
As a workaround I made a function call to run command to list all VM-related volumes right after each snapshot operation:
So it now helps me to get this specific moment when disk disappears.
[2026-06-13 08:25:21,323: INFO/ForkPoolWorker-1]...
Just in case someone else has the issue: The issue was, that our VM had used a BIOS instead of UEFI. After changing this (and disabling Secure Boot) it worked also with the new Kernel.
I deleted pve-enterprise.sources.
The server kernel and pve is updated.
Now apt update
apt upgrade
# and
apt dist-upgrade
works perfectly
Thank you very much for your support
Thanks for sharing the detailed investigation. One thing that stood out to me is the mismatch between the expected thin pool transaction ID and the actual transaction ID reported during the rollback operation:
"transaction_id is 10, while...
I believe you will always get the latest point release when upgrading via APT interface. The only way for you to get a particular 9.x release is a fresh install from ISO. Then you will need to avoid full system upgrades and/or hold particular...
You should be able to insert a install ISO of PVE 9.0 and update using the repositories located on the ISO.
Older ISOs can be obtained from [0].
[0] http://download.proxmox.com/iso/
Well, the PBS is a VM itself, and it sits on same same PVE host. However, the PBS storage is "remote" as in I've added it as a PBS store inside PVE. So I'm guessing it's just going over the bridge of PVE to the PBS vm.
But the reading of the vm...
Im my case the problem was uploading the windows 2025 ISO with web-upload using chrome. The SHA256 was different on proxmox and the file size of the ISO was different as well. Using WinSCP to transfer the ISO to proxmox was solving the problem...
Perfect, glad the upgrade finally worked.
Yes this is expected behavior after a major pve-manager update.
You can safely remove the pve-enterprise.sources file.
After that apt update should return no errors.
Hi @user8923428934,
Its possible there is some transition state/race that you occasionally hit. Troubleshooting the cause will require a reproducible scenario, or detailed (logs/debug/trace) record of the event.
The easier path is to add a retry...
ok - but that is to be expected then - if you want to sign only mails from PMG - just add the fqdn of your pmg to the dkim domains e.g. pmg.your.domain (sorry I thought FQDN in your post did not refer to your internal domain, but to the fqdn of...
After apt update
apt upgrade
and
apt dist-upgrade
the server is now on
uname -r
7.0.6-2-pve
pveversion
pve-manager/9.2.3/d0fde103346cf89a (running kernel: 7.0.6-2-pve)
which seems perfect.
But again running
apt update
Hit:1...
Hi there,
We use some custom scripts to automatically roll back VMs to a specific snapshot. We do this using the Proxmox API's rollback endpoint.
To determine when the rollback has completed, we continuously poll the VM status of the rollback...
off topic, aber es hängt eben alles mit Allem zusammen :):
Fußnote zu windows_exporter: Der Collector "cs" wurde aus neueren Releases entfernt, soweit ich verstehe, daher zeigen etliche Dashboards manche Instanzen nicht mehr an, weil die...