Thanks for your reply! I went through those steps, none of the commands hung so that was a good sign, no errors on the pool and it was online. I'm now running the scrub. It's about 30TB of data so I'll report back once that is done.
I was trying upgrade both nodes of my 8.4 PVEs to 9.x. One completed successfully, but one failed. I can't figure out how to resolve this particular one. Can someone point me in the correct direction?
This is not planned, as already mentioned in the past, a single subscription would have to start much higher to recoup cost, the current approach scales much better for all and provides an additional benefit for basic and higher.
In any case...
Hi,
Real question: why use a script when there is an official guide ?
As i can see the script does not :
Make a backup of /etc/proxmox-backup to ensure that in the worst case, any relevant configuration can be recovered
Ensure that you have at...
Hi,
Still not a paywall, since, by definition, a paywall limits a feature by paying, which is not the case with ANY proxmox software (remember "No-Subscription" Repository).
As far as I know, you don't need an enterprise license to use PDM...
That's not really an issue though since the enterprise repo get new packages only after the test and no-subscription repo. So the "paywall" doesn't actually limit you any feature or getting updates. Basically you pay by being beta tester and...
Some brute force greping suggests the following files have the /24 in them
/etc/ceph/ceph.conf
/etc/frr/frr.conf
/etc/pve/ceph.conf
/etc/pve/sdn/fabrics.cfg
Easy enough to update them all with sed. I think I could restart the OpenFabric SDN...
I upgraded a 5 node Cluster (with CEPH) from Proxmox 8.4 to Proxmox 9.1.4. The 5th node failed.
So I reinstalled Proxmox 9.1 on the 5th node and tried to add it back to the cluster but all isn't well.
What are the correct steps to take in...
Looks like a corrupted ZFS space map.
Try in recovery mode:
zpool import
zpool import -N -o readonly=on zfspoolname
zpool status -v
zpool events -v
dmesg -T | grep -iE 'zfs|nvme|ata|error|timeout|reset|checksum|panic'
If read-only works you...
Looks like a corrupted ZFS space map.
Try in recovery mode:
zpool import
zpool import -N -o readonly=on zfspoolname
zpool status -v
zpool events -v
dmesg -T | grep -iE 'zfs|nvme|ata|error|timeout|reset|checksum|panic'
If read-only works you...
Hi @Impact! I did not forgot you but I've set this problem on hold for the moment because I can't access the VM's OS so diagnostic this problem is bit hard.
I appreciate your help.
Hi, I have hired a dedicated server and installed PVE on it. I have a Promox cluster at home too and Proxmox backup server. Now my question is it possible to connect the PBS at home to my dedicated server? Is this possible? Is this safe?
Thanks for the help, I managed to fix it by reverting the repos to bookworm and performing a dist-upgrade. That step is on the upgrade guide but was not implemented in the helper script. I opened a ticket to include it and they have since...
FYI, RTL8157 support is now merged into the mainline r8152 driver: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/usb/r8152.c?id=fd3c7d080df53136c7e7e37f753fb7bd4640ca42
It will be in Kernel 7.1.
hi,
First of all thanks for the post, this really helped.
I am facing an issue when I initiate my backups to this pbs. Logs from the failed backup are atteached-
2023-06-11T01:15:39+05:30: starting new backup on datastore 'pve_backups'...
I'm having an issue and can't get my server to boot back to the prompt. Any reboot gives the error
[31.621178] PANIC: zfs: rt={spa=(zfspoolname) vdev_guid=1903510110132383870 ms_id=471 ms_allocatable}: removing nonexistent segment from range...
Exakt was zu erwarten war.
Nochmal für's Verständnis:
Deine GPU hat ein Problem damit, wenn sie mitten im Betrieb resettet werden soll.
Das ist für ein Consumer-Device auch nicht wirklich Teil des Use-Case.
Nun kann man dafür Workarounds...