Invalid type 'C' in pack at /usr/share/perl5/Convert/ASN1.pm

My Proxmox server consists of a PC with Intel 13700 (Non K) CPU
2x32GB Ram DDR5 5600
NVME1: 500GB VMs
NVME2: 2TB Backups
SSDSata: 2TB Backups
Intel X550T2 NIC

Code: 
root@proxmoxhome:~# df -Th
Filesystem           Type      Size  Used Avail Use% Mounted on
udev                 devtmpfs   32G     0   32G   0% /dev
tmpfs                tmpfs     6.3G  3.9M  6.3G   1% /run
/dev/mapper/pve-root ext4      461G  238G  204G  54% /
tmpfs                tmpfs      32G   40M   32G   1% /dev/shm
tmpfs                tmpfs     5.0M     0  5.0M   0% /run/lock
efivarfs             efivarfs  192K  125K   63K  67% /sys/firmware/efi/efivars
/dev/nvme0n1p2       vfat     1022M   12M 1011M   2% /boot/efi
/dev/nvme1n1p1       ext4      1.8T  1.2T  598G  66% /mnt/pve/NVME2TB
/dev/sda1            ext4      1.8T  840G  901G  49% /mnt/pve/SSD2TB
/dev/fuse            fuse      128M   20K  128M   1% /etc/pve
tmpfs                tmpfs     6.3G     0  6.3G   0% /run/user/0

Updated with the latest BIOS available
 
Last edited:
I'm afraid you have one of the errors that occurs with the Intel 13xxx and 14xxx CPUs.
I have heard many reports of problems, but I don't know of a solution for these CPU models.
 
Proxmox is truly an excellent platform, but this Bug thing relating to Intel generations 13 and 14 makes me very uncomfortable.
The computer I'm using is new; it is an Acer Veriton X4715GT with Bios updated to the latest version.
So, in your opinion, is it an Intel Bug problem?
Since the computer is new, I would rule out any hardware-related problems. Correct?
 
OMG
I checked the manufacturer's website to see if there was a new update for the computer... and indeed there is a new BIOS !!!

Fingers crossed !!!

INTEL.png
 
  • Like
Reactions: fiona
InTeL3D said:
Proxmox is truly an excellent platform, but this Bug thing relating to Intel generations 13 and 14 makes me very uncomfortable.
The computer I'm using is new; it is an Acer Veriton X4715GT with Bios updated to the latest version.
So, in your opinion, is it an Intel Bug problem?
Since the computer is new, I would rule out any hardware-related problems. Correct?
Click to expand...
This is not a Proxmox problem. It is a general design problem of these Intel CPUs. You have the same problems with all other hypervisors. You just don't hear about it with ESXi because very few people run ESXi on consumer hardware.
HyperV is also no longer free, so the open source hypervisors are the ones that stumble across these problems first.
 
  • Like
Reactions: fabian and Johannes S
as i know you can request rma to get a fully working processor, intel knows about the 13xxx and 14xxx problems.
 
You must log in or register to reply here.
Top Bottom