Lvm on Margrop Blog

Adding Proxmox VE local-lvm Usage and Link-Speed Monitoring to Uptime Kuma

Tue, 05 May 2026 17:20:00 +0800

Short version

Proxmox VE local-lvm is usually an LVM-thin pool, not a normal mounted directory, so df -h is not enough to catch it before it becomes full. Network link speed is another quiet failure mode: services may stay online while a NAS or router uplink falls back to 100 Mb/s and turns large file transfers into a crawl. A practical fix is to feed both checks into the Uptime Kuma you already use: expose a small HTTP health endpoint for local-lvm, and push link-speed status from the Proxmox host with an ethtool script.

This article walks through the design, the problems in a naive implementation, improved scripts, systemd units, Uptime Kuma configuration, verification steps, and safety notes. All addresses, tokens, host names, and environment-specific values are placeholders. Replace <PVE_HOST>, <KUMA_URL>, <PUSH_TOKEN>, and <INTERFACE> with values from your own environment.

Resize the disk of an Ubuntu VM in PVE — the complete workflow from Web UI to guest OS

Mon, 23 Mar 2026 10:30:00 +0800

Preface When you manage a virtualized environment with Proxmox VE, running out of disk space is only a matter of time. Maybe your Ubuntu VM keeps pulling more Docker images, or maybe database logs fill up the root partition. In short, disk expansion is a must-have skill for PVE operations. This article walks through the entire process, from resizing the virtual disk in the PVE Web UI to expanding LVM inside the Ubuntu guest, step by step.

1 Why do we need to resize?

PVE usually allocates a fixed-size virtual disk when a VM is created, for example 32 GB. As the workload grows, that space may no longer be enough. Fortunately, PVE supports online disk expansion, and Ubuntu’s default LVM setup also supports dynamic logical volume expansion. Together, they make the process very convenient.

PVE disk inspection connected to UptimeKuma - the 404 pitfall and the final script

Wed, 14 May 2025 22:16:48 +0800

Read first The previous article showed how to push the PVE host’s LVM-Thin usage to UptimeKuma. After following the instructions, some readers got a 404 when the script used curl. This article explains the cause, fixes the script, and provides an optional upgrade path. Follow along from scratch and you should succeed on the first try. 1 Phenomenon: curl ... 404 curl -fsS --retry 3 \ "${PUSH_URL}?status=up&msg=OK" \ -H 'Content-Type: application/json' \ --data-raw "$result" # ↳ curl: (22) The requested URL returned error: 404 The same URL works in a browser or with curl GET:

PVE host disk space monitoring - from pitfalls to UptimeKuma

Wed, 14 May 2025 22:11:33 +0800

Target Reader This article is written for readers who have just started using Proxmox VE (referred to as PVE) and want to copy the steps and get it running. The article aims to: explain why the problem happens provide the full command at each step give troubleshooting ideas when something goes wrong 0 Background - What went wrong? The official PVE installation wizard defaults to putting the VM disk into the LVM-Thin pool (commonly pve/data)

Online expansion of Ubuntu/CentOS disk root directory & modification of partition inode number

Sat, 25 Mar 2023 13:42:44 +0800

When Ubuntu is used as a server system, the system disk may not have enough space. If apt apt is used, the root directory will be full. Granted, adding a disk/partition and mounting it is a solution, but it doesn’t solve all problems (like apt). At the same time, some servers running on cloud platforms do not have good means of operating disks offline. At this time, online expansion is extremely necessary.