<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Recovery on Linux Café</title>
    <link>https://mrtomlinux.org/tags/recovery/</link>
    <description>Recent content in Recovery on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 31 Jul 2026 12:04:25 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/recovery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Recovering from a Failed systemd Update on a Small Home Server</title>
      <link>https://mrtomlinux.org/post/2026-07-31-recovering-from-a-failed-systemd-update-on-a-/</link>
      <pubDate>Fri, 31 Jul 2026 12:04:25 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-31-recovering-from-a-failed-systemd-update-on-a-/</guid>
      <description>&lt;h2 id=&#34;introduction-to-systemd-recovery&#34;&gt;Introduction to systemd Recovery&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when a &lt;code&gt;systemd&lt;/code&gt; update fails - it&amp;rsquo;s a pretty stressful experience, especially when &lt;code&gt;systemd&lt;/code&gt; is the core init system for your Linux distribution. Recently, I had a similar issue on my small home server. The update process seemed fine at first, but after a reboot, I was greeted with an error message indicating that &lt;code&gt;systemd&lt;/code&gt; had failed to start.&lt;/p&gt;&#xA;&lt;h2 id=&#34;identifying-the-problem&#34;&gt;Identifying the Problem&lt;/h2&gt;&#xA;&lt;p&gt;The real trick is to stay calm and use the right tools to diagnose the issue. I booted into rescue mode using a live USB stick, which gave me access to the filesystem. From there, I inspected the &lt;code&gt;systemd&lt;/code&gt; logs using the following command:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Recovering from a Failed Boot after Accidentally Removing Initramfs with a Rootless Podman Container</title>
      <link>https://mrtomlinux.org/post/2026-07-30-recovering-from-a-failed-boot-after-accidenta/</link>
      <pubDate>Thu, 30 Jul 2026 11:09:16 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-30-recovering-from-a-failed-boot-after-accidenta/</guid>
      <description>&lt;h2 id=&#34;introduction-to-the-problem&#34;&gt;Introduction to the Problem&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been experimenting with rootless Podman containers on my Linux system, and I&amp;rsquo;m sure I&amp;rsquo;m not the only one who&amp;rsquo;s pushed the limits of what&amp;rsquo;s possible without root privileges. However, in my enthusiasm, I once accidentally removed the initramfs image, which led to a failed boot. Don&amp;rsquo;t bother with trying to guess how I did it - let&amp;rsquo;s just say it was a misconfiguration that allowed a rootless container to access the host&amp;rsquo;s filesystem. This article will guide you through recovering from such a situation, focusing on practical steps and commands to get your system back up and running.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Recovering from a Failed Boot After Accidentally Removing systemd on a Desktop System</title>
      <link>https://mrtomlinux.org/post/2026-05-21-recovering-from-a-failed-boot-after-accidenta/</link>
      <pubDate>Thu, 21 May 2026 10:50:50 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-21-recovering-from-a-failed-boot-after-accidenta/</guid>
      <description>&lt;h2 id=&#34;introduction-to-the-problem&#34;&gt;Introduction to the Problem&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when you&amp;rsquo;re trying to remove unnecessary packages from your system - accidentally removing systemd can be a real headache. As of 2026, systemd has become an essential part of many Linux distributions, including Debian, Arch Linux, and OpenSUSE. It&amp;rsquo;s responsible for managing system services, boot processes, and system states. If you&amp;rsquo;ve found yourself in this situation, don&amp;rsquo;t worry, it&amp;rsquo;s recoverable. In this article, we&amp;rsquo;ll walk through the steps to recover from a failed boot after removing systemd.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
