Recent content by logics

Einer meiner PVE hosts war nicht mehr via Web GUI erreichbar, ist komplett gecrasht (im Syslog stundenlang keine Einträge mehr) also habe ich den Hetzner "Automatischer Hardware-Reset" genutzt, um einen Reset auszulösen und das System neu zu starten. Ich habe folgendes in /var/log/kern.log...

thanks for the quick reply. I've opened https://bugzilla.proxmox.com/show_bug.cgi?id=4646

To be precise: The sync job on host A (which pulls data from remote host B) does cause lots of proxmox-backup-proxy logging on host B, not on host A. I have the same problem, because several servers sync data from a host about every 5-10 minutes, so on the host that data is being pulled from I...

Thanks a lot for your solution, and the details! I just want to add some detailed instructions, and provide another example of bus IDs, so maybe my example helps out someone: I am using the brand new Hetzner EX 101 which includes a Intel® Core™ i9-13900, and tried to install Proxmox...

Because in case of a problem, we can use live-restore and like this, our VM and web server is up and running after about 7-9 minutes. If you have a full-restore, even without parallelization, it would be difficult to restore 750 GB in under 10 minutes I guess. Of course combining both would be...

I tried parallelization of the restore process, see parallelize restore.rs on https://lists.proxmox.com/pipermail/pbs-devel/2020-December/subject.html But see the restriction in https://lists.proxmox.com/pipermail/pbs-devel/2020-December/001685.html Indeed I did see an improvement in my...

Hi guys, when restoring a VM via full-restore (i.e. the old way), you log the name of the backup as follows: new volume ID is 'local-zfs:vm-102-disk-0' restore proxmox backup image: /usr/bin/pbs-restore --repository root@pam@localhost:chunks4tbnvme101 vm/101/2021-05-17T11:32:02Z...

Thanks for the PVE 6.4 release! The Live-Restore feature is especially interesting to me, because I've always looked for ways to make the restore faster in order to keep disaster recovery times a minimum. Situation: Main Node has 16 cores / 32 threads VM 101 has 32 vCPUs, because the database...

Thanks, I did it, that was an easy apt-get install pve-kernel-5.11 (see https://forum.proxmox.com/threads/kernel-5-11.86225/page-2#post-381945) relevant /var/log/syslog parts: # boot with kernel 5.4: Apr 3 16:17:44 MyHost kernel: [ 0.000000] Linux version 5.4.106-1-pve (build@pve) (gcc...

Enabling pvetest repo is not needed anymore. I am using the default deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise and just installed it via apt-get install pve-kernel-5.11 Awesome: Ryzen 5000 CPU temperature monitoring is working now with Proxmox! ~# uname -r...

pve-no-subscription yes, see https://forum.proxmox.com/threads/kernel-5-11.86225/#post-380185 But I can't see it pop up in the enterprise repository yet

Thanks for the news! Though I'll wait until it comes to the stable repo

I am having the same issue, probably because of kernel 5.4: Mainboard: Asus Pro WS 565-ACE BIOS: tested both Version 0502 (2021-01-15) and current Version 0703 (2021-03-11) which is the newest BIOS version as of today. Same error messages in both versions. CPU: AMD Ryzen 9 5950X (Hetzner...

your instructions worked perfectly:)

Wow thanks a lot! I'll try that out and keep this thread updated