there are actually multiple checksums.
chunks contain a CRC (verified on each read of the chunk) and have a digest (that the chunk is referenced by). both are calculated on the client side, the CRC is verified by the server upon upload, the...
Check and restart -if it is not "active (running)"- pveproxy:
~# systemctl status pveproxy.service
~# systemctl restart pveproxy.service
~# systemctl status pveproxy.service
Hi,
The latest version (in no-subscription) is pve-manager/9.0.6 which fix your issue. It's fixed in pve-container (6.0.10), which was released the 07-Sep-2025 (in no-subscription).
Best regards,
Yes, you are (or course) correct. Note that I do admit that although I am using ZFS exclusively - the few clusters I have are small.
With that number of nodes ZFS-replication (over all nodes) would be a bad choice. And partial replication -let's...
Managing ZFS replication with multiple nodes is a PITA and the pain scales with the number of nodes and machines. Just go with shared storage. This will yield a much better cluster experience. For me, a "real" cluster requires a (dedicated or...
Each tool has it own benefits. But yes, I am using cv4pve for exactly that reason. While I am absolutely able to handle Desaster recovery with naked replicated snapshots the integration in the PVE logic and in the GUI is really convenient! The...
!!! 1.Hint: This Thread is not for Ceph fan boys. Go away! !!!!
Occasion:
In the Thread "Vote for Feature in ZFS-over-ISCSI" my one (the word "one" is always related to a human being, not a matter or person or number) had to put question marks...
Circling back around on this, the answer is...yes, it was a 'too much data' problem. Setting a pretty wide net of prune (keeping around 50 snapshots over time per VM, around 2,000 snapshots currently) cleared ~95,000 snapshots, and the subsequent...
Thanks a lot for the explanation, it's very clear and I like the fact that this protects the best part of the backup chain of hardware and software. This means that if the PVE host does not corrupt data, then any further corruption, even in the...
My grub was messed up after upgrading, so I did a liveboot to mount the root volume and boot, then reinstalled and updated grub and I was back.
# find your root and boot by looking at your partitions, mine looked like this
lsblk
NAME...
Wahrscheinlich, aber richtig gut kann ich dir zu dem Modell nichts sagen, da müsstest du hier mal nach Beiträgen von anderen suchen. Bei Micron weiß ich wenigstens, dass ich das firmware-binary bekomme und auch unter Proxmox direkt flashen kann...
It is (first) calculated on PVE.
Then this checksum is transmitted to PBS - only the checksum, no data.
If a chunk with that checksum already exists on PBS then some references are updated to reflect this new backup.
Only if that checksum is...
Things like this can simply be tested: when I disable the debian sources and query the policy of a random (but known to be installed) package I get:
~# apt policy bash
bash:
Installed: 5.2.37-2+b5
Candidate: 5.2.37-2+b5
Version table:
***...
I am not @fabian ;-) but I can show you this:
My system is using non-subscription, everything updated.
~# pveversion
pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve)
The swtpm binary comes from the corresponding package...
So... I upgraded the cluster on my own.
- I moved all my VMs/Containers to the second node
- I followed the guide to remove first node from cluster (be careful as there some steps to follow there)
- Don't forget to remove any replication between...
Then don't. Any change to PVE can and will probably lead to problems down the way.
Those are similar to the ones for the enterprise repository, so just delete the file. It and the enterprise repository may come back with an upgrade, so be...
Interesting that you have "pbs" there.
Not on mine any more.
My output:
systemd-boot:
Installed: (none)
Candidate: 257.8-1+pmx1
Version table:
257.8-1+pmx1 500
500 http://download.proxmox.com/debian/pve...
Yeah, that the one instance I have with PVE + PBS installed in parallel. I will try to not take that node as an example-generator anymore, as I could not exclude extraordinary behavior.
Glad you spotted it. That's why I usually copy-n-paste the...