<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data-Recovery on Philipp Metzler</title><link>https://chili-it.de/tags/data-recovery/</link><description>Recent content in Data-Recovery on Philipp Metzler</description><generator>Hugo</generator><language>en-us</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chili-it.de/tags/data-recovery/index.xml" rel="self" type="application/rss+xml"/><item><title>Read-Only Is a Superpower: Recovering a Dying NVMe Over SSH</title><link>https://chili-it.de/posts/read-only-is-a-superpower/</link><pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate><guid>https://chili-it.de/posts/read-only-is-a-superpower/</guid><description>&lt;p&gt;A small tax firm called me on a Monday. Their server had &amp;ldquo;reset itself&amp;rdquo; over the weekend. Everything looked wiped.&lt;/p&gt;
&lt;p&gt;It hadn&amp;rsquo;t reset. The truth was worse, and more interesting.&lt;/p&gt;
&lt;p&gt;The system NVMe, a cheap DRAM-less consumer drive that had no business running a production database around the clock, was dying. On the last reboot the BIOS couldn&amp;rsquo;t see it, shrugged, and booted an ancient Windows off a second disk nobody remembered was still in the box. To the staff it looked like the machine had been factory-reset. To me it looked like a drive with unreadable sectors and a controller that crashed the moment you leaned on it.&lt;/p&gt;</description></item></channel></rss>