Search results

Danke noch einmal für die Unterstützung. Mein Serveranbieter hat die Hardware soeben ausgetauscht - mal schauen, ob das etwas bewirkt.... Ich bin gespannt... Entsprechend habe ich auf die anderen Punkte verzichtet - oder würdest Du trotzdem eine der Maßnahmen ergreifen? Die BIOS Version ist...

sad, I've set it to 0 and for 8 hours have no issues yet...

Danke für den Hinweis! Über entsprechende Berichte bin ich auch gestolpert, allerdings wäre das doch ein großer Zufall nach einem Upgrade (oder?). Das BIOS Update hat immerhin bewirkt, dass ich die services einfach neustarten kann... aber das ist natürlich nicht wirklich zufriedenstellend :(

Can you post the output of: cat /sys/module/vhost_net/parameters/experimental_zcopytx

But it happens after an upgrade, right? If yes I doubt it is your hardware. Have you direct access to the server (e.g. homeserver) and can you conduct a BIOS update?

I understand that, but do you get CPU softlocks/hardlocks so you have to restart the machine, or is it sufficient to restart the service.

Me neither. Does your system completely crash? After a bios update my system is running for 3 days without totally freezing. However, I still have random segmentation faults with pvestatd. A simple service restart pvestatd makes the webinterface available again.

Nach dem BIOS update bekomme ich zwar keine soft oder hard locks mehr dafür aber folgendes: Sep 26 02:23:03 servers kernel: CPU: 11 PID: 79094 Comm: sshd Tainted: P D O 6.8.12-2-pve #1 Sep 26 02:23:03 servers kernel: Hardware name: ASUSTeK COMPUTER INC. System Product...

Thank you for reporting back. Indeed I had the same messages in the journal regarding the network interfaces. And i can confirm making the bridges VLAN aware made these messages vanish. did not have any effect. I am not sure regarding the cronjob you talked about, since it seems useful to me...

Es geht weiter... Sep 25 00:41:10 server kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 Sep 25 00:41:10 server kernel: #PF: supervisor read access in kernel mode Sep 25 00:41:10 server kernel: #PF: error_code(0x0000) - not-present page Sep 25 00:41:10 server kernel...

I am so desperate I opened my own thread: https://forum.proxmox.com/threads/pveproxy-worker-pvestatd-pvedaemon-segfault.154908/

Hallo zusammen, seit rund 10 Tagen (nach upgrade auf 8.2.7) gehe ich (scheinbar) zufälligen segmentation faults auf die Schliche, die ich nicht erklären kann. Konkret sieht das ganze so aus: Sep 24 02:25:58 server kernel: pool[197135]: segfault at 8 ip 0000583433640eaf sp 00007b891dfff680...

it also crashed on 6.5 for me. I contacted the support of my server provider and asked for a BIOS update. Until now it is working. Before, I could trigger the error with my wireguard in a lxc container. As in the thread I have referenced the BIOS update really seems to help.

Absolutely same behavior here. I am investigating this since a week and for now I have decided to pin 6.5.13-6-pve. This thread might help you aswell: https://forum.proxmox.com/threads/proxmox-freeze-nach-kernel-update-to-6-8-4-2-pve.145920/page-4

Thank you for your quick reply t.lamprecht! I doubt that the storage is full. I am using a Hetzner Storagebox for my backups (2TB) and the other Backup jobs also do not report any errors. In fact the storage still got 1.3 TB of free space. I am not in a hurry so just relax :-)

Hello all, I am relatively new to proxmox and I would like to configure backups. My linux vms are backed up with the snapshot mode, but I got a windows vm which I would like to backup in stop mode. Actually what I expected was: 1. Shutdown the VM 2. copy the disks to the defined backup space 3...