Proxmox Gray question marks on every machine and every storage

Pablo1732

Member
Dec 25, 2021
43
3
13
Hello,
I had a problem a few months ago where a gray question mark was displayed on every machine and every storage. When I tried to display the shell via the web interface, nothing happened for ages, then a login timeout was displayed. When I logged in via SSH, it also took forever (approx. 1-2 minutes). When I typed in "reboot now" it also took forever and then an error was displayed. However, the VMs and CTs were still running. The only possibility was to switch off the server via the physical switch on the server by holding it down for a few seconds. Then I was able to switch it on normally and everything was running again. I think it was a kernel crash. I had this problem 2-3 times.
But then there was no more crash until now and I thought everything was working again.

However, I have now had the same problem again 2 times this week.

Now there is a similar problem.
The whole server works as it should, no problems, I can restart normally etc..

But the question marks are still displayed.
I have installed all updates again and again ...


Hopefully someone can help me

Code:
root@proxmox-server:~# pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.13-1-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.1
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.4-1
proxmox-backup-file-restore: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-2
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.5-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve2
 

Attachments

  • Screenshot 2024-03-09 131244.png
    Screenshot 2024-03-09 131244.png
    56.5 KB · Views: 7
Last edited:
Hello,

Could you check the syslog looking for any interesting messages?

Could you also please post the output of `cat /etc/pve/storage.cfg` (get rid of all sensitive data ;)) before post the output!
 
Hello,
I found out that one of my RAM sticks was broken. I have now replaced it. Maybe the problem is now solved.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!