<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>System-Administration on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/system-administration/</link>
    <description>Recent content in System-Administration on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 13 Jun 2026 11:45:33 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/system-administration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Recovering a Borked Linux Boot with a USB Rescue Drive and chroot</title>
      <link>https://linuxeries.org/post/2026-06-13-recovering-a-borked-linux-boot-with-a-usb-res/</link>
      <pubDate>Sat, 13 Jun 2026 11:45:33 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-06-13-recovering-a-borked-linux-boot-with-a-usb-res/</guid>
      <description>&lt;h2 id=&#34;introduction-to-linux-rescue-and-recovery&#34;&gt;Introduction to Linux Rescue and Recovery&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when a Linux system becomes unbootable - it can be a real nightmare. Whether it&amp;rsquo;s a failed update, a misconfigured kernel, or a corrupted filesystem, having a reliable method for recovery is crucial. One of the most effective ways to rescue a borked Linux boot is by using a USB rescue drive in combination with the &lt;code&gt;chroot&lt;/code&gt; command. This approach allows you to access and repair your system from a safe environment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
