Node Freeze after upgrade from PVE7 to PVE 8

alain_b_

New Member
Sep 2, 2023
3
0
1
Hi,
I had converted my old laptop to a pve node and it had been running perfectly for over 2 years but since I migrated it to PVE 8 it freezes after 48 hours even though there are no VMs on it.
How can I diagnose the problem?
I can't find anything in the system logs.
Thanks

CPU: dual core Intel Core i5-4200M (-MT MCP-) speed/min/max: 2495/800/2500 MHz
Kernel: 6.2.16-10-pve x86_64
Up: 15m
Mem: 1578.8/7656.1 MiB (20.6%)
Storage: 238.47 GiB (43.2% used)
Procs: 172
Shell: Bash
inxi: 3.3.26
 
Last edited:
Hello, could you please share system logs (`journalctl`) containing the timestamp where the crash happened. What NIC model are you using?
 
Hello,

Logs (journalctl) :
Aug 31 13:40:49 pve12 smartd[540]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 62 Aug 31 13:40:51 pve12 pmxcfs[813]: [dcdb] notice: data verification successful Aug 31 13:41:25 pve12 qm[892921]: <root@pam> end task UPID:pve12:000D9FFA:01747D87:64F0798D:qmrestore:8120:root@pam: OK Aug 31 13:41:26 pve12 qm[895577]: <root@pam> update VM 8120: -onboot 0 Aug 31 13:41:26 pve12 postfix/pickup[893811]: BBF76600BC: uid=0 from=<root> Aug 31 13:41:26 pve12 postfix/cleanup[895263]: BBF76600BC: message-id=<20230831114126.BBF76600BC@pve12.local> Aug 31 13:41:26 pve12 CRON[888560]: pam_unix(cron:session): session closed for user root Aug 31 13:41:26 pve12 postfix/qmgr[908]: BBF76600BC: from=<root@pve12.local>, size=39939, nrcpt=1 (queue active) Aug 31 13:41:26 pve12 proxmox-mail-fo[895580]: pve12 proxmox-mail-forward[895580]: forward mail to <mail@example.fr> Aug 31 13:41:26 pve12 postfix/pickup[893811]: C2E7E600BD: uid=65534 from=<root> Aug 31 13:41:26 pve12 postfix/cleanup[895263]: C2E7E600BD: message-id=<20230831114126.BBF76600BC@pve12.local> Aug 31 13:41:26 pve12 postfix/local[895265]: BBF76600BC: to=<root@pve12.local>, orig_to=<root>, relay=local, delay=0.04, delays=0.02/0/0/0.0> Aug 31 13:41:26 pve12 postfix/qmgr[908]: BBF76600BC: removed Aug 31 13:41:26 pve12 postfix/qmgr[908]: C2E7E600BD: from=<root@pve12.local>, size=40103, nrcpt=1 (queue active) Aug 31 13:41:26 pve12 postfix/smtp[895269]: C2E7E600BD: to=<mail@example.fr>, relay=none, delay=0.02, delays=0.02/0/0/0, dsn=5.4.6, status=b> Aug 31 13:41:26 pve12 postfix/qmgr[908]: C2E7E600BD: removed Aug 31 13:41:26 pve12 postfix/cleanup[895263]: C8BC9600BC: message-id=<20230831114126.C8BC9600BC@pve12.local> Aug 31 13:50:01 pve12 CRON[897402]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Aug 31 13:50:01 pve12 CRON[897403]: (root) CMD (/root/nas1-check.sh) Aug 31 13:50:05 pve12 CRON[897402]: pam_unix(cron:session): session closed for user root Aug 31 13:50:05 pve12 postfix/pickup[893811]: 6C998600BC: uid=0 from=<root> Aug 31 13:50:05 pve12 postfix/cleanup[897411]: 6C998600BC: message-id=<20230831115005.6C998600BC@pve12.local> Aug 31 13:50:05 pve12 postfix/qmgr[908]: 6C998600BC: from=<root@pve12.local>, size=815, nrcpt=1 (queue active) Aug 31 13:50:05 pve12 proxmox-mail-fo[897418]: pve12 proxmox-mail-forward[897418]: forward mail to <mail@example.fr> Aug 31 13:50:05 pve12 postfix/pickup[893811]: 76829600BD: uid=65534 from=<root> Aug 31 13:50:05 pve12 postfix/cleanup[897411]: 76829600BD: message-id=<20230831115005.6C998600BC@pve12.local> Aug 31 13:50:05 pve12 postfix/local[897416]: 6C998600BC: to=<root@pve12.local>, orig_to=<root>, relay=local, delay=0.06, delays=0.03/0.01/0/> Aug 31 13:50:05 pve12 postfix/qmgr[908]: 6C998600BC: removed Aug 31 13:50:05 pve12 postfix/qmgr[908]: 76829600BD: from=<root@pve12.local>, size=979, nrcpt=1 (queue active) Aug 31 13:50:05 pve12 postfix/smtp[897432]: 76829600BD: to=<mail@example.fr>, relay=none, delay=0.05, delays=0.02/0.01/0.03/0, dsn=5.4.6, st> Aug 31 13:50:05 pve12 postfix/qmgr[908]: 76829600BD: removed Aug 31 13:50:05 pve12 postfix/cleanup[897411]: 85CB8600BC: message-id=<20230831115005.85CB8600BC@pve12.local> -- Boot 267a79a05ab04acca06875036a61bdd5 -- Sep 02 14:06:57 pve12 kernel: Linux version 6.2.16-10-pve (wolfgangb@sbuild) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian> Sep 02 14:06:57 pve12 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-10-pve root=/dev/mapper/pve-root ro quiet


And below are my 2 network adapters

root@pve12:~# ethtool -i enp3s0 driver: r8169 version: 6.2.16-12-pve firmware-version: rtl8168g-3_0.0.1 04/23/13 expansion-rom-version: bus-info: 0000:03:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no root@pve12:~# root@pve12:~# root@pve12:~# ethtool -i enx3c18a0d5364f driver: r8152 version: v1.12.13 firmware-version: rtl8153a-4 v2 02/07/20 expansion-rom-version: bus-info: usb-0000:00:14.0-2 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no
 
Last edited:
Hello, unfortunately, I don't see anything that could point to an issue in your logs. Have you tried upgrading? The latest version uses kernel 6.5 which might improve the situation.
 

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!