Oversubscribing LVM-Thin on Proxmox – warnings
Background LVM-Thin is great because you don’t use all the disk space and can share between hosts. However, it’s dangerous to oversubscribe if one of
proxmox
Proxmox installation stuck on 3% creating LVs
Yep, this is apparently normal, mostly if you had data on the drive before, see: https://forum.proxmox.com/threads/proxmox-installation-stuck-on-3-creating-lvs-please-help-guys.94650/
Proxmox SNMP Primer
Introduction Proxmox VE hypervisors need to be monitored. Some of the key items you could monitor are: Disk I/O Wait time CPU temperature Smart Status
Proxmox Backup Server fingerprint issues after adding Let’s Encrypt ACME
After installing an HTTPS certificate, the following problem started occurring: 2024-05-19T08:41:52.869412+02:00 server pvestatd[1481]: backup-server1.example.com: error fetching datastores – fingerprint ‘X’ not verified, abort! 2024-05-19T08:41:53.063071+02:00 server
Anatomy of (another) Proxmox hypervisor reboot gone wrong
Introduction I hate Proxmox hypervisor reboots. Any hypervisor reboot is a bad thing, because at the end of the day you’ll have VMs on the
Proxmox Mail Gateway Quick Start Guide
Introduction Writing a quick start article for an anti-spam gateway is not trivial. The fact of the matter is everyone’s idea on how to use
Proxmox Hypervisor Reboot: DMAR-IR: [Firmware Bug]: ioapic 3 has no mapping iommu, interrupt remapping will be disabled
A while ago I rebooted a Proxmox server in cluster and got this scary message: DMAR-IR: [Firmware Bug]: ioapic 3 has no mapping iommu, interrupt
Anatomy of Proxmox File Systems Crashes – stuck on `random: crng init done` again?
Proxmox disks sometimes break. It’s not supposed to, but when it happens it can be devastating. I only use defaults. Nothing fancy. Whatever the operating
Proxmox Backup Servers offline after upgrade from 3.1 to 3.2 (large drives)
On both my PBS servers this morning I’m getting the following. Both PBS server has more than 2 TB drives, which might be of relevant.
How do you determine if a Proxmox linked clone is attached to a disk?
Sometimes you want to get rid of a VM template. In doing so, you might encounter the following issue: TASK ERROR: base volume ‘nas02:base-9403-disk-0’ is