PVE crashes “randomly”
- Thread starter xMGamerPlex
- Start date
Would you like to tell us a bit more about your hardware?
Has the server ever run stable, or never?
CPU, manufacturer, storage (NVME/SSD...), what kind of file system do you use? Raid level if used...? How much RAM does the machine have?
Things that could give us a clue as to why the server is crashing?
Has the server ever run stable, or never?
CPU, manufacturer, storage (NVME/SSD...), what kind of file system do you use? Raid level if used...? How much RAM does the machine have?
Things that could give us a clue as to why the server is crashing?
Hey, sorry I forgot to tell you.
In the beginning the server ran without any problems. I can't remember exactly when, but the server just started crashing at some point. The power LED is still on and the activity LED is permanently off. The fans are also still working normally. I can no longer access the web interface (no longer accessible). In the beginning I didn't care but now I have a Pi-Hole and use it as the main dns server in my network.
CPU: AMD Ryzen 5 1600
Mainboard: ASRock B450 Fatal1ty Gaming
RAM: 32GB (2x 16GB) G.Skill Aegis DDR4-3000
Boot SSD: 512GB Silicon Power Ace A55 2.5”
Storage HDD: 2TB Seagate Barracuda Compute ST2000DM008
Backup NVME SSD: Silicon Power PCIe M.2 NVMe SSD 512GB Gen3x4
Attachments
Thanks for the info's. Basically the server looks good. Straight forward setup. Please answer a few more questions:
What PVE Version to you use?
Is it possible that the RAM runs out of space and this causes a kernel panic? -> Check the stats on the hosts dashboard.
Check your jounallog on errors: Here are some examples to search with prioryties in the journallog:
And post your smart values of your boot ssd:
What PVE Version to you use?
pveversion -vIs it possible that the RAM runs out of space and this causes a kernel panic? -> Check the stats on the hosts dashboard.
Check your jounallog on errors: Here are some examples to search with prioryties in the journallog:
Code:
journalctl -r -p3
journalctl -r -p4
dmesg -l err
dmesg -l warnAnd post your smart values of your boot ssd:
Code:
smartctl -a /dev/sdaThanks for the quick reply.
I am currently using PVE 8.2.0:
Code:
proxmox-ve: 8.2.0 (Running kernel: 6.8.12-1-pve)
pve-manager: 8.2.4 (current version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-1
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.8.8-3-pve-signed: 6.8.8-3
proxmox-kernel-6.8.8-2-pve-signed: 6.8.8-2
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2 firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1All VM's and LXC CT used a total of 9728 MB RAM and 1536 RAM SWAP