New here, question about Seq fault, SGX disabled by bios

[ProxmoxBoy1]

Hello all,
This is my first post here.
Iám running @home about 9 months Proxmox 7.xx
This was running ok until last 2 weeks
The vm's and containers are running but proxmox is greyed out.
The shell is working , reboot fixes the problem for 1 or 2 days

The proxmox host
Intel nuc 8 GM ram //512 GB Disk

Vms Homeassistant 2 cpu / 4GB ram /32gb disk
Container Pihole 1Cpu / 2 GB ram /40GB disk

Recently made some tests with other VM's import from esxi ( planning to leave esxi platform and move the other server also to Proxmox)
These vm's are switched off

I have found some info about this on the forum so here is some additional info

root@pve:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

The Dmesq

root@pve:~# dmesg --level=err,warn
[    0.000000] secureboot: Secure boot could not be determined (mode 0)
[    0.012126] secureboot: Secure boot could not be determined (mode 0)
[    0.114710] x86/cpu: SGX disabled by BIOS.
[    0.116291] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.116291]  #3
[    0.117236] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.331062] hpet_acpi_add: no address or irqs in _CRS
[    0.582090] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.582091] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.582093] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.582094] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.582095] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.582096] platform eisa.0: Cannot allocate resource for EISA slot 5
[    0.582097] platform eisa.0: Cannot allocate resource for EISA slot 6
[    0.582098] platform eisa.0: Cannot allocate resource for EISA slot 7
[    0.582099] platform eisa.0: Cannot allocate resource for EISA slot 8
[    1.736122] usb: port power management may be unreliable
[    5.333909] spl: loading out-of-tree module taints kernel.
[    5.337820] znvpair: module license 'CDDL' taints kernel.
[    5.337824] Disabling lock debugging due to kernel taint
[    5.653835] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    5.808414] thermal thermal_zone2: failed to read out thermal zone (-61)
[   14.549281] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
[   20.409702] kauditd_printk_skb: 8 callbacks suppressed
[51739.677867] show_signal_msg: 8 callbacks suppressed
[51739.677870]pvestatd[979]: segfault at 57e3858eae50 ip 000055e37f14814a sp 00007ffde820e150 error 4 in perl[55e37f066000+185000]
[51739.677881] Code: fe ff 48 8b 4c 24 08 49 89 c4 eb a5 0f 1f 40 00 41 55 48 89 d1 49 89 f5 41 54 48 83 ec 18 4c 8b a7 08 01 00 00 4d 85 e4 74 3e <49> 8b 04 24 48 83 87 00 01 00 00 01 48 89 87 08 01 00 00 49 c7 04
[66522.992698] perf: interrupt took too long (3320 > 3136), lowering kernel.perf_event_max_sample_rate to 60000

[ 0.114710] x86/cpu: SGX disabled by BIOS. Could be switched on i think

[ 0.116291] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
I don't no what to do, maybe nothing

[51739.677870]pvestatd[979]: segfault at, now is there memory overwritten ?

 

[leesteken]

[ 0.114710] x86/cpu: SGX disabled by BIOS. Could be switched on i think

SGX is deprecated, so better leave it off.

[ 0.116291] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
I don't no what to do, maybe nothing

Disabling Hyper-threading might make this message go away. Your CPU, like most CPUs, is vulnerable to various speculative execution security problems.

[51739.677870]pvestatd[979]: segfault at, now is there memory overwritten ?

I don't know what changed or maybe some bytes got corrupted on disk or maybe your system memory is failing?

 

[ProxmoxBoy1]

I will do a memory test with the proxmox Memtest

 

[ProxmoxBoy1]

So update,
The memory is ok,
I had for some months a Samsung SSD disk with sata<>USB3 adaptor connected. This disk i used for backups.
I do not know why this was happening now, the disk is working fine on another PC.
I do not longer use this disk in PVE, the backups are now on my Synology station.