<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postgres on Linux Colorado</title><link>https://www.linuxcolorado.com/tags/postgres/</link><description>Recent content in Postgres on Linux Colorado</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 13 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.linuxcolorado.com/tags/postgres/index.xml" rel="self" type="application/rss+xml"/><item><title>Two Ways My Self-Hosted Immich Broke — and Neither Was Corrupt Data</title><link>https://www.linuxcolorado.com/post/2026-08-18-immich-flaky-mount-and-boot-loop/</link><pubDate>Thu, 13 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.linuxcolorado.com/post/2026-08-18-immich-flaky-mount-and-boot-loop/</guid><description>&lt;p&gt;I self-host &lt;a href="https://immich.app"&gt;Immich&lt;/a&gt; for my photo library, and it has broken on me in two completely different ways — both instructive, and both sharing a reassuring punchline: &lt;strong&gt;the photos were always fine.&lt;/strong&gt; The failures were in the plumbing around them, not the data.&lt;/p&gt;
&lt;p&gt;The first was a storage problem wearing a data-corruption costume: thousands of &amp;ldquo;unsupported image format&amp;rdquo; and &amp;ldquo;input file is missing&amp;rdquo; errors for files that were perfectly healthy. The second was a self-inflicted supply-chain problem: an overnight auto-update yanked the database extension out from under the server and put it in a boot loop. This post is both stories, because together they&amp;rsquo;re a decent field guide to operating Immich in a homelab.&lt;/p&gt;</description></item></channel></rss>