惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

美团技术团队
阮一峰的网络日志
阮一峰的网络日志
T
The Blog of Author Tim Ferriss
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
宝玉的分享
宝玉的分享
L
LangChain Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Last Week in AI
Last Week in AI
博客园 - 司徒正美
M
MIT News - Artificial intelligence
人人都是产品经理
人人都是产品经理
WordPress大学
WordPress大学
B
Blog RSS Feed
H
Hackread – Cybersecurity News, Data Breaches, AI and More
博客园 - Franky
B
Blog
V
V2EX
J
Java Code Geeks
D
Docker
博客园 - 叶小钗
The Cloudflare Blog
量子位
博客园_首页
MongoDB | Blog
MongoDB | Blog

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
With new HA-Disarm Feature is there a Documentation for N...
invalid@exam · 2026-05-29 · via Proxmox Support Forum

Hi,

I think it's mostly depend on your exact setup, like if you have ceph or not, if you use a SAN, local storage, etc.

Example for me, I let the power cut the node. I don't try a safe shutdown.

Best regards,

Hi,

If I'm not mistaken, there's already information in the official documentation regarding maintenance (node and ceph).

As for the UPS (with Nut, for example), since it's not part of the Proxmox core but rather a modification of the server manager, I don't see what more Proxmox could recommend, as it's primarily the manager who will have to decide on the desired behavior.

This looks more like a risk assessment (by the manager) than a "general guideline" that Proxmox should provide.

For example, we host nodes/clusters in data centers where we cannot have the state of the UPS, so we prefer to let the nodes/cluster have a power cut than having a power cut when he's trying to shut down (we feel it's less dangerous that way).
For us we take the risk of the power cut because we use ceph (so we lose compute & storage at the same time) and have 2 PBS (1local 1remote), so we assume that the power cut won't harm data (if so, we use the backup) and we can just lunch the whole cluster after the power cut (we already have this event 1 time so we know it can survive a power cut).

Note: This is just my opinion

Best regards,