Recent content by Szymons

I can confirm that in latest proxmox v8 this bug still persist... filter for rsyslog seems to be like a "Powdering BUG's..."

I had to change /etc/default/chrony to fix it https://forum.openmediavault.org/index.php?thread/41020-chronyd-and-chrony-services-failed-to-start/&pageNo=4 update... after doing this .. I thing there is no option to check chrony

after proxmox kernel update this is not working anymore... SMP PVE 5.15.131-3 (2023-12-01T13:42Z)

Hello, I cannot add bridge-vids into vmbr network : ip link stats : vlan aware is working cause I can see bridge -c vlan show After I add vlan tag 123 into vm id 108 network 3 where is vmbr used :

I can admit after few years ... that in proxmox 8 and latest ifupdown2 I have feelings that this bridge-vids is not working ! but I will create new topic and noone will say to me that I was not searching :D

Hello, in proxmox 7.4-1 and kernel 5.19.17-2-pve UBSAN messages still occure ================================================================================ UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:125:9 index 1 is out of range for type 'MR_LD_SPAN_MAP [1]'...

ofc after editing grub... run : update-grub about cpu idle states ... I am using linux-cpupower and set performance during bootup /usr/bin/cpupower -c all frequency-set -g performance or add /lib/systemd/system/x86_energy_perf_policy.service [Unit] Description=Run x86_energy_perf_policy at...

I have UBSAN messages only on bootup but this is more megaraid UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:103:32 index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' https://forum.proxmox.com/threads/proxmox-ve-7-2-megaraid-issues.110587/ about Your issue...

I cannot see 'dmesg' startup information cause there is only : this is not enought ?

and there is no option to fast patch this ? ...

hello, In other topic : https://forum.proxmox.com/threads/new-proxmox-server-mce-hardware-errors.126713/#post-589381 I had same issue without information. On one specified HW issue stop when I replaced FibreChannel card. But it was working... Still proxmox team should fix MCELOG (or rasdaemon)...

On QANTA server mce error log dissapear after replacing Fibre Chanal card. Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) But still PROXMOX team... why there is no info what is that 'hardware error'... MCELOG not exist anymore , rasdaemon not working...

if You are asking me ? I have two different HW and both without 'issue' one : QUANTA motherboard from OCP leopard ipmitool sel list 1 | 07/15/2000 | 03:22:12 | Unknown #0x70 | | Asserted 2 | 08/26/2000 | 18:24:15 | Unknown #0x70 | | Asserted 3 | 09/06/2000 | 02:49:38 | Unknown #0x70...

Hi, any update in this topic ? I am struggling similar issue but with different interval. as I already know... MCElog is not installed anymore... I installed RASDAEMON but same result... no info what is wrong.... some people says that rasdaemon have some bugs.. some people says... any...

Hello, mce: [Hardware Error]: Machine check events logged I am facing same issue as above. proxmox version : proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve) pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4) pve-kernel-helper: 7.3-3 pve-kernel-5.15: 7.3-1 pve-kernel-5.4: 6.4-20...