Hello,
it isn't solved - as the Datastore3 still shows 1.35TB. And yes I could move all Disks to Datastore1 and recreate Datastore3, but I would rather find the issue and "repair" Datastore3.
There was or there is an error in capacity reporting. I have no link, but the main point was that "more capacity" was actually present but just not reflected by the displayed values.
As you found your solution by recreating the pool you may...
After expanding the RAIDZ2 you need to rewrite the data so it can use the new parity ratio of 2:4 instead of 2:2.
See: https://openzfs.org/w/images/6/68/RAIDZ_Expansion_v2.pdf and...
Thanks for the information. I’m just not entirely sure if I understood it correctly.
I also had a Datastore1 that originally consisted of 4x 480GB drives and was later expanded to 6x 480GB — same issue. As a test, I moved all disks to Datastore3...
Hello Chris
Most likely you do have empty backup groups where the file has not been cleaned up as expected in the past. Make sure to manually clear such empty groups and try again. But first make sure you are running an up to date version...
Unified PMG Tracking Center (multi-node)
I built a small open-source web UI that gives you a single Tracking Center for a Proxmox Mail Gateway cluster. Instead of logging into each PMG node, it queries each node’s official PMG API...
Hi together,
I recently upgraded my Proxmox cluster from pve8 to pve9.1.9.
Then I noticed that some of my VLANs were not working anymore as intended. I could not find a solution since everything looked fine and I didn't change any configuration...
I tried the following drivers: 0.1.240, 0.1.266, 0.1.271, and 0.1.285. I realized this was not a virtio scsi issue, as I said before, when it did not matter if the drive was attached using a SATA / IDE controller or SCSI controller. I am able to...
If I am adding a second pbs storage (same PBS) to replace this one but without "fingerprint" I have :
create storage failed: pbs2-storage: error fetching datastores - 500 Can't connect to 192.168.xxx.xx:8007 (hostname verification failed) (500)
This is interesting. Looks like VMware is testing the waters with ARM support: https://www.theregister.com/virtualization/2026/05/19/vmware-quietly-debuts-arm-hypervisor-tech-preview/5242293
The deprecation itself was not strongly influenced by that, but the decision to communicate it more actively was in fact primarily driven by it. Normally, we only mentioned it on the side once a new kernel became the default. In the past, we...
Thank you guys. I need to find some time and then I will fire upgrade (6 to 7).
I think I use it although I don't understand completely to what you refer? I have a Proxmox on separate SSD drive (ext4) and VM's are on raidz ZFS volume (4 x 2TB...
I cannot seem to get USB pass through to work in my Mac OS 26.5 Tahoe w/ OpenCore-ISO VM. I have tried individually passing through the ID's and ports, I created mapped devices, I set the pass through through ssh, and I have even passed through...
Its doable but I wonder if you using an old boot method which adds an extra challenge. I know my oldest Proxmox install doesnt use the current supported boot method, and I have to treat it with kids gloves.
Sorry for the confusion, this is what I meant. OP can use the archive repo for updating to Debian bullseye, but the regular repos still have Debian bullseye/bookworm/trixie and PVE7/8/9 so no real need to use the archive?
Where did you get, that they don't got to Buster? They actually I could open following links on the page:
https://archive.debian.org/debian/dists/buster/
https://archive.debian.org/debian/dists/buster-updates/...
After expanding the RAIDZ2 you need to rewrite the data so it can use the new parity ratio of 2:4 instead of 2:2.
See: https://openzfs.org/w/images/6/68/RAIDZ_Expansion_v2.pdf and...
PVE7 is based on Debian 11/bullseye, PVE8 on 12/bookworm and PVE9 on 13/trixie.
It seems all 3 repositories you need are still available for both Proxmox and Debian:
http://download.proxmox.com/debian/pve/dists/...