Virtual Machine's status: Internal-error On proxmox 7.1-7

DaniloJavier

New Member
Mar 22, 2022
3
0
1
I have this problem with proxmox 7.1-7
I have an intel server with 2 hard disk (raid 1)
Is that a hardware problem?
 
hi,

Is that a hardware problem?
who knows? you'll need to post more information :)

* do you get this error with all the VMs, or just a single one?

* is your server in a cluster or is it a standalone node?

also please send the outputs of the following:
* pveversion -v
* qm config VMID (replace VMID with yours)
* journalctl -xe > journal.txt and attach the resulting txt file here as well
 
Last edited:
sorry me bad
i have 3 vm and 2 of them have that problem
my server is atandalone node

resutls of 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

1rst vm
root@pve:~# qm config 100
boot: order=sata0;ide2;net0
cores: 2
ide2: local:iso/SW_DVD9_Win_Server_STD_CORE_2019_1809.11_64Bit_Spanish_DC_STD_MLF_X22-51044.ISO,media=cdrom
memory: 4000
meta: creation-qemu=6.1.0,ctime=1646427251
name: WindowsServer
net0: rtl8139=26:3D:7D:51:DE:17,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: local-lvm:vm-100-disk-0,cache=writeback,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=2d2d6d22-0613-42e5-a254-eb5722b12525
sockets: 1
usb0: host=1-13
usb1: spice,usb3=1
vmgenid: ba6eaf8c-1954-4b97-a1ab-6dcec4282dcd

2nd vm
root@pve:~# qm config 101
agent: 1,fstrim_cloned_disks=1
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
description: %0Aroot%0Afocus2022
ide2: local:iso/CentOS-7-x86_64-NetInstall-2009.iso,media=cdrom
memory: 6144
meta: creation-qemu=6.1.0,ctime=1646534066
name: Oml1
net0: virtio=4A:9C:98:01:EA:32,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
parent: LimpioPre
scsi0: local-lvm:vm-101-disk-0,size=50G
scsihw: virtio-scsi-single
smbios1: uuid=e82c1572-7a0c-450d-bfd6-0f1d035032ad
sockets: 1
vmgenid: 88ddaf61-3cfd-4d2f-b5be-faf9f415fe28
 

Attachments

proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
could you try to upgrade your packages to the latest available ones?

and afterwards please reboot your node and observe if the issue still occurs.
 
I saw the syslog on my web interface and got this:

Mar 24 14:46:59 pve smartd[1097]: Device: /dev/bus/0 [megaraid_disk_00] [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 72 to 73
Mar 24 14:47:00 pve smartd[1097]: Device: /dev/bus/0 [megaraid_disk_02] [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 84 to 100
Mar 24 14:47:00 pve smartd[1097]: Device: /dev/bus/0 [megaraid_disk_02] [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 80 to 79
Mar 24 14:47:00 pve smartd[1097]: Device: /dev/bus/0 [megaraid_disk_02] [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 20 to 21
Mar 24 14:47:00 pve smartd[1097]: Device: /dev/bus/0 [megaraid_disk_02] [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 1 to 100

i rebooted the wm (CLI)
the wm was working for a few hours and then it happened again
Captura.PNG
 
Code:
Mar 24 14:46:59 pve smartd[1097]: Device: /dev/bus/0 [megaraid_disk_00] [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 72 to 73
Mar 24 14:47:00 pve smartd[1097]: Device: /dev/bus/0 [megaraid_disk_02] [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 84 to 100

yes that could be a disk error... (it's also in the journal you've sent, the Raw_Read_Error_Rate increasing is not a good sign)
maybe take a look at replacing that disk

though you should still upgrade your machine as i suggested earlier.