Random reboots multiple times a day

N

newcomers

New Member
May 30, 2025
8
0
1
Hi guys,

I have a new pc with the following specs:

AMD Ryzen 5 5600GT Six Core CPU with Radeon™ Graphics (3.6GHz-4.6GHz/19MB CACHE/AM4)
GIGABYTE B550 GAMING X V2 (AM4, DDR4, PCIe 4.0)
32GB Corsair VENGEANCE RGB PRO DDR4 3200MHz (2 x 16GB)
2 x 1TB CORSAIR ELITE MP600 NVMe PCIe M.2 SSD (up to 7000 MB/R, 6200 MB/W)
2 x 240GB KINGSTON A400 2.5" SSD, SATA 6 Gb (500MB/R, 350MB/W)
8TB SEAGATE BARRACUDA SATA-III 3.5" HDD, 6GB/s, 5400RPM, 256MB CACHE
1 x 250gb USB Kingston SSD (Using sata to usb adapter)
1 x 2TB Seagate External HDD
1 x 6TB Seagate External HDD

Proxmox is installed on the 2 Kingston ssds (raid1) and containers and vms go on the 2 x nvme (raid1)

I had a major issue last week which caused the 8tb HDD to fail which has now been replaced. I did a fresh install and these are the packages:

Code: 
proxmox-ve: 9.0.0 (running kernel: 6.14.11-2-pve)
pve-manager: 9.0.9 (running version: 9.0.9/117b893e0e6a4fee)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.14.11-2-pve-signed: 6.14.11-2
proxmox-kernel-6.14: 6.14.11-2
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
amd64-microcode: 3.20250311.1
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx10
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.10
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.7
libpve-rs-perl: 0.10.10
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-1
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.14-1
proxmox-backup-file-restore: 4.0.14-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.1
proxmox-widget-toolkit: 5.0.5
pve-cluster: 9.0.6
pve-container: 6.0.11
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.16-4
pve-ha-manager: 5.0.4
pve-i18n: 3.6.0
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.21
smartmontools: 7.4-pve1
spiceterm: 3.4.0
swtpm: 0.8.0+pve2
vncterm: 1.9.0
zfsutils-linux: 2.3.4-pve1

Im new to Proxmox so not sure what to look for in logs but at the time of the reboots, I was copying data from the 8tb drive to the 6tb drive. For now Im not going to copy anymore and see if that stops the reboots (not sure why it would cause it to reboot). I have attached the 3 syslogs.

Syslog 1 - restart occurs at 17:03:31
Syslog 2 - restart occurs at 00:41:52
Syslog 3 - restart occurs at 05:23:01

I have tried the following in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=assign-busses apicmaintimer idle=poll reboot=cold,hard"

and have also disabled c-states in the bios.

Im at a loss as to what is causing this so any help would be gratefully appreciated
 

Attachments

Hi,
Have you been able to find the cause of this problem?
If not, I would say as you might suspect it looks like a hardware related issue. On syslog1 and syslog3, There's frequent SMART attribute changes on `/dev/sdc` → possible failing drive or controller instability. This is the only thing which looks suspicious in the current log.
 
abobakr said:
Hi,
Have you been able to find the cause of this problem?
If not, I would say as you might suspect it looks like a hardware related issue. On syslog1 and syslog3, There's frequent SMART attribute changes on `/dev/sdc` → possible failing drive or controller instability. This is the only thing which looks suspicious in the current log.
Click to expand...

I ended up starting again and installed proxmox 9, along with updating the bios firmware and so far it has been rock solid.

If I had over provisioned on memory, would cause similar problem? I lowered ram limits on some vms also but not sure if that would've been the cause
 
If I had over provisioned on memory, would cause similar problem? I lowered ram limits on some vms also but not sure if that would've been the cause
Click to expand...
To my knowledge, memory over-allocation might causes crash to the VMs but not to the host PVE. There's a lot of threads on this topic in the forum, For example:
https://forum.proxmox.com/threads/proxmox-using-high-ram.132813/
https://forum.proxmox.com/threads/oom-shut-down-vm.155657/
https://forum.proxmox.com/threads/p...mory-than-sum-of-vm-without-using-zfs.136639/

But you will see all of them about VMs crashes not the host it self.

Proxmox provide some options for automatic memory allocation, this is by setting the minimum memory lower than memory in GUI. The minimum amount you specified is always available to the VM, and if RAM usage on the host is below a certain target percentage, it will dynamically add memory to the guest up to the maximum memory specified. Please read [0][1] for more information on memory allocation.

Please keep in mind that memory over-allocation can never work, and it's important to account for the host virtualization overhead. As a general practice, the total allocated RAM for all guest systems should be kept below 80% of the host total RAM. Therefore, please review your setup to ensure sufficient memory is available for stable operation [2].


[0] https://pve.proxmox.com/wiki/Dynamic_Memory_Management
[1] https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_memory
[2] https://forum.proxmox.com/threads/p...mory-than-sum-of-vm-without-using-zfs.136639/
 
You must log in or register to reply here.
Top Bottom