Running Proxmox 9.2.21
I m running USB Google Coral for a long time, but now i m getting this update error.
Err:6 https://packages.cloud.google.com/apt coral-edgetpu-stable InRelease
403 Forbidden [IP: 142.251.38.110 443]
Reading package...
Running Proxmox 9.2.21
I m using USB Google Coral for a long time, but now i m getting a update error
Err:6 https://packages.cloud.google.com/apt coral-edgetpu-stable InRelease
403 Forbidden [IP: 142.251.38.110 443]
Reading package lists...
E...
I have an odd problem since upgrading my Proxmox cluster from PVE 9.1 to PVE 9.2.3. It consists of three physical proxmox nodes joined together in a cluster. On proxmox I host 3 talos linux control planes and 3 workers. After the update I'm no...
Good: 7.0.14-15-pve. Bad: 7.0.14-19-pve
I've noticed after updating from 7.0.14-15 to 7.0.14-19 higher memory usage than usual. It gradually grew over a few days before I noticed it becoming critical, nearing 100%. Shutting the VMs down returned...
So In the end, i upgraded to Proxmox 9 by reinstalling and restore backups.
Everything is back to normal, fingers crossed.
thank @gfngfn256 and @Impact for your time and help.
Bests,
Thomas
Seems like your thin volumes are broken. I can't really explain why CloneZilla would have caused this for the source disk. I'd restore the guests from backups.
Whatever you need the new one to have. As leesteken tried to explain, the answer is going to be drastically different for different situations. For example, if this disk contains a windows installation, just copying the files won't cut it, you...
lvm-thin is an abstraction, and is not meant to be cloned. For ext4, if you changed sector sizes for example, between 512 and 4k that could maybe cause some of the issues you're seeing bc the underlying topology has changed...
Having the same issue with Broadcom BCM57414 Dual 25Gb adapter, on a DELL PowerEdge R6515 with an AMD EPYC CPU and PVE 9 kernel 7.0.14-20-pve.
Also using Linux bond, in active-backup mode. There are two bonds on each server - only the second...
In my home lab, I use this script to download the latest deb package for aarch64 and extract the binary to be used on random aarch64 boards.
#!/usr/bin/env bash
set -euo pipefail
REPO="wofferl/proxmox-backup-arm64"
INSTALL_DIR="/usr/local/bin"...
I would suggest reviewing the PVE Wiki page for Windows VirtIO drivers:
https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers
I note that you mentioned 0.1.302 as the installed driver version - but currently 0.1.271 is currently recommended for...
Hello Stoiko,
Thank you for your analysis.
I checked the Dell support site and upgraded the Broadcom BCM57412 firmware to the latest version available from Dell.
After the firmware update, I pinned the previously failing kernel (7.0.14-20-pve)...
Thank you for your reply.
Yes, right, I'm using the test repo for this cluster.
I identified the affected and working kernels:
Working kernel:
7.0.14-19-pve (boot 0)
Failing kernel:
7.0.14-20-pve (boot -1)
The issue is fully reproducible:
-...
Out of interest, what changes have you made to the governor? Updating the kernel shouldn't have changed anything...
Microcode 20260811 or later is what you want since it's got fixes to Alder Lake processors, especially C-State issues...
It should also be noted that the full documentation to upgrade from PVE 8 to 9 is available here:
https://pve.proxmox.com/wiki/Upgrade_from_8_to_9
This documentation also includes a list of known issues, a checklist and gotchas you may come across.
Hi,
Same issue here with Broadcom BCM57504 NIC (bnxt_en driver) on 7.0.14-20-pve, working fine on 7.0.14-19-pve and previous.
Tell me what logs you need if you need any.