Recent content by rotanid

can confirm, works again with Linux pve-2 5.15.39-*-pve

we had the issue again today after upgrading to 4.15.18-26

we have 5 systems at the moment with this intel NIC and ProxmoxVE. the system that crashed 2 days ago was running pve-kernel-4.13.16-2-pve until 3 days ago thanks, will try this!

the network crashes are back for us with kernel pve-kernel-4.15.18-2-pve / 4.15.18-20 Aug 29 15:19:28 vh6 kernel: [53879.772436] e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang: Aug 29 15:19:28 vh6 kernel: [53879.772436] TDH <0> Aug 29 15:19:28 vh6 kernel...

oh wow. no, this is a damn cheap consumer device, only 64 TBW in a server...

we know. at least we have no problem after downgrading to pve-kernel-4.13

hm, so 5.2 has been released probably without a fix for this issue with pve-kernel-4.15 ...

so far it only happened during heavy backup traffic times (BackupPC, rsync)

since updating to pve-kernel 4.15.17 (a week ago) we had multiple cases where the NIC driver e1000e had problems and we had to reboot the machine to get network running again. it happened on 2 different servers, multiple times on one of them. the NIC: 00:1f.6 Ethernet controller: Intel...

Hello, we set up a new cluster with ProxmoxVE 4.1 (pve-no-subscription), 2 nodes, no HA. one can see the VMs of the other cluster node and their disk/memory/cpu/uptime. but when we click on on of these VMs on the other node (not the one where the browser points to) then an error appears above...

we are also experiencing similar massive write count increase (SMART and iostat). i started logging SMART-Outputs once per hour to have further data... we use 2 mirrored hard disks with 2 ssds as mirrored log and cache the KVM VMs use qcow files, the next cluster will use ZFS Volumes...

Today, i tried to set up a new ProxmoxVE Node but can't complete the installation, because pve-cluster fails to get the local IP - last week i set up two nodes with exact the same configuration (like /etc/hosts and so on) Is it possible that there is a problem with one of the updates that were...