Is Silent Mode better then Performance Mode for the Fans?IN HW Monitor Menu Setting to Silent model will better.
I would assume that the silent mode doesnt cool better then performance.
Is Silent Mode better then Performance Mode for the Fans?IN HW Monitor Menu Setting to Silent model will better.
Silent Mode.MAX CPU frequency lower than default.Is Silent Mode better then Performance Mode for the Fans?
I would assume that the silent mode doesnt cool better then performance.
░░ Subject: A start job for unit pve-daily-update.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pve-daily-update.service has begun execution.
░░
░░ The job identifier is 599.
Aug 04 05:52:06 pve pveupdate[381821]: <root@pam> starting task UPID:pve:0005D393:0060C9FA:689082C6:aptupdate::root@pam:
Aug 04 05:52:06 pve pveupdate[381843]: update new package list: /var/lib/pve-manager/pkgupdates
Aug 04 05:52:07 pve pveupdate[381821]: <root@pam> end task UPID:pve:0005D393:0060C9FA:689082C6:aptupdate::root@pam: OK
Aug 04 05:52:07 pve systemd[1]: pve-daily-update.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pve-daily-update.service has successfully entered the 'dead' state.
Aug 04 05:52:07 pve systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
░░ Subject: A start job for unit pve-daily-update.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pve-daily-update.service has finished successfully.
░░
░░ The job identifier is 599.
Aug 04 05:52:07 pve systemd[1]: pve-daily-update.service: Consumed 1.985s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pve-daily-update.service completed and consumed the indicated resources.
Are you running the 6.8 or 6.14 kernel?Has anyone ran into an issue in proxmox where the entire system freezes? When checking the previous boot in journalctl -b -1 -xe was
Code:░░ Subject: A start job for unit pve-daily-update.service has begun execution ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit pve-daily-update.service has begun execution. ░░ ░░ The job identifier is 599. Aug 04 05:52:06 pve pveupdate[381821]: <root@pam> starting task UPID:pve:0005D393:0060C9FA:689082C6:aptupdate::root@pam: Aug 04 05:52:06 pve pveupdate[381843]: update new package list: /var/lib/pve-manager/pkgupdates Aug 04 05:52:07 pve pveupdate[381821]: <root@pam> end task UPID:pve:0005D393:0060C9FA:689082C6:aptupdate::root@pam: OK Aug 04 05:52:07 pve systemd[1]: pve-daily-update.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit pve-daily-update.service has successfully entered the 'dead' state. Aug 04 05:52:07 pve systemd[1]: Finished pve-daily-update.service - Daily PVE download activities. ░░ Subject: A start job for unit pve-daily-update.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit pve-daily-update.service has finished successfully. ░░ ░░ The job identifier is 599. Aug 04 05:52:07 pve systemd[1]: pve-daily-update.service: Consumed 1.985s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit pve-daily-update.service completed and consumed the indicated resources.
Afterwards, the entire system was stuck. Unable to access web interface, unable to ping, unable to ssh, tried checking output to a kvm but it wasn't on at the time so there was no display. A restart brought the device back, but still odd that it happened. Readings in the sensors seem fine, seemingly not dealing with heat issues. Latest BIOS, latest PVE. Some other posts online suggest may be hardware related, but I'm not entirely sold on the idea
I have no idea if it would help with your issue, but I'd suggest the 6.14. I went straight to the 6.14 on mine; my view is that the AMD 9xxx is new enough that you probably don't want a kernel from early 2024.+
6.8.12-13-pve
I have the 7945hx model but I'll still give 6.14 a try. There have been 2 of these freezes so far so hopefully this solveI have no idea if it would help with your issue, but I'd suggest the 6.14. I went straight to the 6.14 on mine; my view is that the AMD 9xxx is new enough that you probably don't want a kernel from early 2024.
7945hx here with the 128GB DDR5 Crucial kit here and a -750 pbo max boost reduction, no freezes so far. Kept the kernel / software up to date on the non-enterprise channel (from the very start), currently 6.8.12-13-pve as of yesterday. But my utilization is fairly low on the CPU besides a few openwebui/ollama tests.I have the 7945hx model but I'll still give 6.14 a try. There have been 2 of these freezes so far so hopefully this solve
Same 128gb kit -500 pbo. This crash happened with all VMs shutdown. If my issue persists with the new kernel, I'll adjust pbo further down.7945hx here with the 128GB DDR5 Crucial kit here and a -750 pbo max boost reduction, no freezes so far. Kept the kernel / software up to date on the non-enterprise channel (from the very start), currently 6.8.12-13-pve as of yesterday. But my utilization is fairly low on the CPU besides a few openwebui/ollama tests.
Would definitely run a memtest / stress test to see if any errors occur, may need a replacement 128gb kit. I really need to get around to doing it myself too just in case I haven't triggered anything yet.Same 128gb kit -500 pbo. This crash happened with all VMs shutdown. If my issue persists with the new kernel, I'll adjust pbo further down.
Any specific test you would recommend?Would definitely run a memtest / stress test to see if any errors occur, may need a replacement 128gb kit. I really need to get around to doing it myself too just in case I haven't triggered anything yet.
The proxmox bootloader should have an option to run memtest86+, just use that (make sure secure boot is off).Any specific test you would recommend?
Perfect, will give it a shot when I have the chanceThe proxmox bootloader should have an option to run memtest86+, just use that (make sure secure boot is off).
I agree the nvme cooling is really bad which is why I made a 3d printed mount. my drives run under 40C now so hopefully the next one they create a real cooling solutions for nvmes.With all the complains about heat, its a mobile CPU, they are designed to go up to 100c depending on the model for peak loads. If you dont like it, get a desktop setup or the Framework Desktop, that type of devices can or have better cooling options.
But i was really unhappy with the NVME situation, heat is a much bigger issue here. My two Western 8TB SN850x getting really hot on idle, up to 70c. I now put them in two USB 4 NVME enclosures and temp stay around 35-45c on idle and around 50 on load, yes its just usb 3.2, but 1gb/sec is enough for a home system. Running them in mirrored ZFS for Proxmox LXC Containers.