Proxmox 9.0.11 randomly freezes with no logs

Keeble

New Member
Nov 17, 2025
3
1
1
Hello everyone!
So I've been using Proxmox for awhile and all has been going great! It's just up until recently it started hanging randomly and I'm completely lost on whats causing it. My setup just has an i7 8700k, 32gb of memory and 2 8TB WD Red Plus's. I run the 2 HDDs in a stripe ZFS pool (maybe thats important i dunno). So I decided to try to run my setup on bare metal TrueNAS and I had no issues at all! I decided to go back to Proxmox since I prefer how it works, this time I ran TrueNAS in a VM having it handle my ZFS hard drives as well as NFS and SMB. Everything was working well until I just came back from work and the server has hung yet again. Honestly I'm completely lost at what it could be. The logs produce absolutely no errors before hanging and I don't see anything odd with memory usage, CPU usage or anything like that. Nothing out of the ordinary happens and there really isn't a trigger that causes it.

The memory is quite new, and to be honest I haven't tried a memtest cause I'm confused how just switching OS's could cause issues. The only thing that I might be concerned about is the PSU since it's decently old. But yet again how does it work fine on TrueNAS but not on Proxmox? It makes no sense and I'm completely lost. If anyone has any idea on what it could possibly be I definitely appreciate it! The gap in summary is where it hangs up. The crash occurred around 19:08:00, yet the last log was 18:17:01.

Since posting this, I heard C-States could cause issues with it. Tho I'm unsure how thats happening with qBittorrent downloading/seeding, but I set the max cstate to 1 in GRUB to hopefully help.
summary.pnglogs.png
 
Last edited:
I haven't tried a memtest cause I'm confused how just switching OS's could cause issues.
Hi. I'm not stating that RAM is the reason, but issues from faulty RAM happen unpredictable. So it's worth to check it with Memtest for a night or more anyway.
 
Hi!

Seems like there was something in the way of writing it to disk, you can try to gather the log on a separate console, e.g. netconsole [0], so that the information persists if there block io is unavailable.

[0] https://www.kernel.org/doc/Documentation/networking/netconsole.txt
Hey!
I believe I set it up correctly at least I hope I did. I ran modprobe netconsole netconsole=@192.168.50.70/vmbr0,@192.168.50.133/ on the host and nc -l -u -p 6666 on my main machine, I'll let you know if anything comes up when it freezes next.
 
  • Like
Reactions: dakralex
Hi. I'm not stating that RAM is the reason, but issues from faulty RAM happen unpredictable. So it's worth to check it with Memtest for a night or more anyway.
Of course. It is a possibility of it being the RAM since it's not ECC memory or anything "enterprise" grade. It's just simple Corsair memory. When it freezes next I'll run a memtest to see if that's whats causing this.