<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Homelab on d093w1z</title><link>http://d093w1z.com/tags/homelab/</link><description>Recent content in Homelab on d093w1z</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 16 May 2026 22:45:37 +0530</lastBuildDate><atom:link href="http://d093w1z.com/tags/homelab/index.xml" rel="self" type="application/rss+xml"/><item><title>Recovering a Broken Proxmox LXC After Running Out of Disk Space</title><link>http://d093w1z.com/posts/proxmox-calibre-storage-recovery/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>http://d093w1z.com/posts/proxmox-calibre-storage-recovery/</guid><description>Recovering a Broken Proxmox LXC After Running Out of Disk Space Link to heading Recently I ran into a serious issue with my homelab setup where multiple LXC containers on my Proxmox server suddenly stopped starting.
The root cause turned out to be a completely full storage volume combined with large RAW disk images and duplicated data.
This post is a short overview of how I recovered the system, migrated my Calibre setup to a cleaner structure, and improved the deployment architecture.</description></item></channel></rss>